Test your eye.
Ten real Power BI visuals built from the HR data, each with problems in it. Look, decide what you'd fix, then open the answer.
Look, decide, then open the answer.
- Look for five seconds. Can you say the message out loud? If not, that's the first problem.
- List what you'd fix. Most visuals here have three to five problems. Write them down before you peek.
- Open the answer. Each problem names the rule it breaks, with a link to that rule, and the fixed version is underneath.
Every number comes from the HR Dataset: 301 employees, hired 2006-2016. 102 have left (34%), counting voluntary exits and terminations for cause.
A pay chart, straight from the Fields pane.
This visual is headed for a presentation page about pay. What would you fix?
Show the answer: five problems
- A field-name title. "Average of Pay Rate by Department" names the data, not the finding. Rule 15, Titles.
- Alphabetical order. The ranking is the point, and alphabetical order hides it. Rule 9.
- No unit, two decimals. "31.90" of what? Dollars an hour, to one decimal. Rule 14.
- Labels and an axis. They say the same thing twice, and the axis titles repeat the chart title. Rule 11.
- Nothing to look at. Every column is the same blue. Rule 4.
Fixed: sorted, in dollars, with the two departments the title compares in colour. Executive Office is one person, and the subtitle says so.
Where do hires come from? Try reading it from this.
The question is which hiring sources bring in the most people. What would you fix?
Show the answer: four problems
- 22 slices. Nobody can rank angles that small. A pie works for two or three parts of a whole. Pie and donut charts, Rule 3.
- A 22-item legend. The reader's eye goes back and forth between slice and key for every source. Rule 10.
- 22 colours that mean nothing. Colour should point at the answer. Rule 4.
- No numbers and a field-name title. The reader can't tell that the top two sources bring in 60 people. Rule 15.
Fixed: a sorted bar of the top eight, with the other 14 sources grouped at the bottom, where "other" always goes.
The chart is fine. What about the text box?
A presentation page about hiring sources. It shows sources with at least 10 hires, so no rate rests on one or two people. What would you fix?
Show the answer: five problems
- The callout describes the chart. "This chart shows…" adds nothing. A callout says what it means and what to do. Callouts.
- It's far from the evidence. It sits in a wide box under the chart, away from the referral bar it should explain. Put it beside that bar. Callouts.
- Its colour doesn't match. The heading is orange, the highlighted bar is blue, so nothing links words to data. Rule 16.
- No comparison. Is 12.90% good? The company rate (34%) belongs on the chart. Rule 5.
- A label title and two-decimal rates. Titles, Rule 14.
Fixed: the title states the finding, a dashed line shows the company rate, and the callout sits next to the referral bar in the same blue.
Four cards, four numbers, no story.
The top row of a turnover dashboard. What would you fix?
Show the answer: four problems
- Field names as labels. "Sum of Left Company" tells the reader a machine made it. Rule 15, Cards.
- Wrong formats. 102.00 people, and a rate shown as 0.34 instead of 34%. Rule 14.
- No comparison. 34%: up or down? Better or worse than what? Rule 5.
- Cards that don't serve the question. Two cards show the same fact (102 left, 34% left), and headcount answers nothing about turnover. Three cards are plenty. Cards.
Fixed: three cards, plain labels, each with a comparison. Only the gaps are coloured, with an arrow so colour isn't the only cue.
A good dashboard. Is it the right page for the meeting?
This page goes on the screen at the quarterly leadership meeting, where the group has ten minutes to decide what to do about turnover. As a dashboard, nothing on it is wrong. What would you change?
Show the answer: four problems
- The wrong page type. Leaders deciding in ten minutes need one answer, not a tool to explore. Rule 1, Presentations vs. dashboards.
- A question for a title. Right for a dashboard, wrong here: state the answer, with a number and a comparison. Titles.
- Slicers. Someone will filter mid-meeting and the numbers on screen will change under the discussion. A presentation page has none. Presentations vs. dashboards.
- No "so what". Nothing tells the room what to do, and three cards compete with the chart for the one message. Rule 2, Callouts.
Fixed: the presentation version, with an action title, one chart, a takeaway, and the source and date.
Do low performers leave more? The colours won't tell you.
Turnover by performance score. What would you fix?
Show the answer: five problems
- Seven colours that mean nothing. Grey everything, then colour the scores the title is about. Rule 4.
- A legend that repeats the axis. The names are already under the columns. Rule 10.
- A rating scale in alphabetical order. "Exceeds" sits between "90-day meets" and "Exceptional". Use the scale's own order. Rule 9.
- False precision. 53.33% rests on 15 people, and 44.44% on 9. Round to whole percentages and say how small the groups are. Rule 14.
- A field-name title. Rule 15.
Fixed: best rating to worst, low ratings in blue, and the two "too early" groups combined (26 of 68 left, 38%).
Hires per year, with everything switched on.
What would you remove, and what would you add?
Show the answer: five problems
- Ink that carries no data. The border, gridlines, both axis titles and a one-series legend. Rule 6.
- Labels and an axis. Keep the labels, drop the axis. Rule 11.
- "84.00" hires. People come in whole numbers. Rule 14.
- A field-name title. Rule 15.
- No emphasis. The 2011 peak is the story; colour it. Rule 4.
Fixed: only the data and its labels remain. The subtitle warns that 2016 is a part year that includes future starts.
Women leave far more often. Or do they?
Look at the bar heights, then at the numbers on them. What would you fix?
Show the answer: three problems
- The axis doesn't start at zero. Someone set its minimum to 33.84%, so a 0.05-point gap looks like a near four-to-one difference. Bar length must be proportional to the value. Rule 8.
- Two decimals. They invite the reader to see a difference that doesn't matter. Rule 14.
- The title misses the finding. The finding is that there is no gap. Say so. Titles.
Fixed: bars from zero, the counts behind each rate, and a title that states the finding.
Pay bands in the wrong order hide a clean pattern.
Turnover by hourly pay band. What would you fix?
Show the answer: four problems
- Text sorted as text. Power BI sorts "Under $20/hr" after "$45+/hr", so the lowest band ends up last and the pattern breaks. Sort by a band-order column. Rule 9.
- A label title. The finding is that turnover halves from the lowest band to the highest. Titles.
- No emphasis. Colour the two bands the title compares. Rule 4.
- Labels, axis and two decimals. Rule 11, Rule 14.
Fixed: lowest pay to highest. In Power BI, add a Pay Band Order column (1-4), select Pay Band, and use Column tools > Sort by column > Pay Band Order.
A recruiting budget to the cent.
One year of recruiting spend by source. What would you fix?
Show the answer: five problems
- Cents on a budget. "$10,980.00" is seven digits where three do the job: $11.0K. Rule 14.
- Truncated names. Long category names belong on a bar chart, where they read across. Rule 3.
- Alphabetical order. Rule 9.
- Labels and an axis, both in cents. Rule 11.
- "Sum of Total by Source". Rule 15.
Fixed: sorted bars in thousands, with the two biggest costs in blue. Together they are $21.0K of the $84.5K spent.
Five field-name titles. Write the finding instead.
Each of these is a title Power BI writes for you. Using the fact given, write an action title: who or what, what happened, the number, and compared with what. Then open the model answer.
"Count of Employment Status by Employment Status". Fact: 102 of 301 employees have left, 88 of them by choice.
Model answer: "A third of employees have left, and most of them chose to go: 88 of 102"
It gives the size (a third), the split that matters (voluntary), and both numbers.
"Count of Reason For Term by Department". Fact: 14 people left unhappy and 11 for more money, all of them in Production.
Model answer: "All 25 people who left unhappy or for more money worked in Production"
"All" is the finding. It points straight at where to act.
"Sum of Left by Term Year and Department". Fact: IT/IS lost 7 people in 2015 and none in 2014.
Model answer: "IT/IS lost 7 people in 2015, after none in 2014"
A change over time needs both ends of the change in the title.
"Sum of Left by Employee Source". Fact: 25 people were hired through search engines and 15 of them have left.
Model answer: "15 of the 25 people hired through search engines have left, nearly twice the company rate"
60% against the company's 34% is the comparison that makes the number mean something.
"Count of Date of Hire by Department". Fact: Production employs 208 of the 301 people.
Model answer: "Production employs 208 of 301 people, so its turnover drives the company's"
The second half is the "so what": why a reader should care about headcount on a turnover report.
Run this before you share any page.
Each line is one question. If the answer is no, the rule beside it shows the fix.
| Check | Ask yourself | Rule |
|---|---|---|
| Page type | Is this page presenting one point, or for exploring? | 1 |
| One message | Can I say the page's point in one sentence without "and"? | 2 |
| Title | Does it state the finding, with a number and a comparison? (On a dashboard: a question, a plain description or a dynamic title.) | Titles |
| Chart type | Does the chart fit the comparison? No pie past three slices, no gauges, no radial or 3D. | 3, 19 |
| Colour | Is everything grey except the point? Does each colour mean the same thing on every visual? | 4, 16 |
| Comparison | Does every number have a target, prior period or benchmark beside it? | 5 |
| Clutter | Have borders, gridlines, legends and decimals that don't inform been turned off? | 6 |
| Reading order | Is the answer in the top left, then the charts, then the detail? | 7 |
| Axes | Do bars start at zero? Any second axis? | 8 |
| Sort | Sorted by value, or by the categories' natural order? | 9 |
| Labels | Are series labelled on the chart? Labels or an axis, not both? | 10, 11 |
| Layout | Are edges aligned and gaps equal? Is the main visual the biggest? | 12, 13 |
| Numbers | $3.4M, not $3,412,887? Zero or one decimal on percentages? Units stated? | 14 |
| Words | Any field names left in titles, axes, legends, slicer headers or tooltips? | 15 |
| Accessibility | Does every status have a sign or arrow as well as a colour? Is text at least 4.5:1 contrast? Alt text on each visual? | 17 |
| Type | One font, three sizes, left-aligned, sentence case, nothing under 10 pt? | 18 |
| Slicers | Grouped on one edge, with plain headers, never top left? | 20 |
| Frame | Subtitle with units? Source and as-of date in the footer? | 21 |
| Story | Read only the page titles, in order. Do they tell the story, answer first? | 22 |
| Five seconds | Show the page to someone for five seconds. Can they say the point out loud? | Titles |