Events that survive a reorg
When squads reshuffle, analytics often breaks first. A naming and ownership pattern that keeps measurement intact through org change.
Application analytics rarely fails because the tool is wrong. It fails when ownership of event names walks out with the last PM who cared. Reorgs expose that soft spot overnight.
Write a short constitution: verb-object event names, English-only in code, localized labels only in the UI, and one named steward who can reject new events that break the pattern. Publish it where engineers already look for standards.
For products serving Korean and English interfaces, keep the code contract stable. Translating event strings mid-flight creates filters that silently empty the moment a new teammate joins.
Limit the core plan to the events that answer activation and retention. Expansion rights belong to the steward—not to whoever opens a pull request after a late brainstorm.