Delete metrics that have no corresponding goal
Aliases: orphan metric · vanity metric · metric retirement
What it is
An orphan metric is a number on the dashboard that cannot be traced to any live goal. Page views, cumulative registrations, and all-time peak concurrency often remain because they were once asked or because they cost almost nothing to generate. Deletion is not tidiness. A metric without a goal still occupies alerts, standups, and experiment readouts, and reports “the number moved” as if something that matters had happened. What should go is counting that no longer serves a judgment, not every number that looks simple.
Why it happens
Metrics have a creation event and rarely a retirement event. The goal changes; the field stays. A chart added for one demo becomes the default home. Orphans harm along two paths. Attention: the meeting has to find the columns that matter inside the noise, and discussion quality falls with column count. Spurious causation: an orphan in the treatment arm rises by chance, is treated as a side effect or unexpected win, and then changes the design, even though nobody can say which success it corresponds to. Orphans also defend themselves: because they are still reported they look important; because they look important nobody dares delete them. Deletion restores “which goal does this serve” as an admission condition, and turns the dashboard from an archive back into a judgment tool.
Studying it
Trace every live metric to a goal: keep those that can state a current goal, signal, and use; send the rest to a deletion candidate set. Count citations in meeting recordings or notes; long-zero citation with no regulatory use marks an orphan. Run a deletion trial: drop the candidates from the default view for several weeks and see whether any decision fails for lack of them; if none does, deletion holds. Distinguish sentinel metrics that are rarely watched but extremely costly when they break from true orphans; sentinels have a goal, it is risk control rather than optimization.
Where it stops holding
Statutory counts in legal, financial, and safety reporting cannot be dropped because the experience team has no goal for them. Raw events needed for exploratory analysis and incident debugging belong in the query layer; they need not appear on the default experience dashboard. Some metrics exist to brief external stakeholders; if that briefing still happens, they are not orphans. Deletion is not a ban on recomputation: archive, stamp an expiry, and leave the default view, which is more auditable than physically erasing history.
Applying it
- Label each default metric with the live goal it serves; blanks enter the deletion set.
- Pull candidates out of the default view first, keep query access, and watch two cycles for a decision that fails without them.
- If none fails, retire alerts and meeting slots, and write the expiry date and reason into the change log.
- New metrics must register a retirement condition: goal cancelled, or two consecutive periods with zero citation, starts the same flow.