Designing Dashboards People Actually Read
Most dashboards are museums of data nobody visits. The discipline of designing for decisions — what to show, what to hide, and what to make impossible to miss.
Zara Ahmed
Design Lead
Ask most teams what their dashboard is for and they'll say 'so we can see the numbers.' That's a museum brief, not a product brief. Dashboards exist to support decisions, and every design choice should trace back to which decision a viewer is trying to make.
Decisions before data
List the five decisions your audience makes weekly: 'do we need to reorder stock?' 'which campaign is underperforming?' 'who's falling behind on follow-ups?' Each decision earns a widget. Everything else is clutter competing for attention.
The hierarchy of attention
- The one number that matters most — big, at the top
- Trends over time — the shape beats the latest point
- Anomalies surfaced, not buried: thresholds, color, alerts
- Details on demand, not on the first screen
What kills dashboards
Three killers: charts without context (a 5% drop is meaningless without a baseline), tables pretending to be summaries, and dashboards that require interpretation. If a user needs a meeting to understand it, it's a report, not a dashboard.
A good dashboard answers the question before the user asks it. A great one asks the question before the business feels the problem.