Data Core · KPI management · Module
The review
The rhythm in which measures are actually read and something is decided — because where the review is presentation, the whole measurement effort is decorative.
The idea
How it works
Measurement becomes management at the review or it does not become management at all. A meeting where numbers are presented, noted and moved past is reporting with an audience.
The most useful structure is exception-based: only measures outside their normal variation are discussed. It shortens the meeting substantially and directs it at what changed.
Working with it
In practice
- 01
Discuss only the exceptions
Measures inside their normal band need no discussion. This alone halves most review meetings.
- 02
Require a decision or an explicit no action
Every exception ends with something decided, including deciding that nothing is needed.
- 03
Match the rhythm to the measure
Measures that move monthly do not need weekly review. Reviewing faster than the measure moves produces reaction to noise.
- 04
Record what was decided
And check it at the next review. Without that, the same exception is discussed repeatedly.
One level in
The components of the review
A component is something that exists afterwards which did not exist before — a deliverable or a mechanism, not an intention.
Discuss only measures outside their normal band. It halves the meeting and directs it at what actually changed.
The other modules in kpi management
Choosing what to measure
Narrowing to the few measures the organisation is actually run on, balanced across what matters rather than across what is easy to collect.
LearnDefinitions
What each measure means precisely enough that two people calculating it independently get the same answer.
LearnTargets and thresholds
What good looks like, at what level, and what happens when the reading crosses it — because a measure with no threshold produces observation rather than action.
Learn