Hierarchy is read in milliseconds, before comprehension starts
A user opening a dashboard doesn't read top to bottom like a document. Their eye jumps to what looks biggest, boldest and highest-contrast first — a KPI number, an alert, a headline metric — and only then reads the supporting labels around it. Typography is doing that sorting work before comprehension even begins.
When every piece of text on a dashboard is roughly the same size and weight, that sorting fails, and the user has to read everything to figure out what matters — exactly the opposite of what a dashboard is for.
Building a hierarchy with a small type scale
Five or six sizes are enough
A KPI value, a section heading, a card title, body text, a caption, a label — that's usually the whole hierarchy a dashboard needs. More sizes than that dilutes the signal each one carries.
Weight does more work than size alone
A bold 14px label can outrank a regular-weight 18px one. Combining size and weight gives more distinct hierarchy levels than size changes by themselves.
The biggest number on a card should be the KPI, always
The metric value should visually dominate its card — larger and heavier than its own label. A stat card where the label is as prominent as the number has its hierarchy backwards.
Muted color is a hierarchy tool, not just a style choice
Secondary text at 60-70% opacity or a muted gray recedes without needing to shrink in size — useful when space is tight and a smaller size would hurt legibility.
Tabular numerals for anything meant to be compared
Numbers in a column need a monospaced or tabular-figure variant so digits align vertically — proportional numerals make columns of figures visibly harder to scan and compare.
Never rely on color alone to rank importance
Color-blind users and grayscale printing both lose a hierarchy built on hue alone. Size and weight should carry the ranking; color reinforces it.
Test it with the five-second glance
Show the dashboard to someone for five seconds, then ask what they remember. If they can name the one or two things that actually matter — revenue is down, three tasks are overdue — the hierarchy is working. If they describe the layout instead of the content, the type scale isn't doing its job yet, no matter how polished the individual components look.
The takeaway
A small, deliberate type scale — five or six sizes, weight doing as much work as size, muted color for secondary text, tabular numerals for comparison — tells a dashboard user what matters before they've read a single word. Test it with a five-second glance: if they remember the right thing, the hierarchy is real.
Let's talk about your productRelated reading
Visual Design · Hierarchy
Contrast, Weight and Whitespace: The Three Levers of Visual Hierarchy
Visual Design · Spacing
Spacing Systems: Why "It Looks Off" Is Almost Always a Grid Problem
UX · Reading Behavior
Designing for the Second Glance: What Users Actually Scan vs. Read
See this typographic hierarchy applied in production on the Rota case study.