Decision First
What this screen is for, before which charts exist.
Most dashboards are built from what the data warehouse can produce rather than from what anyone needs to decide, so they become inventories of available metrics. Dashboard UX design starts from the opposite end: what decision is this screen for, what would change it, and what can therefore be left off.
A dashboard nobody acts on is a report with a refresh button.
What this screen is for, before which charts exist.
What is abnormal, surfaced — not twelve equal tiles.
A number without a baseline cannot be interpreted.
From "something is wrong" to "here is what".
Removing charts is usually what makes a dashboard useful.
Four reasons, and all four are design decisions.
Discuss Your Dashboard →Twelve tiles of the same size, so nothing stands out.
A number with nothing to compare it to means nothing.
Something is wrong and the screen offers no way to investigate.
Assembled from what exists rather than what is needed.
The decision, the hierarchy, and the route from signal to cause.
For internal tools generally, see B2B UX design.
Ask what would change as a result of looking. If nothing, the chart does not belong.
What action this screen supports.
Only those that would change the decision.
Prominence by consequence, not by tile grid.
From anomaly to cause.
The charts nobody uses, which is usually most of them.
Every additional chart reduces the attention available for the ones that matter.
Someone asks for a metric, it is added, and it is never removed. Requests are cheap to grant and there is no cost visible at the moment of adding.
The cost is real and diffuse: each new tile takes a share of the screen and a share of the reader's attention, and the important numbers get harder to find.
A useful discipline is that adding a chart requires nominating one to remove. It forces the comparison that additive requests never do.
Because nobody knows whether 847 is good. Interpretation requires a comparison — last week, last year, the target, the usual range.
A dashboard of bare figures makes every reader do that work from memory, which means most of them do it badly or not at all.
Showing the comparison alongside the number, and marking what is outside the normal range, is what turns a display of data into something someone can act on.







Dashboard UX design structures data screens around the decision they support — selecting metrics that would change that decision, directing attention to anomalies, and providing a path from signal to cause.
Usually because everything on it looks equally important, the numbers have no baseline to compare against, and noticing a problem offers no way to investigate it.
Fewer than it does. A useful rule is that adding a chart requires nominating one to remove, which forces the comparison that additive requests never do.
Practically, yes. A bare figure cannot be interpreted — nobody knows whether 847 is good without a baseline, a trend or a target alongside it.
Show much less. A phone can carry a few critical indicators and an alert; attempting the full desktop dashboard on a small screen produces something nobody reads.
Still deciding if dashboard ux design is right for you?
Talk to UsSomeone asks for a metric on the dashboard. It exists in the warehouse, the query is simple, and adding a tile takes an afternoon. There is no reason to refuse.
What is not visible at that moment is the cost, because it lands somewhere else: on every future reader, who now has one more thing competing for the attention that should have gone to the number that mattered.
Twenty such decisions later, the dashboard contains everything and communicates nothing — and every individual addition was reasonable.
Send us your dashboard and tell us who uses it. We will identify which metrics support a decision and which are taking up attention.
