event tracking
Event Taxonomy Workshop
Working groups iterate on naming conventions, versioning rules, and reviewer workflows suited to fast-release environments. You practice diff reviews on breaking changes and leave with a lightweight governance memo teams can adopt without heavyweight committees.
- Namespace patterns for mobile, web, and partner surfaces
- Breaking-change checklist with rollback considerations
- Reviewer rotation model for small squads
- Diff ritual templates for release trains
- Thailand-relevant examples for omnichannel retail
- Office-hour debugging for your draft taxonomy
- Stakeholder comms pack for engineering partners
Outcomes
- Draft a versioned taxonomy outline with rollback notes
- Define who signs off on breaking changes in your org size
- Ship a short governance memo engineering can link from PR templates
Participant notes
Event Taxonomy Workshop gave us a diff ritual we pasted into our release checklist. The omnichannel retail examples matched our store rollout.
Still wish we had one more week on partner SDK naming, but the governance memo alone saved two noisy debates.
Program FAQ
No SDK coding; focus is naming, governance, and review rituals.
Yes with a client sponsor who can approve naming choices.
Vendor contract negotiation and billing administration are out of scope.