FM-11: Metric Authority Drift
A pattern. The number was meant to inform the decision. Now it is the decision.
Justin R. Greenbaum · The Lexicon · June 2026
A VP of sales knows a deal is real, but it does not fit the stages the forecast tool recognizes, so it gets logged unqualified and dropped, because the pipeline number now sets priorities the VP used to set. A hiring manager wants to make an offer, but the scorecard lands two tenths under the bar, so it dies in committee, because the rubric became the verdict instead of an input. A support director’s team is resolving harder cases on purpose, but the handle-time dashboard is red, so headcount gets pulled from the work that needed it, because the metric outranks the context it cannot see. A product manager sees a feature is right for the next two years, but it costs a point on this quarter’s chart, so it gets cut, because the chart carries more weight than the people who built the roadmap.
None of these people are failing. Each one is deferring to a number that was never supposed to hold the final say.
This has a name. It is Metric Authority Drift.
Here’s the pattern. A metric arrives to inform a decision, one input among several. Over time it is easier to point at the number than to defend a judgment, so the number starts carrying the decision alone. People stop asking whether it is meaningful and start asking whether it is green. The measure that stood in for the goal becomes the goal. Authority drifts onto the metric, and no one ever decided to hand it over. Leadership reads following the data as rigor, which is the reverse of what happened. Judgment was not informed. It was replaced.
Deference masquerades as rigor. The manager who cites the dashboard for every call is called data-driven. The team that hits its number is called high-performing long after the number stopped meaning what it did. The leader who follows the metric is never asked to justify it; the one who overrides it has to defend the exception. The signal the system reads is rigor. The condition underneath is a decision quietly handed to a number.
What Metric Authority Drift gets mistaken for is what keeps it alive.
Data-driven leadership. Accountability. Operational maturity. Professionalization. Each is a hero narrative, and each is how the system rewards the behavior that blinds it. Praising the data-driven manager removes the reason to ask what the data cannot see. Treating the override as the thing that needs defending teaches everyone to stop overriding. In reality, it is abdicated judgment.
Hero narratives are how Metric Authority Drift survives contact with the quarterly business review.
The pattern recurs and changes costumes. In one organization it is a sales team walking away from real revenue because the deal does not fit the stages the tool recognizes. In another, a hospital guarding its throughput metric while the care it was built to protect erodes. In a third, a “we go where the data tells us” mantra so complete that the decision the data cannot see never gets made.
The conditions are structural, not behavioral. Better dashboards do not interrupt it, because a cleaner number is easier to defer to. More data-literacy training does not interrupt it; it teaches people to trust the number more, not less. Tighter targets and better KPIs do not interrupt it; they deepen the metric’s authority instead of bounding it.
What interrupts it is structural. Declare zones where judgment openly overrides the metric, so there are decisions the number does not get to make. Have leaders model metric refusal in the edge cases, so overriding is something the room watches, not something it punishes. Keep metrics as inputs, not verdicts, each tied to a named owner who holds the call. Run retrospectives on decision quality, not just outcomes, so a sound call that missed the number still counts as sound. Where a number has fully captured a decision, the fail-safe is to invalidate it as the decision authority and force the judgment back into the room.
When Metric Authority Drift has a name, the options change.
The product manager who cut the right feature stops calling it discipline and sees a decision the dashboard made for him. The manager above stops reading “follows the data” as rigor and asks which calls the data is quietly making. The executive sees that a data-driven review and a well-judged operation are not the same reading, and that one has stood in for the other. The board sees that a green dashboard is not evidence the right decisions are being made; it can be evidence they have been handed to the dashboard.
Naming does not fix. Naming changes what can be seen. What can be seen is what can be acted on.
If any of this feels familiar, it has a name and a taxonomy.
The canonical definition of FM-11, including its early warning signals, common misdiagnoses, and recovery conditions, is at dripractice.com/fm/fm-11.
A role-specific view of how the same pattern looks from the executive seat is at dripractice.com/lens/the-executive.
A five-minute diagnostic that runs entirely on your device and never leaves it is at dripractice.com/diagnose.
Next in The Lexicon: FM-12, Strategic Myopia. Once the number holds the authority to decide, the organization optimizes for what the number can see and slowly loses the rest. FM-12 is what happens to strategic vision when the dashboard becomes the map.
Subscribe to The Lexicon.