Useful analysis begins with a precise question and enough context to interpret behaviour responsibly. This note offers a practical way to bring both into everyday product work.
Name behaviour, not interface
Buttons move and screens are redesigned. User intent is more stable. Prefer names such as subscription_started over green_button_tapped. Add interface context as properties when it is genuinely useful for diagnosis.
Define before implementation
Every event needs a plain-language definition, trigger, properties, owner, and example. Review the plan with product, engineering, and analytics together. Ten minutes spent resolving ambiguity in the plan can prevent weeks of conflicting reports.
Treat changes as product changes
Version important definitions, review analytics in release acceptance, and keep a short changelog. Deprecate old events deliberately instead of silently reusing them. This creates an audit trail and protects trend continuity.
Write down the decision you expect the analysis to influence. If no possible result would change that decision, refine the question before adding another chart.