Lesson 1: What a Dashboard Is Actually For

LESSON TEXT

A dashboard has one job: to help someone make better decisions faster. That sounds obvious, yet most dashboards fail at it — not because the data is wrong, but because they were built to display everything available rather than to serve a decision. The result is a wall of numbers that looks impressive, informs little, and gets ignored within weeks.

The name is a useful clue. A car's dashboard shows you the few things you need to drive safely — speed, fuel, warnings — not every measurement the engine produces. It's ruthlessly selective, because its job is to support driving, not to prove the car is measuring things. A business dashboard should be the same: a focused instrument for a specific person making specific decisions, not a data dump.

So the first question in building any dashboard or report is never 'what data do we have?' It's 'who is this for, and what decisions should it help them make?' Everything follows from that. A dashboard for a warehouse supervisor deciding today's staffing needs different things than one for an executive deciding quarterly strategy. Build for the decision, and the dashboard becomes useful. Build for completeness, and it becomes wallpaper.

This connects directly to everything in this program: a dashboard is a tool for the 'gather' and 'assess' stages of the core cycle. Its purpose is to get the right information in front of the right person clearly enough that they can assess it and decide. Judge every dashboard by that standard — does it help someone decide? — and you'll avoid the trap that most organizations fall into.

VIDEO SCRIPT

[On camera] A dashboard has exactly one job: help someone make a better decision, faster. Sounds obvious — and yet most dashboards fail at it. Not because the data's wrong. Because they were built to show everything available instead of to serve a decision. So you get a wall of numbers that looks impressive, tells you nothing, and gets ignored in a month. The name gives it away. Your car's dashboard shows the few things you need to drive — speed, fuel, warning lights. Not every reading the engine produces. It's ruthlessly selective, because its job is to help you drive. A business dashboard's the same — a focused instrument for a specific person making specific decisions. Not a data dump. So the first question is never "what data do we have?" It's "who's this for, and what decisions should it help them make?" A warehouse supervisor deciding today's staffing needs something totally different from an executive setting quarterly strategy. Build for the decision — useful. Build for completeness — wallpaper. Judge every dashboard by one question: does it help someone decide?

Lesson 2: Choosing What to Show

LESSON TEXT

The hardest part of good reporting isn't adding — it's subtracting. Every metric you show competes for attention with every other. Show too much and nothing stands out; the important drowns with the trivial. Deciding what to leave out is the core discipline.

Start from the decisions, work back to the metrics

List the decisions this person actually makes, then include only the metrics that inform those decisions. If a number wouldn't change any action the viewer takes, it doesn't belong on their dashboard — however interesting it is. This single rule eliminates most clutter.

Distinguish the vital few from the merely available

Most situations have a handful of metrics that truly matter and dozens that are just measurable. A sales leader may live and die by pipeline value, conversion rate, and cycle time — while page-views and email-open-rates, though available, don't drive their decisions. Identify the vital few and give them prominence; relegate or remove the rest.

Prefer metrics that prompt action over metrics that just describe

A good dashboard metric, when it moves, tells you to do something. 'Orders awaiting fulfillment over threshold' prompts action. 'Total orders all-time' is a vanity number that prompts nothing. Favor metrics tied to decisions and thresholds over static totals that only describe.

Give every number a comparison

Recall from Course 3: a number alone is inert. Wherever possible, pair each metric with a comparison — versus target, versus last period, versus benchmark — so the viewer instantly knows whether it's good, bad, or normal without having to think.

When in doubt, cut. A dashboard with six well-chosen, well-compared metrics that each drive a decision is far more valuable than one with forty. Restraint is not a limitation here; it's the entire skill. The best dashboard shows the least that fully serves the decision.

VIDEO SCRIPT

[On camera] The hardest part of good reporting isn't adding — it's subtracting. Every metric competes with every other for attention. Show too much, and nothing stands out — the important stuff drowns with the trivia. So: start from the decisions, work back to the metrics. List what this person actually decides, include only the numbers that inform those decisions. If a number wouldn't change anything the viewer does — it's off the dashboard. However fascinating. Separate the vital few from the merely available. A sales leader lives on pipeline, conversion, cycle time. Page-views? Available — but they don't drive her decisions. 

Prominence to the vital few, cut the rest. Favor metrics that prompt action over ones that just describe. "Orders awaiting fulfillment over threshold" tells you to DO something. "Total orders all-time" — vanity number, prompts nothing. And give every number a comparison — versus target, versus last period — so the viewer instantly knows good, bad, or normal. When in doubt? Cut. Six sharp metrics beat forty every time. Restraint isn't a limitation — it's the whole skill.

Lesson 3: Choosing the Right Chart

LESSON TEXT

The right chart makes a message instantly clear; the wrong one hides it or distorts it. You don't need dozens of chart types — a handful, matched to the message, covers almost everything. The key is to choose the chart based on what you're trying to say, not on what looks impressive.

Comparing amounts → bar chart

To compare values across categories — sales by region, tickets by team — a simple bar chart is almost always best. The eye reads bar length accurately and effortlessly. Reach for bars far more often than you'd think.

Showing change over time → line chart

For a trend across time — revenue by month, users by week — a line chart shows direction and rate of change clearly. Lines are for time; use them when the story is 'how this moved.'

Showing composition → use sparingly

To show parts of a whole, a pie chart can work for two or three large slices, but it fails the moment there are many similar-sized parts — the eye can't compare angles well. Often a bar chart of the parts communicates composition better than a pie. Be skeptical of pie charts; they're overused and frequently the wrong choice.

A single key number → just show the number

Sometimes the clearest 'chart' is no chart. One big, bold number with its comparison ('$1.2M, +8% vs target') communicates faster than any graphic. Don't dress up a single value in an unnecessary visual.

Two rules cover most mistakes. First, match the chart to the message: comparison → bars, time → lines, single value → the number itself. Second, avoid decoration that doesn't inform — no 3-D effects, no gratuitous color, nothing that makes the data harder to read in exchange for looking fancy. Clarity always beats flash.

VIDEO SCRIPT

[On camera] The right chart makes your message instantly obvious. The wrong one hides it. And you don't need a dozen chart types — a handful, matched to the message, covers almost everything. Choose based on what you're trying to SAY, not what looks impressive. 

Comparing amounts across categories — sales by region? Bar chart. The eye reads bar length effortlessly. Reach for bars way more than you think. Change over time — revenue by month? Line chart. Lines are for time; they show direction and pace. Composition, parts of a whole? Pie charts work for two or three big slices — and fall apart the second you've got lots of similar ones, because we can't compare angles. Honestly, a bar chart of the parts usually beats a pie. Be suspicious of pie charts. And a single key number? Sometimes the best chart is no chart. One big bold "$1.2 million, up 8% on target" beats any graphic. Two rules and you'll avoid most mistakes: match the chart to the message, and cut any decoration that doesn't inform. No 3-D, no gratuitous color. Clarity beats flash. Every time.

Lesson 4: Designing for Attention

LESSON TEXT

Even the right metrics in the right charts can fail if they're arranged poorly. Human attention is limited and predictable, and good dashboard design works with it rather than against it. A few principles from how people actually read a screen make the difference between a dashboard that's understood in seconds and one that overwhelms.

Most important, top-left

In cultures that read left-to-right, top-down, the eye lands first at the top-left. Put the single most important metric there. Arrange the rest in rough order of importance, flowing down and across. Don't make the viewer hunt for what matters most.

Group related things

Place metrics that are read together near each other. If someone evaluating sales health looks at pipeline, conversion, and cycle time together, group them visually. Scattering related metrics forces the viewer to reassemble the story themselves.

Use visual hierarchy

Make important things bigger and bolder; make context smaller and quieter. If everything is the same size and weight, nothing has priority and the eye doesn't know where to go. Size and emphasis should signal importance.

Use color with restraint and meaning

Color is powerful precisely because it's noticed — so spend it carefully. Reserve strong colors (especially red) for things that need attention, like a metric off target. If everything is colorful, color signals nothing. A mostly calm, neutral dashboard with one red flag communicates far more than a rainbow.

Good design is largely invisible: the viewer simply understands the dashboard quickly and can't say why. That ease is the product of deliberate choices — important things first and prominent, related things grouped, clear hierarchy, and disciplined color. Design for how attention actually works, and your reporting does its job.

VIDEO SCRIPT

[On camera] Right metrics, right charts — and it can still fail if it's arranged badly. Human attention is limited and predictable, and good design works WITH it. Most important thing, top-left. We read left-to-right, top-down — the eye lands top-left first. Put your single most important metric right there. Don't make people hunt for what matters. Group related things. If someone checks pipeline, conversion, and cycle time together to judge sales health — put them together. Scatter them, and you've forced the viewer to reassemble the story themselves. Visual hierarchy: important things bigger and bolder, context smaller and quieter. If everything's the same size, nothing has priority and the eye gets lost. And color — use it with restraint and meaning. Color's powerful because it's noticed, so spend it carefully. Save strong colors, especially red, for what needs attention — a metric off target. If everything's colorful, color means nothing. A calm, neutral dashboard with one red flag says more than a rainbow ever could. Good design is invisible — people just get it fast and can't tell you why. That ease is the whole point.

Lesson 5: Dashboards vs. Reports — Different Jobs

LESSON TEXT

'Dashboard' and 'report' get used interchangeably, but they do different jobs, and confusing them produces things that serve neither purpose well. Knowing the difference lets you build the right thing.

A dashboard is for monitoring — an ongoing, at-a-glance view of how things are going right now, usually updated live or frequently. Its job is to let someone check status quickly and spot when something needs attention. It answers 'are we on track?' and it's built to be scanned in seconds, repeatedly. Operational dashboards for daily or real-time decisions live here.

A report is for understanding — a deeper, usually one-time or periodic analysis of a specific question. Its job is to explain something: why did this happen, what does it mean, what should we do? It answers 'what's going on and what should we do about it?' and it's built to be read and reasoned through, once, carefully. The strategic analyses behind big decisions live here.

The mistake organizations make is building one when they need the other. They pack a dashboard with so much explanatory detail it becomes an unreadable report that can't be scanned. Or they deliver a big analytical question as a dashboard of live metrics that never actually explains anything. Match the format to the job: monitoring status → dashboard; understanding a question → report.

Recall the operational-vs-strategic distinction from Course 1. Operational decisions — frequent, routine — are served by dashboards. Strategic decisions — rare, deep — are served by reports. When you know which kind of decision you're supporting, you know which format to build.

So before you build anything, ask: is this for monitoring or for understanding? Is the underlying decision operational or strategic? Your answer tells you whether to build a lean, scannable dashboard or a focused, reasoned report — and building the right one is half of doing it well.

VIDEO SCRIPT

[On camera] "Dashboard" and "report" get used like they're the same thing. They're not — and mixing them up gives you something that serves neither. A dashboard is for monitoring. An at-a-glance, live view of how things are going right now. Its job: let you check status fast and catch when something needs attention. It answers "are we on track?" — built to be scanned in seconds, over and over. That's your operational, daily, real-time stuff. A report is for understanding. A deeper, one-time or periodic look at a specific question. Its job: explain something — why did this happen, what does it mean, what should we do? Built to be read and reasoned through, carefully, once. That's your strategic analysis. And the classic mistake? Building one when you need the other. Stuffing a dashboard with so much explanation it becomes an unreadable report. Or answering a big strategic question with a wall of live metrics that never actually explains anything. Remember Course 1 — operational decisions want dashboards, strategic decisions want reports. Figure out which decision you're serving, and you know which one to build. That choice is half the battle.