Skip to content
ale@portfolio:~/portfolio$ cat README.md

portfolio

Every case study here answers one question: measurable outcome.

events-playbook.mdZapier

Events Playbook

ShippedTeam: Data
TL;DR

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

Outcome

  • ↓time to learn eventing for new people and teams
  • ↑single source of truth for the full event lifecycle
Saw It
  • Event creation documentation was getting poor feedback: users called it confusing, frustrating, and time-consuming to work through.
  • The actual documentation lived across several sources, including Slack conversations, with no single owner.
↓
Figured It Out
  • Chose to consolidate rather than patch each scattered source individually.
  • Needed stakeholder sign-off on structure before writing, to avoid building something that duplicated existing docs.
  • Validated the schema with stakeholders before drafting.
↓
Did It
  • Shipped the playbook to the intranet, deprecating and redirecting old docs.
  • Some content still ended up duplicated with other intranet sections at first. Fixed in a second pass that cleaned up the overlap.

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.

Full breakdown

Problem & Risk

Usability Risk

No unified source for how to create, modify, or deprecate an event. Risk was continued time loss for every new person or team trying to learn eventing from scratch each time.

Customer Discovery & Validation

Evidence

Direct user feedback calling the existing docs confusing and time-consuming, plus a real second-pass fix once duplication with other intranet sections was found post-launch.

Context

Documentation was in several sources, including team conversations, with an obvious need to unify the information in a single place.

Timeline

git log --oneline⏱ ongoing maintenance
kickoff: event docs scattered across sources, poor feedbackPhase 0
discovery: gathered and organized all docs by use casePhase 1
ship v1: playbook published, old docs deprecated and redirectedPhase 2
feedback: some content still duplicated with other intranet pagesPhase 2
next: new sections added as recurring Slack questions surfaceNext

What We Did

  • Gathered and organized all existing documentation by use case and priority
  • Validated the structure with stakeholders, drafted, then validated content
  • Published to the intranet, deprecated old docs, redirected traffic
  • Socialized it, pointed every related Slack thread to the playbook going forward
~ rough sketch, not an actual screenshot ~

docs scattered

5+ sources

consolidated + validated

with stakeholders

published

old docs deprecated

Who Benefits

Developers and product teams get one source of truth for the full event lifecycle instead of five. Onboarding time to learn eventing dropped.

Next Steps

Adding new sections as recurring questions come up.