The BI Usefulness Test
A dashboard is useful only if it survives the full chain: a real decision, a real user, a possible action, an explanation, a drill-down, and a fit with how work actually happens.
A dashboard is not useful because it has charts. It is useful when someone can look at it, understand what changed, explain why it changed, and decide what to do next.
The chain#
Run any dashboard through six links. It is only as useful as its weakest one.
- Decision — Is there a specific decision this exists to support? "Awareness" is not a decision.
- User — Is there a named person who makes that decision and will actually look here?
- Action — Can that person do something different based on what they see? If every value leads to the same behavior, the chart is decorative.
- Explain — When the number moves, can they explain why without opening a ticket?
- Drill — Can they go from the headline to the underlying records that produced it?
- Workflow — Does looking here fit the rhythm of their actual week, or is it a place they have to remember to visit?
The failure mode#
Most "BI debt" is dashboards that pass the first link and fail the rest: a decision exists in theory, but no named user, no possible action, no path to explanation. They accumulate because building a chart is easy and retiring one feels rude.
A metric with no decision attached is not a metric. It is a number wearing a costume.
How to use it#
Before building, walk the chain forward and refuse to start until all six links are real. Before retiring, walk it backward: a dashboard that fails user or action is a candidate for deletion, and deleting it is a feature, not a loss.