Guidelines
Suggest edit

Annotate key observations directly on the view

For narrative explanation of dense charts or maps, use direct annotations on the current view to maximize insight and address missed comparisons for readers who are unlikely to infer the main pattern on their own.

  • purpose:refine
  • basis:empirical
  • density:dense
  • quality:insight:use
  • lever:text-annotation
  • component:annotation:use
  • audience:general-public

advice

Direct on-view annotations

Place short annotations at the exact points, regions, or intervals that carry the main message. For example, label the moment when a trend accelerates, mark where estimates diverge from actuals, or annotate a dense map region to answer the comparison the reader is most likely to ask.

reason

Why direct annotations work

Dense views can contain too much raw information for readers to turn into a clear conclusion on their own. Direct annotations put the intended observation at the point of need and connect text to evidence immediately.

Mechanism: On-view annotations reduce search and interpretation effort by tying the claim to a specific visual target.

Evidence: The analyzed narratives used annotations to explain key events and comparisons, while the paper critiques dense interactive views that lacked map annotations, memorable factoids, or synthesis and therefore made meaningful conclusions hard to draw (Segel & Heer, 2010).

context

Use when the story depends on a specific takeaway from a dense view

  • User Goal: Understand the intended comparison, turning point, or explanation quickly.
  • Task: Read an authored takeaway from a dense chart or map.
  • Data: Large or information-heavy views where many plausible readings compete.
  • Chart Setting: Narrative graphics that combine visualization with explanatory text.
  • Audience: General readers rather than trained analysts.
  • Success Criterion: The main takeaway is visible in the graphic itself, not only in external prose.

exceptions

Do not force authored annotations into purely reader-driven tools

Break it when: The display is intended as a purely reader-driven analysis tool with no authored narrative. Why: That setting prioritizes free exploration and minimal messaging rather than guided takeaway reading.

costs

Costs of direct annotations

Sacrifice: Annotations consume space inside the view.
Risk: Too many annotations create clutter and weaken the main point.
Mitigation: Keep annotations to key events and replace long explanatory prose with shorter fact-like statements where possible.

mistakes

Common failure with direct annotations

Mistake: Leaving explanation in long, terminology-heavy paragraphs away from the view instead of annotating the evidence directly. Why it fails: Readers must parse dense prose and still map it back to the chart or map on their own.

check

How to check direct annotations

Failure Sign: Readers can see the data but cannot tell what conclusion the story wants them to draw.
Quick Check: Inspect whether each main message has a nearby callout tied to a specific mark, region, or interval.
Stronger Test: Remove the surrounding prose briefly and see whether the intended takeaway is still recoverable from the annotated view.

fix

How to fix missing annotations

  • Add callouts at the exact turning points, regions, or comparisons that matter most.
  • Convert long explanatory paragraphs into shorter fact-like annotations attached to the view.
  • Add a short synthesis after the annotated view when the display still leaves the conclusion unclear.

References

Segel, E., & Heer, J. (2010). Narrative Visualization: Telling Stories with Data. IEEE Transactions on Visualization and Computer Graphics, 16(6), 1139–1148. https://doi.org/10.1109/TVCG.2010.179