Events Playbook

Unified all event documentation into one playbook, replacing five scattered sources and cutting onboarding time for anyone learning eventing.

5 → 1
five scattered sources replaced by one playbook
↓
time to learn eventing for new people and teams
↑
single source of truth for the full event lifecycle

Timeline

Phase 0
Kickoff: event docs scattered across sources, poor feedback
Phase 1
Discovery: gathered and organized all docs by use case
Phase 2
Ship v1: playbook published, old docs deprecated and redirected
Phase 2
Feedback: some content still duplicated with other intranet pages
Next
New sections added as recurring Slack questions surface

From scattered docs to one playbook

Docs scattered
5+ sources

Consolidated + validated
with stakeholders

Published
old docs deprecated

The risk, and what happened

Risk	How it was handled	Result
Usability. No unified source for how to create, modify, or deprecate an event. Continued time loss for every new person or team learning eventing from scratch.	Chose to consolidate rather than patch each scattered source. Validated the structure with stakeholders before drafting.	One source of truth for the full event lifecycle instead of five. Onboarding time to learn eventing dropped.

My role. Owned the consolidation, the stakeholder validation, and the intranet publishing and redirect. Partnered with teams across Slack to socialize the change and redirect ongoing questions.

What went wrong. Some content still ended up duplicated with other intranet sections at first. Fixed in a second pass that cleaned up the overlap.

Product leader with a data scientist past · Zapier, Clearbit, HubSpot

Product doc: ale-cabrera.com/portfolio/events-playbook