Event names that survive the third analytics hire
Event catalogs rot when every engineer invents a dialect. A durable naming pattern keeps engagement reports legible as the team grows.
Most engagement confusion we see in Korea-based product teams is linguistic, not statistical. btn_click_primary, PrimaryButtonTapped, and ui.primary_cta may all mean the same moment — or three different ones. The third analytics hire spends their first month reconciling dialects instead of answering product questions.
Prefer object-action pairs that mirror the product vocabulary users already hear: report.shared, dashboard.filter_applied, export.scheduled. Keep property names stable even when UI labels change. Document aliases only when you must preserve historical continuity, and put that alias table next to the engagement dashboard so readers know why older cohorts look different.
If you cannot explain an event name to a stakeholder without opening the tracking plan, rename it before the next release train.