A good Power BI dashboard passes five tests: it answers one clear question, puts the key number top left, uses charts that suit the data, keeps colour and text consistent and loads in a few seconds. The 20-point checklist below covers all five, plus accessibility and testing, so you can review any report in ten minutes before it reaches your manager.
Picture the scene that makes this matter. A finance head opens a new dashboard in a Monday meeting, cannot find the revenue number in five seconds and gives up. The data was right; the design lost the room. If you have not built one yet, start with how to build your first Power BI dashboard, and to learn why design carries the message, read our piece on data storytelling.
The 20-Point Power BI Dashboard Design Checklist
| No. | Area | Check | Pass when |
|---|---|---|---|
| 1 | Purpose | The page answers one stated question | Title or subtitle says it |
| 2 | Audience | Written for one reader type | You can name the reader |
| 3 | Layout | Key KPIs are top left | The eye lands on them first |
| 4 | Layout | Content flows left to right, top to bottom | No visual hunting |
| 5 | Layout | Visuals are aligned to a grid | Equal spacing and edges |
| 6 | Volume | Five to eight visuals per page | Detail moved to drill-through |
| 7 | Charts | Right chart for each question | Bars for comparison, lines for time |
| 8 | Charts | No 3D, no decorative effects | Flat, clean visuals |
| 9 | Charts | Pie or donut has five slices or fewer | Otherwise use bars |
| 10 | Colour | Two or three main colours | One accent for alerts |
| 11 | Colour | Colour carries meaning consistently | Red always means bad |
| 12 | Text | One font family, sizes 10 pt and above | Titles larger than labels |
| 13 | Labels | Titles say what and for when | “Sales by region, FY 2026” |
| 14 | Labels | Units and currency are shown | Rupees, percent, crore, lakh |
| 15 | Interaction | Slicers are few and placed together | Reset or clear is possible |
| 16 | Accessibility | Contrast, alt text and tab order set | Keyboard users can navigate |
| 17 | Colour-blind | Palette avoids red and green only | Shape or label backs up colour |
| 18 | Speed | Page loads in a few seconds | Checked in Performance Analyzer |
| 19 | Accuracy | Key totals match the source | Spot-checked with Excel or SQL |
| 20 | Review | A new reader gets the message in five seconds | Tested with a real person |
How Should You Arrange the Page?
Use the way people read: top left to bottom right. Put the most important KPIs in a row at the top, trends in the middle and detail at the bottom. Group related visuals with whitespace, and use the same size for visuals that compare like with like. A background rectangle behind a group makes it look tidy without extra effort.
Beware the temptation to fill every pixel. White space is not wasted; it is what makes the numbers stand out.
Which Chart Should You Use for Which Question?
| Question | Use | Avoid |
|---|---|---|
| Compare categories | Bar or column chart, sorted | Pie with many slices |
| Show change over time | Line chart | Stacked area with many series |
| Show parts of a whole | Stacked bar, or donut with up to five parts | 3D pie |
| Show a distribution | Histogram or box plot | Table of raw values |
| Show relationship | Scatter plot | Dual-axis line charts |
| Show one key number | Card | Gauge with no scale |
| Look up exact values | Table or matrix | A chart that hides the numbers |
How Do You Use Colour Well?
Pick one base colour for normal data and one accent for exceptions. Use grey for context, so the eye goes to what matters. Keep meaning stable across pages: if blue means “actual” on page one, it should not mean “target” on page two. About 8 percent of men have some form of red-green colour blindness, so do not rely on red and green alone; add icons, labels or shapes. Use Power BI’s built-in colour-blind-friendly themes or a custom theme file to apply the same palette to every page.
What About Accessibility and Mobile?
Aim for text with a contrast ratio of at least 4.5 to 1 against its background, which is the WCAG guideline for normal text. Add alt text to visuals, set a logical tab order and avoid relying on hover-only information. Microsoft provides guidance on accessible reports. If managers read dashboards on phones, build a mobile layout in the Mobile view so the key cards are readable on a small screen.
How Do You Keep Dashboards Fast?
Slow reports lose viewers. Use Performance Analyzer in Desktop to see which visual takes longest. Cut unused columns and tables, prefer measures to calculated columns, reduce the number of visuals on a page, and avoid high-cardinality fields (such as transaction ID) in slicers. Use aggregated tables for very large data. If you work with large and mixed data sources, our modern data stack guide explains how to prepare data before it reaches Power BI.
How Do You Test That the Dashboard Works for Real People?
Run a five-second test. Show the page to someone who has not seen it and ask what the main message is. Then ask them to find one specific number. Note where they hesitate. Check that filters do not produce empty visuals, that blanks are handled and that titles update with slicers. Ask the data owner to sign off on key definitions such as “active customer”. Finally, record the refresh time and the data source on the page, so readers know how fresh the numbers are.





