Ask an organisation how many dashboards it has and the number is usually large. Ask how many were opened this week and the number collapses. The gap is not a tooling problem.
A dashboard is an answer, so start with the question
Dashboards that survive were commissioned to settle a specific recurring argument — is the queue growing, are we going to miss the SLA, which region is dragging the average. Dashboards that die were commissioned to "give visibility".
If you cannot name the decision a view supports and the person who makes it, you are building a report, not a tool.
Design for the glance
The person opening an operational view has seconds and a question. Three things follow:
- Lead with the exception. What needs attention, not what is fine.
- Encode state in form as well as number. Colour and shape are read faster than digits.
- Make the next step available. A number that identifies a problem should link to the thing that fixes it.
Trust is the real dependency
A dashboard is abandoned the first time someone finds a number they can disprove. Reconciliation against the source of truth, visible freshness timestamps and honest handling of missing data matter more than the visual design.
The test
Six weeks after launch, check who opened it. If the answer is the team that built it, the project did not land — and the fix is a conversation about decisions, not a redesign.
