Naming events that survive releases
A taxonomy that breaks every sprint is worse than having fewer events.
Name features by user intent, not by temporary UI labels. Screens rename; intents tend to last.
Pair every feature with a first-use event and a completion event. Incomplete pairs make funnels guesswork.
Document ownership. When two teams ship into the same schema, collisions are inevitable without a named steward.
Version only when meaning changes. Cosmetic property additions should not fork event names.
Keep a short rejected list. Recording why you did not track something prevents the same debate next quarter.