Explanatory visualization exists to hand readers a conclusion the author already reached

What it is

In explanatory visualization, the author has already completed the analysis and knows the conclusion; the chart's job is to deliver that conclusion efficiently to readers with no analysis background. Readers have limited attention, uneven data literacy, and no motivation to "explore it themselves again"—they need to understand "what happened, why it matters, what to do" in minimal time. The design core of explanatory charts is therefore focus and guidance: each chart makes one point, the title states the conclusion directly, and every visual element exists to support that point. This is the opposite of the exploratory "no preset answers."

Why it happens

An explanatory chart's effectiveness comes from directed allocation of cognitive load: when readers open one, their cognitive tasks include decoding visual elements, understanding axes, extracting the pattern, and deriving the meaning—and only the last is where the author wants them to spend effort. The lower the load in the earlier stages, the more resources remain for the conclusion. Every load-reducing technique is "the author deciding for the reader": writing the conclusion directly as the title ("New-user retention has risen for three straight weeks") instead of a neutral description ("Line chart of new-user retention"), highlighting the key series in color while graying the rest, cropping data segments unrelated to the point. These choices would be criticized as "preset conclusions" in an exploratory context, but in an explanatory one they are precisely the value—readers have no opportunity and no desire to re-analyze, and a clear single path beats comprehensive openness. The most common explanatory failure is not "wrong conclusion" but "fuzzy conclusion": the chart contains all the information, but readers must synthesize it themselves, and most will skip synthesis and instinctively grab the most visually prominent element—which may not be the one the author intended to emphasize.

Where it stops holding

Explicit conclusions fail in two scenarios. First, when the data genuinely does not support a single conclusion: if the evidence points to multiple equally valid states ("channels trade wins and losses"), forcing one storyline manufactures false certainty—an honest explanatory chart presents multiple conclusions rather than a disguised single path. Second, when readers' backgrounds vary widely: the same "conclusion-clear" chart is clear to novices but may lose credibility with experts for oversimplification ("where are the quantiles? the sample size?"), and layered presentation (conclusion in the main chart, details on hover or in an appendix) is sturdier than a single version. The conclusion's wording has a boundary too: the title should state the scope the data supports ("over the past six weeks"), while over-generalized phrasing ("retention will keep rising") exceeds what the data can support.

Applying it

• Write explanatory chart titles as conclusion statements ("X caused Y" or "Y rose N% during Z"), never as chart-type descriptions.
• Keep one storyline per chart: the key series in an accent color, others gray or removed.
• Put the conclusion's scope (time, population, conditions) in the subtitle; do not promote it to generality the chart cannot support.
• Verification: show a reader with no analysis background the chart for 10 seconds, take it away, and ask them to restate the conclusion; the deviation from the author's intent measures the explanatory effect.

Related

• Same group: U9.01.1 Exploratory visualization serves the analyst themselves · U9.01.3 The two differ in interactivity and annotation density
• Nearby: U9.01.1 Exploratory visualization serves the analyst themselves · U9.01.3 The two differ in interactivity and annotation density
• Search terms: explanatory visualization · data storytelling · message-driven chart