Field notes
Field notes on measuring well
Short pieces of guidance drawn from common situations. Free to use and share.

The trouble with green dashboards
When every indicator on a report is green, month after month, it is worth asking what would turn one red. Often the thresholds were set to avoid alarm, or the measures track activity rather than results. A healthy report shows some amber: it means the measures are sensitive enough to notice change. Try asking each owner, "What would have to happen for this to go red?" If nobody knows, the measure is not doing its job.
When a proxy becomes the target
Response time is a proxy for service quality; tickets closed is a proxy for productivity. Once people are rewarded for the proxy, it drifts away from the thing it stood for. Pair each proxy with a balancing measure that would suffer if the proxy were gamed, such as reopened tickets alongside tickets closed, and review both together.
Judging a rollout in its first ninety days
Licence counts and logins look reassuring but say little. More honest early signals include: the share of a core task now completed in the new system end to end, the number of workarounds staff report, and how often old systems are still consulted. Agree these before launch and review them at fixed points.
Meetings that use numbers well
A review meeting should spend most of its time on exceptions and decisions, not on reading figures aloud. A useful monthly agenda: changes since last time, measures outside agreed range with owner commentary, decisions needed, actions from last month. Keep a decision log so that next month starts from what was agreed.
Retiring a measure gracefully
Measures outlive their purpose. Once a decision has been taken, ask whether the measure still informs anything. If not, announce its retirement, record why, and stop collecting it. The time saved is usually larger than anyone expects.