A support team meets its response-time KPI by closing difficult tickets early and reopening them later. The dashboard improves while repeat contacts and customer frustration rise.
Decision situation
KPI and benchmark review
Check whether a score is still a useful proxy for the real goal and whether the comparison is being interpreted consistently.
Deep decision guide · reviewed 2026-09-10
A green dashboard can still be describing a bad outcome.
Is the metric measuring the goal, or has the metric quietly become the goal?
Teams need proxies because many goals are difficult to observe directly. The trouble starts when a convenient score stops being treated as partial evidence and becomes the definition of success. A number is easier to compare than a messy objective, so the substitution can happen without anyone deciding to do it.
Metric problems are not all the same. Surrogation asks whether the proxy is replacing the goal in judgment or action. Systematic bias asks whether the measurement process itself is shifted. Outcome bias and confirmation bias can create additional reasoning problems around a good score. Different failures need different fixes.
A better review
Run the decision in five moves.
- 1. Write the real objective in ordinary language before opening the dashboard.
- 2. State what the metric measures directly, what it only approximates and at least one important dimension it misses.
- 3. Run the gaming test: describe a realistic action that improves the number while leaving the objective unchanged or worse.
- 4. Compare the score with an outcome measure, validation sample, companion metric or qualitative evidence that does not share the same blind spot.
- 5. Review the process and incentives behind the score, then define when the metric should be changed, complemented or retired.
Worked example
The green support dashboard
Leaders treat the green KPI as proof that the process works and ask how to push the score even higher.
The team separates response time from the customer outcome, checks how workflow choices affect the metric, adds repeat-contact evidence and asks whether the KPI still represents the objective it was designed to support.
Decision record
Write down the parts that are easiest to rewrite later.
- Underlying objective in plain language.
- Metric definition and what it captures.
- Important dimensions the metric misses.
- How the number can be improved without improving the goal.
- Independent outcome or validation evidence.
- Trigger for changing or retiring the metric.
Practice the decision
Try the reasoning before the stakes are real.
A team prefers a new platform and highlights its strong benchmark score. It dismisses workload, data quality and operating constraints that are not measured by the benchmark.
Try the scenario →A support team meets its response-time KPI by closing tickets early and reopening them later. Leaders call the process successful because the dashboard is green.
Try the scenario →Compare nearby explanations
Similar labels can point to different failures.
Ask whether the problem is that people are optimizing or interpreting the proxy as the goal, or that the measurement process itself is systematically shifted away from the target.
Compare the two →Reviewed research notes
Go deeper where the evidence needs more context.
Surrogation is more specific than the slogan 'what gets measured gets managed.' Research in strategic performance systems shows how a measure can start to stand in for the construct it was designed to represent, and how decision processes can reduce that substitution.
Read the synthesis →Evidence boundary
Useful lens, not a diagnosis.
The project treats surrogation as a narrower management-accounting construct, not as a synonym for every bad metric. A KPI can also fail because of data quality, incentives, sampling, calibration or an unsuitable objective, so the label should never replace direct measurement analysis.
This guide links a reviewed surrogation synthesis and the separate systematic-bias comparison while keeping the existing evidence-reviewed cognitive lenses visible.
Signals to notice
Reasons to slow down and check.
- Improving the metric is discussed as if it automatically improves the goal.
- A single benchmark number hides different operating conditions.
- A good score is being used to defend the process without checking consequences.
Questions before action
Make the missing evidence visible.
- What real outcome is this metric supposed to represent?
- What important behaviour can improve the score without improving the goal?
- Would we make the same decision if the score were hidden and only underlying evidence remained?
Relevant lenses
Concepts that may help you test the reasoning.
Use this concept as a question to test the decision, not as a label for a person.
Open →Use this concept as a question to test the decision, not as a label for a person.
Open →Use this concept as a question to test the decision, not as a label for a person.
Open →Practical moves
Do something different, not only notice a label.
Fix the comparison dimensions before a preferred option makes the criteria move.
Open →Give a strong alternative case enough space to challenge the preferred option.
Open →Preserve what was known, expected and uncertain before the outcome changes memory.
Open →Skill to develop
Evidence evaluation
You can separate a persuasive claim from the evidence that should change your mind.
Practice this situation
Choose a useful first move.
A team prefers a new platform and highlights its strong benchmark score. It dismisses workload, data quality and operating constraints that are not measured by the benchmark.
Skill: Evidence evaluationOpen scenario →A support team meets its response-time KPI by closing tickets early and reopening them later. Leaders call the process successful because the dashboard is green.
Skill: Evidence evaluationOpen scenario →