Report Design

Why this matters

You can now build honest charts and wire them for interrogation — and still ship a page nobody reads. Design is not decoration; it is the difference between a page that argues and a page that merely contains. The good news: report design is a small number of learnable disciplines, most of which you have been absorbing since Lesson 1 without the names. This lesson supplies the names, and the capstone will demand the practice.

One page, one question

The master rule, from which the others derive: every page answers one question, and the page's title says which. "How are we performing against target?" is a page. "How is the business doing?" is a report — split it. The L09 audience frame (answer pages versus exploration pages) told you who a page is for; this rule says what it is about. A page that cannot state its question in one sentence is two pages sharing a canvas, and both will read worse for the company.

Hierarchy: the fifteen-second path

Readers enter at the top-left and sweep like a Z. Design for that path:

• Top-left: the answer. The page's headline number or its most important claim — for a performance page, the attainment card. Not the logo. The logo earns the bottom corner.
• Top band: the context. The supporting cards (revenue, margin, growth) reading left to right in the order the story needs them.
• Body: the evidence. The two or three visuals whose titles argue the page's answer — largest visual for the most important claim, not for whichever chart happened to need the room.
• Bottom or right rail: the controls. Slicers cluster where the eye ends, not where it begins — a reader adjusts filters after absorbing the default view.

Size is emphasis. If everything is the same size, the page claims everything matters equally, which means nothing does. One large visual, several medium, cards small — the layout itself ranks the evidence.

Alignment and white space: credibility you can measure

Two mechanical disciplines separate professional pages from student pages at a glance:

• Everything aligns to something. Visual edges snap to a shared grid — Power BI's gridlines and snap-to-grid (View ribbon) exist for this. A page with seventeen slightly-different left edges reads as careless, and readers extend the carelessness to your numbers. That inference is unfair and universal; design for it.
• White space is a tool, not waste. Margins between visuals group related evidence and separate unrelated evidence — proximity is a claim about relatedness. The urge to fill every pixel produces the cockpit nobody reads; the Briefing page you built in L09 breathed, and that was why it worked.

Accessibility: the part that is not optional

About one reader in twelve has a color-vision deficiency; others navigate by keyboard or screen reader. Accessible design is not a compliance chore bolted on at the end — in this course it has been the default since the theme was chosen, and now you learn the full kit:

• Contrast. Text meets the 4.5:1 ratio against its background (3:1 for large text). The Iris theme's ink-on-paper passes; ad-hoc pale gray annotations are where pages quietly fail.
• Alt text. Every visual carries a description (Format → General → Alt text) — and the craft is describing the finding, not the chart: "Bar chart" helps nobody; "Furniture leads revenue at $24.8M, five times Decor" is the page speaking. Write alt text like a title's understudy.
• Tab order. Screen readers and keyboard users traverse visuals in the order the Selection pane lists them — which defaults to creation order, i.e., chaos. Set it to the reading path: answer, context, evidence, controls.
• Color as support. The standing rule, now formalized: meaning never travels by color alone. Markers, labels, and position carry it too.

Dashboards versus reports — words that matter in the Service

Colloquially everything is "a dashboard." In Power BI the words are technical: a report is what you have been building — multi-page, interactive, one model behind it. A dashboard (Service-side, next lesson) is a single-screen pinboard of tiles from possibly many reports — glanceable, lightly interactive, the lobby-TV artifact. The design consequence: report pages argue; dashboards monitor. When a stakeholder says "dashboard," ask what they will do with it — the answer tells you which to build, and Lesson 11 gives you the machinery for both.

Performance is a design property

Every visual on a page issues queries; a 30-visual page is a 30-conversation meeting. Slow pages do not just annoy — they erode trust in the numbers ("is it broken?"). The disciplines: fewer, larger visuals (the hierarchy rule agrees); measures over calculated columns (the Module 2 rule agrees); and the Performance Analyzer (View ribbon) when a page drags — it names the slow visual, which is usually a table trying to render ten thousand rows nobody will scroll. Design and performance keep giving the same advice from different directions; when the disciplines agree, listen.

Common mistakes

• The logo in the answer slot. Top-left is the most valuable canvas on the page; brand assets go where the eye rests, not where it begins.
• Uniform sizing. Equal sizes claim equal importance. Rank with the layout.
• Seventeen left edges. Snap to grid. Careless alignment gets read as careless analysis.
• Alt text as species labels. "Bar chart" is not access; the finding is.
• The full-pixel page. White space groups and separates; filling it deletes the grouping information.

Summary