A reporting dashboard exists to deliver a few conclusions fast to people with no time to explore

What it is

A reporting dashboard's readers are "people with no time to explore": executives, cross-department colleagues, external audiences. Its job is delivering a handful of conclusions in the shortest time — did we finish, did we hit target, where do we stand against expectation. Its design goal is neither completeness nor explorability but the clarity, ordering, and credibility of conclusions.

Why it happens

Conclusion delivery optimises the reader's cognitive path: readers will not organise the information themselves, so the page organises it for them — conclusions first (each screen states "what this page shows"), evidence in attendance (the supporting graphic immediately follows), and order as argument (the page order is the argument order). The reporting type borrows narrative devices heavily: titles state conclusions rather than metric names ("East exceeded target by 12%," not "East GMV"), annotations mark anomalies and events, and baselines are drawn in so target attainment is judgeable at a glance. Credibility rides on scope transparency: data time point, statistical scope, and sample range visible in the footer — reporting is where scrutiny concentrates, and invisible scope leaves all the challenge to the room.

Where it stops holding

"Conclusions first" sits one line away from selective presentation: organising information is editing, showing only the data that supports the conclusion is manipulation — the conclusion must be re-checkable against the page's evidence, and counter-evidence may not be absent (secondary placement is fine). The reporting type usually derives from monitoring or analytical versions (same data, another audience), and derivation should re-curate rather than screenshot directly — different audiences have entirely different questions. Fixed-period reports (weekly, monthly) should also be templated: stable structure and scope let readers spend attention on what is new.

Applying it

• Write each screen's title as a conclusion sentence, with the graphic as evidence right behind; disclose scope and time point in a fixed footer position.
• Place counter-evidence and exceptions in secondary positions, but never omit them.
• Verification: find a reader without background and give them thirty seconds to retell the page's conclusion; a retelling matching the intended conclusion with cited evidence means delivery succeeded.

Related

• Same group: U7.02.1 Monitoring dashboards optimise for anomaly detection · U7.02.2 Analytical dashboards optimise for depth and comparison · U7.02.4 The three purposes differ in layout and density
• Nearby: U10.03.3 Narrative wording often outruns what the data supports · U10.02.3 Data range, filters, and exclusions must be disclosed
• Search terms: reporting dashboard · executive dashboard · narrative visualization