Event Taxonomy Craft begins with the laptops closed. Each person writes, on paper, the ten verbs a user performs that would still matter if the app were described to a journalist. Then we compare lists. Marketing names lose. Internal jokes lose. ‘cta_click_2’ is retired without a eulogy.
A good event name is a sentence fragment a support agent could speak: ‘slot reserved’, ‘advice task completed’, ‘van dispatched’. Properties then carry the adjectives — platform, country, plan — so that the verb stays stable when the UI is redesigned. Teams that encode the button colour into the event name are writing a diary of the interface, not a history of behaviour.
The public argument
We argue in the room because the argument will happen later anyway, in a worse setting, with a board pack already printed. Product, data, and support must be able to read the same noun. If legal needs a different grain — for example, ‘account closed’ versus ‘app uninstalled’ — that split is made explicit rather than hoped for.
Only after the paper list is stable do we open a tracker. Implementation is then a translation, not a design session. This is slower than a Friday dump of events. It is also the reason alumni still write to Amira a year later with a chart that can be reconstructed by someone who was not in the original sprint.
If you want a facilitated version of this workshop under NDA, the desk will point you to Private Advisory. The public sitting is small and spoken; it is not a place to invent a hundred events for a roadmap that does not exist yet.