KPI names that survive refactors
Name the engineering intent, not the ticket label—or the next board rename breaks every report.
Teams often treat metric names as disposable labels. A designer renames a screen, an engineer ships a new component, and suddenly deploy_fail and change_error both exist for the same moment. KPI reports that once looked clean become archaeological digs.
Prefer verbs that describe intent. Keep platform out of the event name—put it in a property so web and app stay comparable during engineering reviews. Write allowed properties on the same day you create the signal.
In Baseline Audit engagements we spend the first day on inventory alone, because until synonyms are visible every later fix guesses at the wrong root.