Most process dashboards fail in the same way: they report outcomes at a cadence too slow to act on them. By the time the monthly report shows a cycle-time increase, the cause is three weeks old and the people who could explain it have moved on.
Five numbers, reviewed weekly at the level of the process owner, are usually enough to run an operation.
1. Cycle time, measured end to end
Not the time a step takes — the elapsed time from trigger to delivery, including all waiting. Report the median and the 90th percentile. The gap between them tells you how much of your process is exception handling, which is usually where the redesign work is.
2. Queue age
The age of the oldest item waiting at each handoff. This is the earliest warning signal you have: queue age rises days before cycle time does. If you track one leading indicator, track this one.
3. First-pass yield
The percentage of items that complete without rework, rejection or return. Most organisations overestimate this by 20 points because they count only formal rejections, not informal ones — the phone call that fixes an error before it becomes a ticket.
4. Failure demand
The share of incoming work caused by a defect upstream: status calls, corrections, re-sends, escalations. In healthy processes this sits under 10%. In the diagnostics we run, the median is 27%, and it is almost entirely invisible in standard reporting because it looks like normal workload.
5. Decision latency
The elapsed time from a decision being ready to a decision being made. This isolates approval design from execution, and it is the number that most reliably predicts whether a governance structure is helping or hindering.
If your measures only describe what happened last month, you are writing history, not managing an operation.
How to review them
Put the five numbers on one page, reviewed in twenty minutes, weekly, by the process owner — with the authority to change something before the next review. Any number that cannot be actioned within a week should not be on the page. The purpose of the cadence is not visibility. It is decision velocity.