A5.06.2Cascading attentional blink in prompt streamsdesignresearch

Consecutive rapid prompts can swallow each other

Aliases: notification burst · cascading miss

What it is

When an interface fires three or more notifications or prompts in a row, rather than just an isolated pair of targets, the attentional blink does not just affect "the one immediately following the first." It can propagate like a chain: if a given prompt happens to land inside the previous one's consolidation window, its own consolidation gets disrupted too, dragging down identification of the next one after that — producing a cascading series of misses rather than a single isolated one.

Why it happens

Classic attentional-blink studies examine the relationship between only two targets, but real scenarios usually present prompts as a continuous stream — messages, chat notifications, system alerts arriving one after another. When prompt N fails to consolidate, it is not stably encoded, but the processing system still has to deal with the brief disruption it caused; that disruption itself delays when the next prompt can begin consolidating. If prompt density is high enough — gaps consistently shorter than the recovery time needed — consolidation capacity stays perpetually "unable to free up in time," producing a snowballing chain of misses rather than the simple "miss every other one" pattern predicted by the two-target blink model.

Studying it

The corresponding experimental design is a multi-target extension of RSVP: three or more targets are embedded in the same stream, and the question is whether later targets' report accuracy drops below what the two-target model would predict. Beyond accuracy for each individual target, the analysis should also examine conditional accuracy across targets — whether missing target N significantly raises the probability of missing target N+1 — which is what actually tests for a causal chain, rather than several independent blinks simply stacking up.

Methodological caveat: multi-target RSVP is not the most common variant in the psychological literature — most classic attentional-blink work focuses on the two-target paradigm. Extrapolating a "cascading effect" to multi-notification interface scenarios should be done cautiously: existing evidence solidly supports "overall detection rate drops in dense prompt streams," but the stricter claim of a causal chain (missing one prompt directly makes the next one more likely to be missed) is less well established than the two-target paradigm's findings, and this caveat should be made explicit when applying the conclusion.

Where it stops holding

  • The cascading effect is only pronounced in streams with sufficiently high prompt density sustained over a longer period; if there are only two or three prompts total, this is closer to the standard two-target blink paradigm and does not really qualify as "cascading."
  • If the gap between prompts already exceeds the recovery time needed (roughly half a second or more), no cascade occurs, because each prompt gets the chance to fully consolidate before the next arrives.
  • The discriminability of the target itself moderates the effect's magnitude: harder-to-discriminate prompts take longer to consolidate, which lowers the density threshold at which the cascading effect starts to appear.

Applying it

  • When a system generates multiple notifications requiring individual acknowledgment at once (batch task completion alerts, consecutive system warnings), do not fire them at a fixed high frequency — control the pacing instead, giving each prompt enough time to consolidate before the next one appears.
  • If several things genuinely need to be flagged at the same moment, consider merging them into a single summary prompt rather than splitting them into several rapid-fire notifications — a merged prompt only requires one round of identification and consolidation, avoiding the cascade entirely.
  • For a single high-priority critical prompt that unavoidably follows other prompts, deliberately delay its appearance to clear the time window right after a burst of dense prompting.
  • Verification: measure the overall detection-rate curve for a sequence of consecutive prompts under real alert density, and check whether the decline is superlinear as the number of notifications grows. If the drop clearly exceeds what a simple two-target blink model would predict, that indicates a genuine cascading effect, and merging or staggering prompts should be prioritized.

Related

  • Same group: A5.06.1 After processing one target, the next is hard to process for a short window · A5.06.3 Prompts need a minimum interval between them
  • Nearby: A5.16 Habituation and prompt fatigue
  • Search terms: attentional blink · RSVP · notification burst · cascading miss

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/A5.06.2