U9.01.3The two differ in interactivity and annotation densitydesign

Exploratory charts stay wide open to interaction; explanatory charts lean on dense, guiding annotation

Aliases: interaction density · annotation layers

What it is

The exploratory/explanatory difference ultimately lands on two concrete interface dimensions: how open the interaction is and how dense the annotations are. Exploratory gives users open interaction (anything can be filtered, sliced, drilled) with sparse annotation (analysts know what they are looking at and need no narration on every chart); explanatory converges interaction (readers read sequentially or flip limited pages) with dense annotation (titles, subtitles, callouts, highlights all interpret on the reader's behalf). Mixing the interface traits—loading an explanatory chart with full interactivity, or filling an exploration tool with preset conclusions—undermines each mode's core goal.

Why it happens

The differing configurations stem from who carries the understanding work in each scenario. In exploration, the analyst carries it: they decide what to look at, how to slice, and what the conclusion is; the tool's job is to provide possibility (more dimensions, freer cross-linking), not to interpret for them (preset highlights and annotations constrain the exploration space). In explanation, the author carries it: the analysis is done, readers are recipients of the conclusion, and the tool's job is to translate results into low-load visual statements—annotations (conclusion titles, key-point callouts, reference-line explanations) are the vehicle of that translation, while open interaction pushes understanding back onto readers who lack the analytical skills to bear it. The annotation-density difference is tangible in word count: an exploratory chart's average annotation may be just axis labels, while an explanatory chart typically carries 50-200 characters of title, subtitle, and callouts. Mispairing both has classic symptoms: adding filters to a chart in an explanatory slide deck leaves readers lost in interaction while missing the core argument; preset conclusion annotations in an exploration tool anchor analysts' free slicing to the annotation's "authority."

Where it stops holding

The interface traits are not purely binary: mature exploration tools also offer preset views for high-frequency paths (commonly used dimension combinations saved as one-click views), and mature explanatory artifacts offer detail interactions in appendices or hover layers (click a time point to see that day's events). The criterion is whom the interaction or annotation serves: what helps "readers understand the conclusion" belongs to explanatory mode; what helps "analysts keep asking" belongs to exploratory. Hybrid forms (an interactive infographic) are difficult precisely because the two modes must be managed in sequence: default to the explanatory focused form, and expand interaction only after an explicit switch ("explore yourself" button), keeping the two annotation densities from colliding on screen.

Applying it

  • Tag chart artifacts with their type (exploratory view / explanatory chart) and apply different annotation and interaction templates accordingly.
  • Annotation check for explanatory charts: conclusion-style title, at least one key-point callout, and a statement of the data's scope; interaction limited to hover tooltips.
  • Annotation check for exploration tools: no conclusion-style text in the default state; annotations appear only when the user adds them.
  • Verification: produce an exploratory and an explanatory artifact from the same data and have both target users (analysts and business readers) complete their tasks with the matching one; if either group completes the task on the other group's artifact, the mode labeling is unclear.

Related

  • Same group: U9.01.1 Exploratory visualization serves the analyst themselves · U9.01.2 Explanatory visualization serves readers and needs explicit conclusions
  • Nearby: U9.01.2 Explanatory visualization serves readers and needs explicit conclusions · U7.08.5 Drillable elements need a clickable visual cue
  • Search terms: exploratory vs explanatory · annotation density · interaction design

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/U9.01.3