Augment

Designing SaaS Dashboards People Actually Read

A dashboard is a set of answers to questions users already have. Start there, and most layout decisions get easy.

A dark analytics dashboard showing retention and usage charts
Photo by Luke Chesser on Unsplash, with an Augment halftone treatment
Executive Summary

Key Takeaways

  • List the five questions a user opens the dashboard to answer. Design for those, not for the data you have.
  • Lead with the few numbers that matter and let detail sit one click down.
  • Choose the chart for the question: compare, trend, part-to-whole, or distribution.
  • Design the empty, loading, and error states. They are what new users see first.

Start with questions, not widgets

Many dashboards are a pile of every available metric. They look busy and answer little. Instead, interview users and write down the questions they ask when they log in: Is anything broken? Are we on track? What changed since yesterday?

Each question becomes a block. If a metric does not answer a real question, it does not belong on the first screen.

Build a clear hierarchy

  • Top: two to four headline numbers with change versus the last period.
  • Middle: the trends and breakdowns that explain those numbers.
  • Bottom or drill-down: tables and detail for users who want to dig.

NN/g's complex-application heuristics stress keeping users oriented and reducing the memory load. A hierarchy like this does both.

Match the chart to the question

QuestionUseAvoid
How is it changing over time?Line chartPie chart
Which is biggest?Sorted bar chart3D charts
What share is each part?Stacked bar, or a pie with few slicesMore than five slices
How is it distributed?Histogram or box plotAverages alone
What is the exact value?A table or a big numberA chart with no labels

Make it usable at a glance

  • Label axes and units. Never make users guess.
  • Use color to carry meaning, such as status, and keep it consistent.
  • Show comparison: versus last week, target, or average.
  • Let users filter by date range and segment, and remember their choice.

Do not forget the first visit

A new account has no data. An empty dashboard of blank charts feels broken. Show sample data, a short explanation of what will appear, and the one action that will start filling it.

Frequently Asked Questions

Only as many as answer the user's real questions, usually a handful at the top, with detail available on demand.

Sources and further reading

  1. 10 Usability Heuristics Applied to Complex ApplicationsNielsen Norman Group · Published · Updated · Accessed
  2. Designing Empty States in Complex Applications: 3 GuidelinesNielsen Norman Group · Published · Updated · Accessed
  3. Atlassian Design SystemAtlassian · Undated page · Accessed

Credits

  • Written by Augment Editorial Team, Product design and engineering, Augment Lab.
  • Cover photo Photo by Luke Chesser on Unsplash, with an Augment halftone treatment, used under the Unsplash License.
  • Research Statistics and standards are cited from the sources above. Always check the original page for the latest version.

Augment Product Design

Ready to make your product clearer?

From first concept to go-live, we turn complex product ideas into clear, useful experiences.

Designing SaaS Dashboards People Actually Read | Augment. Lab