U6.01.3Details surface on demand, not by defaultdesign

Record-level detail should surface only once a user asks for it, not spill across the chart by default

Aliases: details on demand · on-demand detail

What it is

The mantra's final step: record-level detail (all fields of one record, point values, full text) should appear after the user expresses interest — hover, click, expand — never spread across the chart from the start. Default-full detail is not "more information"; it is noise that dilutes attention: it drowns the overview and turns reading into excavation.

Why it happens

On-demand detail matches the economics of attention to the timing of value: a detail record's value is only realised after the user has locked onto a target — shown earlier, there is no question to answer and the information cannot be encoded into the current task; shown at the right moment, the same line answers instantly. Default-full detail also collides with the overview directly: overviews depend on aggregation and omission (exactly the density conclusions from the readability family), and full detail destroys the aggregate structure, degenerating the chart into a table. On-demand retrieval has an engineering dividend too — detail payloads (full text, line items) can be large, and lazy loading keeps the surface responsive.

Where it stops holding

"On demand" does not mean "hidden": detail entry points must be visible and discoverable (clickable marks, explicit expanders); anything reachable only by accidental clicks fails discoverability. High-frequency fields are the exception — when most users need one value every time (say, the running total), pinning it beats charging everyone an extra click. Retrieved details also need an exit: expanded content must collapse again, or the canvas fills incrementally and the overview disappears with it.

Applying it

  • By default render only the aggregate layer and identity layer; reach detail through hover tooltips, a selection panel, or expandable rows — pick one.
  • Standardise the retrieval interaction product-wide: the same element class uses the same reveal gesture, so users never relearn.
  • Verification: watch the path users take to one detail record; arrival within one or two clicks while the overview stays readable means on-demand detail holds — a canvas crowded with permanent detail is a violation.

Related

  • Same group: U6.01.1 Overview first, then zoom and filter · U6.01.2 Zooming and filtering are two ways to narrow scope
  • Nearby: U6.09.1 Tooltips carry exact values · U5.06.4 High-density charts keep overall shape and lose individual readability
  • Search terms: details on demand · progressive disclosure · drill down panel

Cards in the same group

Quick Actions

Share

Share this page

ios_share

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