liveBook · Manning

Paired metric

As explained in Build High Value Software Systems

A measure considered alongside another measure that guards against harmful changes to the underlying system.

A speed metric can improve while the system gets worse. Pair it with a guardrail that reveals whether the underlying work is actually improving: more deployments alongside more failures, for example, is not healthier delivery. 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

Common speed metrics and their quality guardrails, with examples of what gaming looks like. section 9.3

Use the pair to test whether a better number reflects a better system: faster lead time with flat activity ratio may mean the queue was gamed. When replacing a vanity metric, introduce a system-level measure alongside it, then try one improvement experiment and make the results visible to the team. section 9.3

How Build High Value Software Systems covers it

How deep it goes
Defines the gaming signal and lists five speed-and-quality pairings, without specifying how to calculate each metric.
Examples
Illustrates deployment frequency with change failure rate, lead time with activity ratio, and cycle time with rework rate.
What you can do after
Evaluate apparent process gains by checking whether a paired guardrail degrades.
How it connects
Links vanity metrics and metric gamification to deployment frequency, lead time, MTTR, cycle time, and build time.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.