In this article
Before you start
This page is one step of the data analyst interview path. Most dashboard numbers come from queries, so the SQL interview guide is the best companion.
Why interviewers ask this
A dashboard prompt, such as "how would you design a dashboard for a sales team?", has no single right chart, so it shows how you think before you open a tool. A weak answer lists charts: a map, a pie, a table of everything. A strong answer asks who looks at the page, which decision they make from it and how often, and only then chooses numbers and shapes.
The prompt also separates people who know the data from people who can communicate it. Tool documentation from Tableau and Microsoft starts from the same place, purpose and audience, so an answer built on that order matches what the vendors teach. Expect follow-ups on chart choice, color, filters and speed, which the steps below answer in turn.
Dashboard design from first principles
- Dashboard
- A dashboard is a single-page collection of data visualizations that gives a named audience at-a-glance information on which they can act quickly, built as an overview of the current state of the data first, with exploration secondary.
- Key performance indicator
- A key performance indicator (KPI) is a single measured number, such as revenue against target, that a dashboard shows to tell its audience whether a goal is being met, chosen because it drives a decision the audience actually makes.
- Preattentive attribute
- A preattentive attribute is a visual feature, such as length, area, angle, position or color, that the eye reads with almost no conscious effort, so charts built on the strongest attributes can be compared quickly and accurately, which makes chart choice a perception decision and not a style one.
In plain words
Think of a car dashboard. The driver glances at speed and fuel, then looks back at the road. The page is built for a glance. A glance-first page drops detail on purpose, because every extra number slows the reading of the important ones. Every gauge is there because the driver makes a decision from it. The analogy breaks in two places. A car maker fixes the gauges, while you choose every one. A driver knows what each gauge means, while your audience may not.
In one precise sentence, a good dashboard shows the few numbers an audience needs, in shapes the eye reads fastest, in the order people scan a page.
Step 1: Name the audience, the decision and the handful of KPIs
A dashboard design starts with the audience and the decision, because the same data needs a different page for different people. Tableau's guidance starts from the dashboard's main purpose and places the most important view at the top left. Microsoft lists the questions to ask: how the audience uses the dashboard, which metrics drive their decisions and what information they need. Also ask where the data comes from and how often it refreshes, and agree one definition for each metric so everyone reads one source of truth.
Input: an audience and a decision. Output: a short list of KPIs. Next, fix the type. An operational dashboard is a dashboard for time-sensitive tasks, such as server availability or customer-service calls, fed by continuously updating data. An analytical dashboard is a dashboard for analysis and decision-making with less time pressure, such as a sales view updated daily (Nielsen Norman Group, 2017). The result is an overview, so detail lives in the underlying reports. You now know what the page must say, which is the input to the chart choice.
Step 2: Pick the chart by what the eye compares fastest
Length and position carry quantity best, so bars and lines come first. Nielsen Norman Group explains that besides length, the preattentive features include area, angle, position and color, and that length and position make charts easy to compare. Area and angle, the basis of pie, donut and gauge charts, are weaker for quick, accurate comparison.
Microsoft agrees that bar and column charts compare values better because people can compare values side by side. A line chart suits a trend. Nielsen Norman Group also warns that color should not communicate quantitative magnitude, since up to 4.5% of people have some form of color blindness (Nielsen Norman Group, 2017).
Input: one KPI and the question it answers. Output: a chart whose main channel is length or position. If you want to draw attention to the highest or lowest value, sort by the measure. This is the part of the answer the interviewer pushes on, so say the reason, not just the chart name.
Step 3: Lay out the page from the top left and keep it to a few views
Put the highest-level data at the top left and keep two or three views. Microsoft recommends placing the highest level of data at the top left and adding detail in the direction the audience reads. Tableau notes that most viewers scan web content starting at the top left, and that it is a good idea to limit a dashboard to two or three views.
Because dashboards show important information at a glance, having all the tiles on one screen is best. If the story outgrows two or three views, split it into more dashboards instead of adding more charts to one.
Input: the KPI list from step 1 and the charts from step 2. Output: a one-screen layout with the headline number first. A good layout makes the answer to "are we on target?" visible before anyone reads a label.
Step 4: Keep it fast and readable with few filters and short numbers
Every filter can trigger a query, so filters cost speed: the dashboard must fetch each filter's options and re-run its views when a choice changes, so adding many can make a page slow to render. Tableau adds that too many views can also hurt performance after publishing.
Readability has its own rules. Microsoft advises showing no more than three or four numerals, so "3.4 million" reads better than "3,400,000". It also advises keeping time frames consistent and avoiding large and small measures on the same scale (Microsoft Learn, 2025).
Input: a working layout. Output: a page that loads quickly and reads at a glance. You now have the whole design: audience, chart, layout and speed.
Step-by-step description
- Name the audience and the decision first.
- Bars and lines carry quantity best.
- Highest-level data goes top left.
- Every filter can cost a query.
- Length and position carry quantity best, so bars and lines come first.
- Put the highest-level data at the top left and keep two or three views.
- Every filter can trigger a query, so filters cost speed.
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →Worked example
A sales dashboard for four regions shows the method. The targets and actuals below are illustrative, in thousand orders, and the percentages are computed from them.1 The headline KPI is the share of target reached, because the audience decides where to send help.
| Region | Target (thousand orders) | Actual (thousand orders) | Variance (thousand orders) | Share of target |
|---|---|---|---|---|
| North | 120 | 132 | +12 | 110% |
| East | 90 | 90 | 0 | 100% |
| South | 100 | 91 | -9 | 91% |
| West | 80 | 68 | -12 | 85% |
| Total | 390 | 381 | -9 | 97.7% |
North reached 110 percent of its target and West reached 85 percent.1 Sorting the bars by the measure puts the weakest region last, so the eye lands on it. Because bars use length, a viewer can compare four regions without reading a number.
Text description of the diagram
- North reached 110 percent of its target and West reached 85 percent.
- Sorting the bars by the measure puts the weakest region last.
The same rules apply when the KPIs come from a retrieval-augmented generation (RAG) system, an AI setup that retrieves chunks (short passages of text) and writes an answer from them. Both metrics below come from the Ragas framework (Es et al., 2023). Faithfulness is a metric that measures how factually consistent a response is with the retrieved context, from 0 to 1, computed as claims supported by the context divided by total claims (Ragas faithfulness page). If 4 of 5 claims are supported, faithfulness is 0.8 (illustrative).1
Context precision is a metric that evaluates a retriever's ability to rank relevant chunks higher than irrelevant ones (Ragas context precision page). With the Ragas formula, a ranking of relevant, relevant, irrelevant, irrelevant scores 1.0, and the same chunks in the reverse order score 0.4167 (illustrative).1 A dashboard would show each as a line over time against a threshold.
Trade-offs and edge cases
The two dashboard types differ in what they optimize, and the answer changes with them. Nielsen Norman Group describes the split below.
| Dimension | Operational dashboard | Analytical dashboard |
|---|---|---|
| Time pressure | time-sensitive tasks | less time sensitivity |
| Typical subject | server availability, patient vitals, customer-service calls | a sales view updated daily |
| Data refresh | continuously updating | on a schedule such as daily |
Pie charts are not banned. Microsoft says pie charts are best when there are fewer than eight categories, and Nielsen Norman Group says treemaps are not appropriate for simple, actionable dashboards. Bar charts compare values side by side, so they remain the default for comparing categories.
Text description of the diagram
- Bar charts compare values side by side.
- Pie charts are best when there are fewer than eight categories.
Two more edge cases. Filters help users choose what a view shows, but each one has a cost, so keep only those the audience needs. Detail that does not drive a decision belongs in a report behind the dashboard, which is how a one-screen overview stays honest about its job.
How to answer it in an interview
How would you design a dashboard for a sales team?
I start by asking who uses it and which decision they make from it, because that decides everything else. Then I choose a handful of key performance indicators, put the highest-level one at the top left, and use bars and lines because people compare length and position fastest. I keep to two or three views, sort by the measure, round numbers so they are short to read, and add only the filters people truly need, since each filter can trigger a query and slow the page. Detail goes in underlying reports, not on the dashboard. Finally I check it on the smallest screen the audience uses.
The spoken structure: say the audience and decision, then the KPIs, then the chart reason, then the layout, then the cost of filters.
Common mistakes
- "I would put every metric we have on the page." (wrong) A dashboard is an overview for monitoring, not an exploration tool. (right) "I pick the few KPIs that drive the audience's decisions and link to reports for detail."
- "I would use a different color for every region and a 3D pie." (wrong) Color is a weak channel for magnitude and fails some viewers. (right) "I use sorted bars, and color only to highlight one item, never as the only cue."
- "Pie charts are always wrong." (wrong) They suit part-to-whole views with fewer than eight categories. (right) "I avoid pie charts for comparison and use them only for a few slices."
- "More filters make it more flexible." (wrong) Each filter can add a query and slow the page. (right) "I keep the filters the audience needs and drop the rest."
Follow-up questions
How do you design a dashboard for tablets and phones?
Use fewer tiles, because Microsoft notes that fewer tiles read better on tablets and phones. Tableau notes that a dashboard designed at 1300 x 700 pixels with automatic sizing is resized for smaller displays and can end up with scrunched views or scrollbars, so use Range sizing or a device layout and test the smallest screen.
How do you make a dashboard work for color-blind viewers?
Do not let color be the only cue. Up to 4.5% of people have some form of color blindness (Nielsen Norman Group, 2017), so encode magnitude with length or position and add labels or order to any grouping.
What do you do when the dashboard is correct but nobody uses it?
Go back to step 1. Ask the audience how they use it, which metrics drive their decisions and what information they need, then remove tiles that answer none of those questions. Measure adoption with usage logs before and after the change, so you know whether the fix worked.
How would you show a metric that suddenly dropped?
Show the KPI at the top left against its target and a previous period, and link to a breakdown by segment. The metric dropped case walks through the investigation itself.
What would a RAG evaluation dashboard show?
A RAG evaluation dashboard is a dashboard whose KPIs are retrieval and generation metrics. Generation metrics include faithfulness and answer relevance, and retrieval metrics include context precision and context recall (arXiv 2601.22025). Design it with the same rules: few views, each metric as a line over time against a threshold.
How do you show an experiment result on a dashboard?
Show the difference between groups with its uncertainty, not a bare lift number. The A/B test analysis questions cover how to read the result. For tool-specific rounds, see the Tableau developer questions and the Excel interview questions.
- Start from the audience and the decision, then choose a few KPIs.
- Length and position carry quantity best, so bars and lines come first.
- Put the highest-level data at the top left and keep two or three views.
- Every filter can cost a query, and short numbers read faster.
- A RAG evaluation dashboard follows the same rules, with metrics over time against a threshold.
Sources
- Dashboards: Making Charts and Graphs Easier to Understand — Nielsen Norman Group (Laubheimer), 18 Jun 2017
- Tips for designing a great Power BI dashboard — Microsoft Learn, 20 Oct 2025
- Best Practices for Effective Dashboards — Tableau Help, 26 Oct 2026
- RAGAS: Automated Evaluation of Retrieval Augmented Generation (arXiv 2309.15217) — arXiv (Es et al.), 26 Sep 2023
- Faithfulness (Ragas documentation) — Ragas faithfulness page, 26 Oct 2026
- Context Precision (Ragas documentation) — Ragas context precision page, 26 Oct 2026
- Retrieval-Augmented Generation metric summary (arXiv 2601.22025) — arXiv, 1 Jan 2026
