Metric gaming occurs when people optimize a measured number without improving the underlying outcome. It is a rational response to a target that rewards local activity rather than value flowing through the system. section 9.3
Watch for a metric improving while its real-world counterpart worsens:
- Splitting one coherent change into several PRs can lower per-PR cycle time while leaving feature lead time unchanged and increasing review overhead. section 9.3
- Reducing test scope can shorten builds while change failure rate rises; closing incidents early can improve MTTR while root causes persist. section 9.3
Table 9.3 Paired metrics as guardrails against gaming
|
Speed metric
|
Quality guardrail
|
Gaming looks like….
|
|
Deployment frequency
|
Change failure rate
|
More deploys, more incidents
|
|
Lead time
|
Activity ratio
|
Faster queue clearing, some waiting
|
|
MTTR
|
Incident frequency
|
Faster patching, same root causes
|
|
Cycle time
|
Rework rate
|
Faster merges, more post-merge fixes
|
|
Build time
|
Test coverage
|
Faster builds, fewer tests
|
Compare speed measures with quality guardrails to spot when a better number may hide a worse system. section 9.3
