Event Names That Survive Roadmap Churn
A tracking plan ages poorly when names describe UI chrome instead of user jobs.
Button-level event names break the moment design renames a screen. Prefer verbs tied to the job: project_exported, invite_accepted, report_scheduled.
Keep properties for UI context—screen, surface, experiment flag—so you can still debug without baking labels into the event name itself.
Review the plan every release train. Deprecate with aliases rather than silent renames, and keep a changelog that analysts can trust.