Excel Dashboard Examples: 6 Layouts That Actually Work

The workhorse. A row of three-to-five headline numbers along the top, one chart below showing the trend of the most important one. In my experience most weekly operational reviews want exactly this and nothing more.

Each tile is just a cell referencing a PivotTable result, dressed with a border; the chart is a single PivotChart line. Drop a slicer wired to every PivotTable and the whole thing filters at once.

One metric owns the screen — a north-star number, or a single KPI on a wall-mounted display. One big figure, a sparkline for its trend, and a comparison to its target or to last period.

A large cell for the number, an in-cell sparkline beside it (Excel 2010 and later), and conditional formatting to colour it against a goal. That's the whole build.

Bars for the actual value, a thin marker for the goal, and instant colour telling you who cleared the bar. This is the layout for anything measured against a number it's supposed to hit — collection rate versus benchmark, sales versus quota, utilisation versus plan.

In Excel it's a bar chart with the target added as a second series drawn as markers. Stephen Few's bullet graph is the refined version of exactly this idea, built specifically to replace the gauge (more on that below).

The same little chart repeated once per segment, on a shared scale. Twelve clinics, twenty reps, a metric per product line — the eye scans the grid and the outliers jump out. It's Edward Tufte's favourite device for a reason: it turns "compare twenty things" into a single glance.

The fastest build in Excel is a column of sparklines, one row per segment. For more detail, a grid of tiny identical PivotCharts.

A horizontal bar chart, sorted highest to lowest, top item highlighted. For any question shaped like "which are the biggest / worst / most" — top services by revenue, the weekdays with the worst no-show rate, providers by volume.

A PivotTable sorted descending, plotted as a bar chart — or, if you want it in-grid, conditional-formatting data bars in a sorted table. Bars horizontal, not vertical, so the labels stay readable.

One metric, one big line, the timeline annotated with the things that moved it. When the entire story is the trajectory — a turnaround, a launch, a recovery — give it the whole canvas and mark the events so the chart explains itself.

A line PivotChart, with events added as a helper series or plain text boxes. Keep it to one line if you can.

A dial, a needle, a coloured arc — one number dressed as a car dashboard. The problem isn't that it's ugly; it's that it's expensive. Stephen Few, who wrote the book on dashboard design, made the case against them when he built the bullet graph — the actual-vs-target bar from layout 3 — as their replacement. It was, in his words, "developed to replace the meters and gauges that are often used on dashboards," and its linear form "supports more efficient reading than radial meters" in a fraction of the footprint. A gauge spends the room of many numbers to show one; the bullet graph shows the same comparison in a strip.

Depth and tilt don't add information — they distort it. In a tilted 3D pie the added depth and skew make the slice at the front read as larger than an identical slice at the back; Few demonstrates the effect directly in Save the Pies for Dessert. It's a working example of what Tufte calls the "lie factor" — a graphic that exaggerates an effect beyond what's actually in the data.

There's a deeper reason bars beat pies even in 2D. In the classic study of how accurately people read charts, Cleveland and McGill ranked the visual cues by accuracy: position sits at the top, area near the bottom. A bar encodes value as length and position; a pie makes you compare angles and areas instead — cues that sit lower in that ranking. Keep a pie only for two or three slices of a genuine whole; past that, use a bar.

The one that wins design awards and helps no one: every metric the team could think of, each in its own bright box, glowing on a dark theme. Two things break it. First, Tufte's data-ink ratio — most of the "ink" is decoration, borders and gradients rather than data, so the actual numbers have to fight to be seen. Second, if the meaning rides on red versus green — "red is bad, green is good" — it's invisible to the roughly 8% of men of Northern-European descent (about one in twelve) with red-green colour blindness, who see the same drab pair for both.

The fix isn't decoration, it's subtraction. One decision, the few numbers that serve it, and colour used to mean one thing — not to fill space. If everything on the screen is highlighted, nothing is.