In Short: Design Is Whether the Numbers Get Believed
Report design has a reputation as the cosmetic layer of BI. It is not: it is the difference between reports people use and reports people screenshot into the spreadsheets they actually trust. Users decide in seconds whether a page answers their question, and they judge the numbers partly on how carefully they are presented. Design is therefore adoption work and trust work, not decoration.
These are the practices we apply on every engagement, with the reasoning attached so your authors can apply the judgement, not just the rules.
Start From the Question, Not the Data
Every strong page answers a nameable question for a nameable audience: "Is revenue on track, and where is it not?" for the sales director. Pages designed as "everything we have about sales" serve everyone badly and get abandoned first.
The practical discipline: write the page's question as a sentence before designing; put its answer - the headline number and its context - top-left where scanning starts; and structure the rest of the page as the follow-up questions in the order a reader would ask them. Detail belongs behind drill-through, not on the summary; that is what the dashboard-versus-detail structure is for.
Choose Visuals for the Relationship, Not the Novelty
- Comparison across categories: bars, sorted by value, not alphabet
- Change over time: lines; add a reference line for target or last year rather than a second chart
- A single headline: cards with comparison context (versus target, versus last period) - a number alone is trivia
- Composition: stacked bars or a matrix; pies stop working past a few slices
- Detail lookup: a clean table or matrix, and no shame in it - some questions are lookups
- Relationships and drivers: scatter charts, or the built-in AI visuals (decomposition tree, key influencers) for the why pages
The test for every visual: can a first-time reader extract its message in five seconds? If not, the visual is the wrong type, is carrying too much, or needs a title that states its point ("EMEA margin fell 3pts in Q2") rather than labelling its axes.
Reduce Cognitive Load Ruthlessly
Attention is the budget. Spend it on data, not chrome: consistent alignment on a grid, generous white space, one accent colour for what matters plus semantic red/green used only for meaning, axis and label clutter trimmed, borders and shadows mostly absent. A theme file encodes all of this once - colours, fonts, defaults - so consistency stops depending on author discipline.
Number formatting is part of load: thousands separators, sensible decimals (revenue does not need pennies), currency symbols consistently placed, and matching precision between related visuals. Mismatched formats are how careful readers start doubting careless pages.
Performance is design too: every visual is a query, so a fifteen-visual page is slow before it is confusing. Five to eight purposeful visuals per page, aggregation-friendly measures, and the disciplines from our report performance guide keep the experience matching the design intent.
The System Around the Pages
Individual page craft scales only inside a system: a theme file for identity, template pages for common patterns, agreed KPI presentation rules (our KPI dashboard guide covers those), and design review as part of publishing to certified workspaces. And keep the model honest underneath: well-named measures with described meanings mean tooltips explain themselves - increasingly important now that Copilot narrates your pages to executives who never open them.
Sources and Further Reading
Frequently asked
A reader can answer their question in seconds without instructions: the page has one clear job, the most important number is where eyes land first, visuals are chosen for the data relationship (not novelty), and nothing on the canvas competes for attention it has not earned.
Fewer than authors want: five to eight purposeful visuals is a strong page; fifteen is a page nobody reads and a performance problem besides (every visual is a query). If everything is important, split the page by audience or question.
Bars for comparison, lines for trend, cards for headline numbers, tables or matrices for lookup detail. Pies limp beyond two or three slices, gauges waste space, and 3D anything is a warning sign. Boring charts read fastest, and reading fast is the job.
Yes - a theme file (colours, fonts, defaults) makes every report recognisably yours, keeps semantic colour meanings consistent (one red, one meaning), and saves authors hours of manual formatting. It is the cheapest professionalism available.
Strongly and unfairly: users judge data quality partly by presentation quality. Inconsistent formats, cluttered pages and mismatched totals read as carelessness, and carelessness reads as wrong numbers. Design discipline is credibility discipline.
