Of all SaaS dashboard design best practices, the first is to start from the decision a user makes each morning, not from the data you happen to have. A dashboard people open daily answers "is anything off, and where?" within seconds, shows a few numbers with a comparison beside each, and ends in a short list of things that need someone today. Everything else belongs in reports or drill-downs.
Stephen Few defines a dashboard as the most important information needed to reach an objective, arranged on one screen so it can be monitored at a glance. This guide is for SaaS founders and product leads building one, from metrics to accessibility, with a process and a checklist.
Start from the morning decision, not the data
The usual brief lists everything the database can count. That produces a screen people admire in the demo, then stop opening. Few saw this in 2006: flashy gauges delight on day one and are ignored once they fail to say what people need.
Write a short decision brief instead:
- Who opens it, and when: a founder first thing, a support lead at the start of a shift.
- The decision they make: step in on an account, move budget, ship a fix.
- What would change it: the few signals that would make them act differently.
- Where they go next: the screen or action the dashboard hands them to.
For a B2B founder, "do I need to step in anywhere today?" points to trials against normal, accounts with falling usage, failed payments and urgent tickets. It does not point to total users since launch.
Few describes monitoring as three moves: see the big picture, focus on what needs attention, then drill into what you need to act. Lay the screen out in that order.
Choosing metrics: leading, lagging and the few that matter
In Amplitude's terms, lagging indicators report what already happened (revenue, MRR, NPS), while leading indicators predict what is coming and move quickly (trial signups, error rate, load speed). A daily screen needs mostly leading indicators, because users can act on them today; lagging ones stay as smaller context.
| Metric | Type | Action when it moves |
|---|---|---|
| Trial signups against normal | Leading | Check campaigns and the signup flow |
| Activation of new accounts | Leading | Review onboarding drop-off |
| Error rate and load time | Leading | Escalate to engineering |
| Accounts with falling usage | Leading | Customer success reaches out |
| MRR, NPS | Lagging | Review weekly; rarely a same-day action |
Three of the 13 pitfalls in Few's paper apply to every metric:
- Give it context. A total means nothing until a target or prior period sits beside it.
- Show only the precision needed. $3.8M, not $3,848,305.93.
- Express it directly. If the gap to budget matters, show the variance (-10%), not two numbers to subtract.
Then run a cut test: write the action each metric triggers. If you cannot, it leaves the first screen.
Information hierarchy and the first five seconds
In a five-second test, a method NN/g teaches, people see a design briefly and say what they remember. On a dashboard you want "today is normal, except this one thing". If they recall the logo or a decorative chart, the hierarchy is wrong. Build it in four layers:

- A status line: one sentence summarising the state, as Apple's chart guidance suggests.
- A summary row: a few numbers, each with its comparison and direction.
- Trends: small line charts where shape matters more than value.
- An action list: rows that need someone today, with the action on each row.
Use position, size and contrast for importance, keep colour for exceptions, and always show when the data last updated. Clicking any tile should open the detail behind it with the user's filters intact.
For the action list, NN/g's table research names four jobs: finding, comparing, viewing or editing one record, and acting on several. A morning list needs a readable name in the first column, visible filters and batch actions.

Which chart answers which question
Cleveland and McGill's 1984 study ranked how accurately people decode graphs: position along a common scale first, angle lower, area and colour shading lower still. They concluded pie charts and divided bar charts needed rethinking, and NN/g's dashboard guidance agrees.

| Question | Use | Avoid |
|---|---|---|
| How has this changed over time? | Line chart | Stacked area |
| How do these items compare? | Bar chart, horizontal for long labels | Pie, donut, 3D |
| Are we on target? | Bullet graph | Gauge or dial |
| What ranks highest? | Sorted bar chart | Unsorted bars |
| How is the whole split? | One 100% bar or a short table | Pie with many slices |
| Do two measures move together? | Scatter plot | Two lines on two axes |
| What is the exact value? | Table | Any chart |
Few designed the bullet graph to replace gauges in a small space. And when people only need the data, Apple's guidance is to use a list or table.
Empty, loading and error states
A new account has no data, so the first screen most people see is the empty one. Design it first: one action, a preview of what will fill in, no rows of zeros. NN/g gives empty states three jobs: explain the status, teach the feature, offer a direct path. Getting a new account from sign-up to that first full screen is the subject of my SaaS onboarding design guide.
| State | What good looks like |
|---|---|
| First use | One setup action and a preview, never zeros |
| Filtered to nothing | "No results for this date range" and a clear-filters link |
| A true zero | "No failed payments today", not a blank card |
| Loading | Nothing under 1 second; a page skeleton or card spinner for 2 to 10 seconds; a progress bar beyond 10 |
| One module fails | An error inside that card, the last good value with its time, a retry |
| Stale data | A visible "updated" time and a warning past a set age |
The loading thresholds are NN/g's. Load each module on its own so one slow query never blanks the screen, and write errors in plain words with a fix, keeping the user's filters. States like these are where a design and its code most often part ways, so my design to code review checklist checks every one before release.
Alerts and thresholds people do not learn to ignore
Google's SRE book is blunt: every page should be actionable, and alerts should track symptoms users feel, not every cause. In hospitals, the Joint Commission estimated in 2013 that 85 to 99 percent of alarm signals need no clinical intervention, and its database held 98 alarm-related events in three and a half years, 80 of them deaths. Software is not intensive care, but alarm fatigue works the same way.
- Keep passive indicators on screen and save interrupting notifications for when someone must act; NN/g matches the method to the urgency.
- Set thresholds from the normal range and show bands (fine, watch, act), as a bullet graph does.
- Give every alert an owner and a next step.
- Require the condition to persist, so one spike does not page anyone.
- Prune the log. If an alert fired and nobody acted, change or delete it.
Personalisation and roles
Few argues a dashboard must be tailored to a person, group or function. NN/g separates personalisation (the system adapts) from customisation (the user does), and notes most users will not do the work of tweaking an interface. So ship strong role defaults: a founder, a sales lead and a support lead each get the first screen that answers their morning question.
On top, allow pinning, hiding and saved filters, but avoid a blank "build your own" canvas that hands the design work back to users. If you add AI summaries, show why each item is there; see my guide to shipping AI features people trust.
Mobile, dark mode and speed
Mobile is for checking. Stack the status line, summary row and action list, with trends a tap away. WCAG 2.2 Reflow asks that content work at 320 CSS pixels wide without two-way scrolling; data tables are exempt, their filters are not. Lock the first table column, as NN/g advises, and meet WCAG's 24 by 24 CSS pixel minimum for targets.
Dark mode needs its own palette. NN/g's review found light mode works better for most people with normal vision, while dark mode helps some with conditions such as cataracts, so offer a switch. Material Design recommends dark grey (#121212) over black, with desaturated accents. Chart colours tuned for white fail on dark grey, so recheck contrast.
Speed decides whether people return. Nielsen's limits: 0.1 seconds feels instant, 1 second keeps the flow of thought, 10 seconds is about the limit of attention. Core Web Vitals call a page good when Largest Contentful Paint is within 2.5 seconds and Interaction to Next Paint is 200 milliseconds or less, at the 75th percentile. Pre-aggregate the summary, show it first, reserve space for each card so late data does not shift the layout, and go real-time only when the decision needs it.
Accessible charts: colour blindness, contrast and tables
About 1 in 12 men have a colour vision deficiency (US National Eye Institute), and about 1 in 200 women (Colour Blind Awareness). Red-green is the most common type, so a red and green status pair is the worst way to carry meaning alone.
| Requirement | WCAG 2.2 | On a dashboard |
|---|---|---|
| Use of colour | 1.4.1 (A) | Arrows, signs or labels as well as colour |
| Text contrast | 1.4.3 (AA) | 4.5:1 for labels and numbers |
| Non-text contrast | 1.4.11 (AA) | 3:1 for lines, bars and slices you need to read |
| Text alternative | 1.1.1 (A) | A short description, with the data available |
| Status messages | 4.1.3 (AA) | "Data updated" announced without moving focus |
One nuance from the W3C: if a pie chart labels its values, the slices themselves do not need 3:1. Use a colour-blind-safe palette such as Okabe and Ito's, add markers or line styles, label lines directly instead of using a legend, and offer "view as table": the W3C's complex images tutorial recommends a short and a long description, which can be a data table. Then test in greyscale. In the US, accessibility is a legal risk too: UsableNet's 2025 count put New York first for ADA digital accessibility lawsuits, so my fintech product design in New York builds WCAG 2.2 AA into the components.
A step-by-step SaaS dashboard design process
- Write the decision brief: who, when, which decision, where next.
- Watch what users already open, export or ask for in Slack each morning.
- List candidate metrics and run the cut test.
- Sketch the hierarchy: status line, summary row, trends, action list.
- Choose charts from the question table.
- Design every module's empty, loading, error, stale and zero states.
- Define thresholds and alerts, each with an owner.
- Prototype with ugly real data: long names, zeros, outliers, gaps.
- Run a five-second test, then a task test such as "which account needs you today?"
- Check contrast, colour-only meaning, the table view and keyboard use.
- Ship the smallest version, track which modules get used, and trim. A good dashboard gets shorter as it gets older.
Dashboard design best practices: a review checklist
| Check | Pass looks like |
|---|---|
| Decision | The brief names the person and decision |
| Five seconds | Testers can say if today is normal and where to look |
| Context | Every headline number has a comparison |
| Charts | Bars, lines, bullet graphs, tables; no gauges or 3D |
| States | Empty, loading, error, stale and zero designed per module |
| Alerts | Each actionable, with an owner |
| Mobile | Works at 320 CSS pixels, actions first |
| Speed | Core Web Vitals "good" at the 75th percentile |
| Accessibility | Nothing by colour alone; 4.5:1 text, 3:1 marks |
Common mistakes to avoid
- Starting from the schema or the wish list. Every favourite number pushes the important ones down.
- Numbers without comparison. Few's second pitfall, still the most common.
- Gauges, dials and 3D. Decoration that encodes values with angle or volume.
- Red and green as the only signal. It fails many users and WCAG 1.4.1.
- Never trimming. If a module has not changed a decision in months, remove it.
Frequently asked questions
What makes a good SaaS dashboard?
It supports one named decision for one kind of user and answers "is anything off, and where?" within seconds. It shows a few headline numbers with comparisons, trends where shape matters, and a short list of items needing action. It has designed empty, loading and error states, a visible update time, and never relies on colour alone.
How many metrics should a dashboard show?
There is no magic number. The first screen should show only metrics that change the morning decision, usually a handful. Few points to the limits of short-term memory: people hold only a few chunks of information at once. Everything else belongs in drill-downs or reports. If a metric never triggers an action, cut it.
What is the difference between a dashboard and a report?
A dashboard is for monitoring: it shows at a glance what is happening and whether to act, and people open it often. A report is for analysis: it explains why, holds more detail and is read occasionally. Many failed dashboards are reports squeezed onto one screen.
Which chart types work best on a dashboard?
Bar charts to compare items, line charts for change over time, bullet graphs for progress against a target, and tables for exact values. Cleveland and McGill found people judge position and length more accurately than angle or area, which is why NN/g advises against pies, gauges and 3D on dashboards.
Should a SaaS dashboard update in real time?
Only if the decision happens in real time, such as dispatch or incident response. Most founder and manager dashboards support daily or weekly decisions, where a regularly refreshed snapshot is cheaper, faster and calmer; Few makes the same point. Either way, show when the data last updated.
How do I make dashboard charts accessible?
Follow WCAG 2.2: never use colour as the only signal (1.4.1), give text 4.5:1 contrast and chart marks 3:1 (1.4.3 and 1.4.11), and provide a text alternative (1.1.1). In practice: direct labels, arrows for up and down, a colour-blind-safe palette and a "view as table" option.
My recommendation
Start with the decision, not the chart library. Cut every metric that does not trigger an action, and design the empty, loading and error states before the busy screen. Then ship small and keep trimming: the dashboards people open every morning are short, fast and honest about what they do not know. Where screens like these are heading is in UI design trends for 2027. For real products sorted by the job they do, see dashboard design examples by job.
If you want help, this is the core of my product design work. A project starts with a free 30 minute intro call, then a written scope and one fixed quote, with no retainer. I work remotely, sharing part of your working day.
Sources and method
I opened every source on 1 and 2 October 2026; no currency conversion was needed. Hard evidence on what makes people return to a dashboard is thin, so treat the process as informed practice. The alarm figures come from hospital devices, not software.
- Stephen Few, "Dashboard Confusion", 20 March 2004: perceptualedge.com; "Common Pitfalls in Dashboard Design", February 2006: perceptualedge.com; bullet graph specification, 10 October 2013: perceptualedge.com
- Cleveland and McGill, "Graphical Perception", JASA, September 1984: jstor.org
- Nielsen Norman Group, dashboards, 18 June 2017: nngroup.com; data tables, 3 April 2022: nngroup.com; 5-second test, 20 April 2018: nngroup.com; empty states, 19 September 2021: nngroup.com; skeleton screens, 4 June 2023: nngroup.com
- Nielsen Norman Group, response times, 1 January 1993: nngroup.com; indicators and notifications, 17 January 2024: nngroup.com; customisation, 10 July 2016: nngroup.com; mobile tables, 17 September 2017: nngroup.com; dark mode, 2 February 2020: nngroup.com
- Amplitude, leading and lagging indicators, 9 July 2024: amplitude.com
- Google, Site Reliability Engineering, chapter 6, 2017: sre.google
- The Joint Commission, Sentinel Event Alert 50, 8 April 2013: jointcommission.org
- W3C, WCAG 2.2, 12 December 2024: w3.org; non-text contrast and reflow: w3.org, w3.org; complex images, 8 April 2026: w3.org
- US National Eye Institute, colour blindness, 5 November 2025: nei.nih.gov; Colour Blind Awareness, undated: colourblindawareness.org
- Okabe and Ito, Color Universal Design, 2002, revised 2008: jfly.uni-koeln.de
- Apple, Charting data, 23 September 2022: developer.apple.com
- Google, Material Design dark theme, undated: m2.material.io; web.dev, Web Vitals, 31 October 2024: web.dev
- UsableNet, 2025 Year-End Digital Accessibility Lawsuit Report (New York leads the nation in ADA digital accessibility lawsuits across federal and state courts; companies sued without being based in New York; eCommerce 70% of lawsuits; overlays did not reduce litigation), December 2025, read 5 October 2026: info.usablenet.com
Tags: Dashboards, SaaS, Product design, Data visualisation, Accessibility



