Dashboards fail in a predictable way: they show everything that can be measured instead of what someone needs to decide. A good dashboard is not a collection of charts. It is an answer to a few questions, available at a glance. Here is how to design one.
1. Start from decisions, not data
Before any layout, write down who uses the dashboard and the three to five questions they ask it. "Are sales on target this month?" "Which accounts need attention today?" Every element on the screen should answer one of those questions. If it does not, it goes on a detail page.
2. Put the key numbers first
The top row should hold the few numbers that matter most, each with context:
- The value, large and easy to read.
- A comparison: versus last period, versus target.
- A direction: up or down, with colour used carefully.
A number without context forces the user to remember what normal looks like.
3. Choose simple charts
- Line charts for trends over time.
- Bar charts for comparing categories.
- Single numbers with sparklines for key metrics.
- Tables when users need exact values.
Avoid pie charts with many slices, 3D effects and dual axes, which are easy to misread. Label directly on the chart where you can, rather than relying on a legend.
4. Build a clear hierarchy
Use size and position to show importance: the most important at the top left, supporting detail below and to the right. Group related items in cards with clear headings. Use whitespace generously; dense is fine, cramped is not.
5. Use colour with restraint
Keep most of the dashboard neutral and reserve strong colour for meaning: status, alerts, the one series that matters. Do not rely on red and green alone, which many people cannot tell apart; add icons or labels. See how to choose a color palette for UI.
6. Design every state
- Loading: skeleton cards rather than spinners.
- Empty: explain what will appear and how to get data in. See empty state design.
- Error: say what failed and offer a retry.
- Partial data: show what you have and mark what is missing.
7. Make filters obvious
Date range and key filters belong at the top, always visible, with the current selection clearly shown. Users should never wonder what period or segment they are looking at.
8. Plan for density and scale
Real data is messier than mockups: long names, huge numbers, zero values, hundreds of rows. Test with realistic data early. Tables need sticky headers, sorting and sensible column widths.
9. Adapt for mobile
On phones, prioritise the two or three most important numbers in a single column, turn wide tables into summaries or cards, and let users tap through to detail.
Where to find good dashboard examples
Real products are better references than concept shots, which usually use perfect data. Study analytics tools, admin panels and finance apps you use, and enterprise design systems like IBM Carbon, covered in design system examples. Save the dashboards that handle hard problems well, with a note on what they solve. In GetRef, the numbers and labels inside each screenshot are searchable, so "dashboard with date filter and sparklines" finds your examples. See also UI design patterns.
Common questions
- What makes a good dashboard design?
- A good dashboard answers a few specific questions at a glance. It shows the most important numbers first with context such as trends or targets, uses simple charts, keeps a clear visual hierarchy, and lets users drill into details only when they need them.
- How many metrics should a dashboard show?
- As few as answer the user question, often five to nine key items on the first screen. More detail can live one click away. A dashboard that shows everything usually communicates nothing.
- What charts are best for dashboards?
- Line charts for trends over time, bar charts for comparing categories, single big numbers with a change indicator for key metrics, and tables for exact values. Avoid pie charts with many slices and 3D charts.
- How do I design a dashboard for mobile?
- Prioritise ruthlessly: show the two or three most important numbers first in a single column, turn wide tables into cards or summaries, and let users tap through to detail screens.
