Stop prefixing events with squad names
Squad prefixes feel tidy until two teams track the same action under different banners and your funnel silently splits.
- naming
- instrumentation
Application analytics collapses when every squad invents its own namespace for the same user action. Prefer a shared vocabulary: object, action, and context—written once and reused.
Ban marketing adjectives and temporary project codes inside event names. Properties can carry plan, surface, and experiment IDs; the event name should still make sense after a reorg.
Store the dictionary where engineering already looks—repository docs or a shared sheet with owners—not only in a slide from last quarter’s offsite.
In taxonomy audits from Yeongcheon we routinely find twenty near-duplicates of the same click. Collapsing them usually unlocks more signal than adding another chart.