Dashboard Building โ 1 Complete Dashboard
Turn your analysis into a decision tool โ KPIs, the right charts, clean layout, and a story a stakeholder can act on in seconds.
Learning Objectives
- Explain what a KPI is and why it anchors a dashboard.
- List the key elements of a dashboard: KPI cards, charts, filters/slicers.
- Apply the four design principles: purpose, audience, layout, interactivity.
- Choose the right chart for each question.
- Explain the difference between visualization and data storytelling.
1. What a Dashboard Is & Why
A dashboard is a single page that shows the most important metrics for a decision โ at a glance, so stakeholders don't have to dig through raw data. A good dashboard answers "how are we doing?" in seconds.
2. KPIs โ Key Performance Indicators
A KPI is a measurable value that shows how well a goal is being achieved โ like total sales, churn rate, or average order value. KPIs are the "big numbers" at the top of a dashboard.
3. The Key Elements of a Dashboard
| Element | Purpose |
|---|---|
| KPI cards | the headline numbers (total sales, churn %) |
| Charts | trends, comparisons, distributions |
| Filters / Slicers | let users slice by region, date, segment |
| Title / context | what the dashboard is about and the time period |
4. The Four Design Principles
Before you place a single chart, answer these (from Tableau's own best practices):
- Purpose โ what decision should this dashboard support?
- Audience โ who will use it, and what do they already know?
- Layout โ most important things first, top-left.
- Interactivity โ slicers/filters let users explore on their own.
5. Choosing the Right Chart
| Question | Chart |
|---|---|
| How is a metric trending over time? | line chart |
| How do categories compare? | bar / column chart |
| What's the share of a whole? | pie / doughnut |
| What's the distribution? | histogram / boxplot |
| How are two numbers related? | scatter plot |
6. Data Storytelling
Visualization shows the data; data storytelling adds context and a narrative โ the "what happened, why it matters, and what to do" around the chart. It's what turns a chart into a decision.
7. Building a Complete Dashboard โ a Recipe
- Define purpose & KPIs โ e.g. "help the sales manager spot regional problems."
- Prepare data โ import and clean it (Power Query / Tableau Prep).
- Add KPI cards โ total sales, orders, avg order value, churn %.
- Add trend & comparison charts โ sales over time, sales by region.
- Add slicers โ region, date, product.
- Add a title and one-sentence takeaway โ the story.
8. Interview Questions (with Model Answers)
The dashboard questions interviewers ask. Self-test before revealing.
IQ1. What is a KPI?
Model answer: "A Key Performance Indicator is a measurable value tied to a business goal โ like revenue, churn rate, or conversion. I pick KPIs after understanding what decision the dashboard supports."
IQ2. What are the key elements of a dashboard?
Model answer: "KPI cards for the headline numbers, charts for trends and comparisons, and filters/slicers for interactivity โ plus a clear title and context."
IQ3. Walk me through your dashboard-building process.
Model answer: "First I define the purpose and audience, then choose KPIs, prepare the data, add KPI cards and charts, add slicers for interactivity, and finish with a one-line takeaway."
IQ4. What design principles do you follow?
Model answer: "Purpose, audience, layout, and interactivity. I put the most important KPI top-left, keep the layout clean and focused, and let users explore with slicers."
IQ5. How do you decide which chart to use?
Model answer: "I match the chart to the question โ line for trend, bar for comparison, pie for share, histogram for distribution, scatter for relationships."
IQ6. What's the difference between data visualization and data storytelling?
Model answer: "Visualization shows the data; storytelling adds context and a narrative โ what happened, why it matters, and what to do. It turns a chart into a decision."
IQ7. What is a slicer, and why use it?
Model answer: "A slicer is an interactive filter โ buttons that let users slice the dashboard by region, date, or segment. It makes the dashboard self-service instead of static."
IQ8. How do you make a dashboard stakeholder-friendly?
Model answer: "Keep the key number obvious, use clear charts, add labels and context, avoid clutter, and write a plain-English takeaway so the audience doesn't have to hunt for the insight."
IQ9. What's the most important thing to establish before building a dashboard?
Model answer: "Its purpose and audience. If I don't know what decision it supports and who will use it, I'll build the wrong thing โ so I always clarify that first."
Hands-On Project: Design a Sales Dashboard
Plan (and, if you have Power BI/Tableau, build) a sales dashboard.
Steps
- Write down the purpose and audience in one sentence.
- List 4 KPIs for a sales manager.
- Choose 3 charts and explain why each one.
- Decide which slicers to include.
- Write the one-line takeaway the dashboard should communicate.
View Solution / Walkthrough
- Purpose: "Help the sales manager spot regional performance problems."
- KPIs: Total Sales, Orders, Average Order Value, Sales vs Target %.
- Charts: line (sales over time), bar (sales by region), pie (sales by product category).
- Slicers: Region, Date range, Product category.
- Takeaway: "South region is underperforming due to a product stock-out โ restock to recover."
Key Takeaways
A KPI is a metric tied to a business goal โ pick it after knowing the purpose.
Design by purpose, audience, layout, and interactivity.
Most important KPI goes top-left; keep the layout clean.
Match the chart to the question (trend/compare/share/distribution/relationship).
Storytelling adds the "why and what to do" โ that's what drives action.
Objective Questions โ Test Your Understanding
Q1. What does KPI stand for?
Q2. Which dashboard element lets users filter interactively?
Q3. What should you establish FIRST before building a dashboard?
Q4. Which element shows a single headline number like total sales?
Q5. What does data storytelling add beyond plain visualization?