Each view on a dashboard should answer one distinct question, not restate what another view shows

What it is

Every view on a dashboard should answer one explicit question: how big is the total, which way is the trend, what is the composition, where is the anomaly. Multiple views exist to divide this labour — different questions need different chart forms and different granularities, and a screen of views lets users scan several questions at a glance. A view with no question of its own is placeholder decoration: it consumes canvas and attention while producing no judgement.

Why it happens

The division follows from the matching between questions and charts: trend questions suit lines, composition suits stacks or shares, comparison suits bars, status suits numbers or signals — there is no universal chart, so answering a full set of business questions necessarily takes multiple views. The division also runs across granularity: an overview view answers "should I care," a detail view answers "care about what," and the two differ in density and abstraction. In design, each view should be able to state in one sentence "which question I answer" — that sentence doubles as the basis for its chart type, its position, and its right to stay, and a view that cannot say it is the cleanup target of the next card.

Where it stops holding

Division does not mean one view per metric: different facets of the same question can merge into one compound view (a number plus a sparkline), and the mapping from questions to views should come from task analysis rather than mechanical one-to-one. Division also drifts — business questions change, and formerly well-assigned views collectively lose focus, so a dashboard needs periodic re-checks of "is each view still answering its assigned question?"

Applying it

• Before designing, list the questions: which questions must this screen answer, ranked by priority.
• Map each view to one question on the list and record the mapping in the configuration; views without one get deleted or redesigned.
• Verification: ask users to retell "what did this screen tell you" after viewing; a retelling matching the question list means the division holds.

Related

• Same group: U7.01.2 Views need an explicit data relationship to each other · U7.01.3 Stacking unrelated views scatters attention
• Nearby: U2.01.1 Comparison, trend, distribution, composition, and relation each take a different chart · U7.07.2 Reading order should match decision order
• Search terms: dashboard design · view purpose · task driven dashboard