Dashboard Design
Structure screens the way decisions read
A dashboard answers one question per screen, left-to-right: KPI header, trend context, then drillable slices. Structure, hierarchy and restraint beat decorations every time.
What you will learn
- Design a question-first layout
- Build KPI header + trend + breakdown hierarchy
- Apply restraint: fewer charts, deeper purpose
What is this?
Dashboard design is information architecture: a title announcing the question, KPI tiles summarizing the answer, a trend panel giving context, and segmentable breakdowns supporting drilldown. Navigation, filters and freshness are part of the design. The failure mode is the giant tile-the-floor 'everything board' that answers nothing.
Why do you need it?
- Decision-makers glance for 5 seconds; layout determines what they conclude.
- A question-first board states truth; a kitchen-sink board performs decoration.
- Consistent structure makes the same story readable every morning.
- Restraint reduces review friction and raises trust.
Mental model
An airplane cockpit instrument layout
Dashboard design
The cockpit isn't a wall of random gauges — primary instruments (altitude, speed, heading) sit center-top and read at a glance; secondary systems are organized and accessible. A dashboard's KPI band, trend spine and drilldown quadrants are that same deliberate hierarchy.
How it works
- Start with the decision: 'who decides what on this screen?'.
- Top band = key numbers (until 5), each with its metric, delta, and timestamp.
- Middle = the trend for the main metric (line or sparkline) — context, not decoration.
- Below = breakdowns by segment with filters that stay consistent.
- Every tile earns its place: if a chart doesn't change an action, cut it.
- Keep white space; hierarchy beats density.
The classic dashboard skeleton.
Examples
Layout in a comment
layout = { "row1": ["MAU", "NRR", "Churn"], # KPI tiles "row2": ["MAU trend (90d)"], # context spine "row3": ["New by channel", "Existing by plan"], # breakdowns}for row in layout: print(row)# Rule: every tile states why it's there, or it leavesThe board answers one question — 'is growth on track?' — with KPI tiles, trend spine, and two drill-down panels.
In production
- An exec revenue board shows ARR (tile), ARR trend (spine), then plans/geos breakdowns.
- A support board leads with tickets (tile), queue trend, then priority×team drilldown.
- A customer-success board answers 'which accounts need help?' from one segment panel.
Best practices
- One question per screen; multiple decisions = multiple tabs.
- Lead with the number, then the trend, then the why (breakdowns).
- Global filters apply consistently across all panels.
- Show freshness and units on every tile.
Common mistakes
- Forty tiles answering ninety questions — a wall no one reads.
- No trend context: a 5% delta alone misleads more than it informs.
- Inconsistent colors/filters per panel breaking cross-comparison.
- Dashboards as decoration with no owner or refresh SLA.
Debugging tips
- If reviewers can't name the screen's question, the layout failed — restructure.
- A 12-tile screen: rank tiles by decision impact and cut the bottom half.
- Trends disagreeing with the KPI tile → check the time grain and filters.
- Dashboard 'look green but business is red' → metric definition, not layout.
Interview checkpoint
Hands-on lab
- Write the screen's decision question
- Define KPI tiles with trend context
- Render a three-row prototype
Sketch and Build a Question-First Board
30 min · intermediate
Quick quiz
The top band of an effective dashboard shows:
Every tile must change an action or leave the board.