A small set of measures someone acts on — and the reason most dashboards are opened twice and abandoned.
A KPI dashboard presents a small number of key performance indicators for a specific role, in one view, with the ability to drill from a figure to the transactions behind it. The defining constraints are that it is role-specific and small. A dashboard showing forty metrics to everyone is a report nobody reads.
Dashboards fail for a consistent reason: they are built to display what is available rather than to answer what a particular person decides each week. If a measure does not change anybody's action, it is decoration. And a figure that cannot be drilled into is not actionable — the first question anyone asks about a bad number is which transactions caused it.
What does this person decide weekly? The measures follow from that, not from what the database contains.
Five to eight per role. More than that and attention disperses across all of them.
Against target, against last period, or against a trend. A number alone cannot be judged.
One click from the figure to the underlying documents. Without it the dashboard raises questions it cannot answer.
Centrally, so every view of revenue or margin means the same thing.
An executive dashboard is built with 34 metrics across six categories. It is comprehensive, visually impressive, and within two months nobody opens it.
The failure is that 34 numbers with no hierarchy demand that the reader decide what matters, every time. Without thresholds, nothing stands out. Without ownership, no number implies an action. Without drill-down, a concerning figure cannot be investigated without asking someone. The dashboard reports; it does not prompt.
A rebuild with six metrics — each tied to a stated objective, each with a target, a threshold and a named owner, each clickable through to the underlying records — gets used daily. The other 28 numbers are not lost; they live one level down, available when a top-level measure prompts a question. The principle is that a dashboard's job is to direct attention, and a screen where everything is visible directs attention nowhere.
| Term | What it means |
|---|---|
| KPI | A measure tied to an objective, with a target and an owner. Without those it is just a number. |
| Leading indicator | A measure that predicts an outcome, so there is still time to act. |
| Lagging indicator | A measure that reports an outcome after it has happened. |
| Threshold | The level at which a measure demands attention, defined in advance rather than judged. |
| Drill-down | Moving from a summary number to the records behind it, which is what makes a dashboard actionable. |
A dashboard serving every role serves none. Build per role.
If a figure never changes a decision, remove it. Its presence dilutes the ones that matter.
A figure that cannot be investigated gets ignored once it is first disbelieved.
Totals that only ever go up look reassuring and tell you nothing about performance.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Dashboard usage | Who opens it and how often. The honest verdict on whether it is useful. | |
| Metrics with a named owner | Measures nobody owns produce no action regardless of how they move. | |
| Drill-down usage | Whether people investigate or merely glance. Low drill-down suggests the numbers are not trusted. | |
| Time from data event to dashboard | Latency against decision need, which is often over-specified. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.