Naming rules, ownership, and review practices that keep instrumentation useful after launch.
Model meaning before screens
Screen-based names decay as navigation changes. Prefer events that describe meaningful actions or state transitions, supported by stable context properties. Keep display location as a property when it matters rather than multiplying events for every surface.
Use a small grammar
Choose a consistent pattern such as object_action and document approved verbs. Define required properties, data types, allowed values, collection source, and owner. Examples should show edge cases, not just the happy path.
Govern changes like an interface
Instrumentation is a data contract. Review additions before implementation, version breaking changes, test in staging, and assign ownership for retirement. A lightweight monthly review prevents duplicate events and undocumented properties from becoming permanent.