L5.05.5detail crowding key informationdesignresearch

Excess detail crowds out attention needed for key information

Aliases: attention crowding · warning buried · key sentence missed

What it is

The pane is packed with weight bars; at the very bottom, “this is a draft, do not send.” Gaze is eaten by the bars first; that sentence becomes a footer. Excess detail crowds out the attention needed for key information. The harm is not that the detail cannot be understood. It is that the sentence which could actually change the act is not seen.

Crowding is zero-sum: one more column of weights, one less look at the limit.

Why it happens

Attention has capacity. Salience, length, and position all compete. Detail is usually prettier, longer, more like “content”; key limits are often short, disclaimer-like, parked in a corner. The result of the contest is predictable: pretty wins. Users are not refusing the limit; it does not get a turn.

This is not “detail does not produce understanding.” People can fully understand what the weight bars say and still miss the draft mark. The problem is allocation, not comprehension. After the miss, the act is chosen in a world where the limit was never given; transparency is ample on paper and the key information equals not given.

Studying it

Park a key limit in a fixed place, increase the amount or visual weight of surrounding detail, and measure detection with eye tracking or a later probe, plus whether people still send. Independent variables: amount of detail, position and contrast of the key sentence, whether it is a block of its own. Dependent variables: detection of the key sentence, send rate, rate of recalling detail but not the limit.

Recalling many details and not being able to say the limit is crowding’s signature, not “did not read carefully.”

Where it stops holding

If the key information is itself long (ten legal consequences that must be listed), the capacity problem becomes how to split steps, not simply deleting detail. When the whole screen is one sentence, crowding does not exist. Capacity is smaller on mobile; the same amount of detail may still coexist on desktop and already push the limit off the first screen on a phone. This entry does not care whether detail is understood; it cares whether that sentence was pushed out.

Applying it

  • Place the sentence that can change the act first, then decide how much room detail still has. Do not reverse the order.
  • Give the key limit a block of its own, with contrast and position stronger than any chart. Do not put it in an appendix that appears only after scrolling to the end.
  • Collapse detail. When detail is expanded, the key sentence stays pinned in the viewport.
  • Check: a five-second glance test, then “do you think this can go out.” If most people say yes and your limit sits under a weight chart, the key information has already been crowded out.

Related

  • Same group: L5.05.1 Excess technical detail does not produce understanding · L5.05.2 Transparency must serve the user's next decision · L5.05.3 Information that cannot be acted on is noise · L5.05.4 Transparency is sufficient only if the user can change the next action from it · L5.05.6 Transparency and usability are in tension; full disclosure makes the interface unusable · L5.05.7 Transparency does not necessarily produce trust; exposing complexity can lower it · L5.05.8 Different roles should receive different depths of explanation, not the same text
  • Nearby: L5.01 Types of Explainability · L1.03 Visualizing Uncertainty · L5.02 Local and Global Explanations
  • Search terms: attention crowding · key information · warning buried

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/L5.05.5