Events Migration

Ran the org-wide migration to schema-validated Avro events across every microservice leaving the monolith.

↑
team understanding of the migration's value
→
roadmap reworked to flex around team priorities
Phase 0
added after early learnings, when deadlines slipped

Program-level timeline

Phase 0
Kickoff: monolith-to-microservices move forces Avro schema rules
Phase 1
Discovery: legacy events cataloged, owners identified via Lost & Found
Phase 2
Ship v1: migration roadmap phased, checklists per phase
Phase 2
Feedback: deadlines slipped, no downstream lineage tooling
Next
Phase 0 added, roadmap reworked around team priorities

How the program moved

Monolith → microservices

Events cataloged

Phased roadmap

Deadlines slipped

Phase 0 added

The risk, and what happened

Risk	How it was handled	Result
Feasibility. No schemas or rules meant risk of breaking changes and duplicated, double-owned events at scale as the org moved to microservices.	Cataloged every legacy event and assessed relevance. Broke the program into phases with checklists rather than one big migration.	A phased migration roadmap, with ownership and documentation built out through the Lost and Found and Playbook projects.

My role. Owned the migration roadmap, the phasing, and the cross-team sizing negotiations. Partnered with every team that owned events being migrated.

What went wrong. Deadlines slipped because this started as isolated initiatives instead of one coordinated program. Fixed by adding a phase 0 and reworking the roadmap around actual team priorities.

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

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