When I suggest that people will game whatever metrics we put in place, I'm often met with shocked indignation. We would never game the numbers! And yet we do.
I took my car in for service this morning and I was asked if it was ok that they split the bill across two transactions. "You're being measured on number of cars through?" I asked. The answer was obviously yes, and this way I counted as two cars.
It's not just a matter that the numbers are now wrong, we have now introduced waste into the system. There were two credit card transactions rather than one. Two receipts instead of one. There was additional time for the workers to explain why they wanted to do it this way. Overall, this was complete waste, but because they felt they were being judged on the count of cars through, it was justified.
If people think that they'll be judged based on measurements then they'll game those. The more judgement, the more the numbers will be inaccurate, and the more waste will be introduced into the overall system.
You might think that I'm opposed to measuring anything then but that's not at all true. I'm a big proponent of measuring those things we want to improve. I'm just a realist and recognize that we have to design our measurements very carefully. If we measure the wrong things, or in the wrong way, we'll drive the wrong behaviours and that's our problem to solve.
Big congrats to Annika Reinke for winning the Hector Foundation Prize 2025 for Metrics Reloaded, setting new standards for AI in image analysis. 
Want deeper insights into your security threats? Check out Remediation Metrics! 
Track key security insights like: 
Greg Cocks 
NBA37 – DORA
4 DORA-Metriken: Speed (Lead Time, Deploy-Freq) & Stability (Change-Fail %, MTTR).
Spiegel fürs Team, kein KPI-Pranger.
Quick-Check zeigt euren Reifegrad & Hebel.
Welche DORA-Metrik packt ihr zuerst an?