Captured attention takes time to return
Aliases: return cost · inhibition of return · IOR
What it is
Once attention has been captured by a stimulus and shifted there, returning to the task at hand is not instantaneous — there is a measurable disengagement-and-return delay. This delay is often called the disengagement cost: even if the capture event itself lasts only a moment, the time a user takes to refocus on the primary task is often much longer than the capture event itself.
Why it happens
Attention shifting splits into two independent sub-processes: disengagement (moving away from the current focus) and orienting (moving to the new location). When a capture event occurs, both steps happen almost passively and automatically, and quickly. But returning to the original task after capture requires actively re-executing disengagement and orienting — and this time it is a voluntary shift, which is inherently slower to initiate than stimulus-driven capture.
Research further shows that after attention briefly leaves a location, that location shows inhibition of return (IOR): voluntarily sending attention back to a just-vacated location is actually slower shortly afterward, which further lengthens the time to return to the original task.
Studying it
A common approach is a variant of the cueing paradigm: an automatically capturing peripheral cue is presented first, then a target appears either at the original task location or at the cue location; by manipulating the stimulus onset asynchrony (SOA) between cue and target, reaction time is measured as a function of SOA — at short SOAs, responses at the cue location are faster (capture is still active); at slightly longer SOAs, responses at the cue location become slower instead (entering the IOR range).
Typical dependent variables: target reaction time, and the time needed to first return to the original task location.
In interface research, this method is mainly used to quantify how much an interface interruption (a popup, a notification) actually slows the primary task, rather than just asking "did the user see the notification."
Methodological caveat: IOR's specific time window is measured in simplified, millisecond-scale lab tasks. Real interface interruptions usually involve more complex cognitive processing (reading a notification's content, deciding whether to open it), so the real return time far exceeds the lab-measured IOR window — the magnitude should not be transplanted directly.
Where it stops holding
- The size of the return cost correlates with how complex the capture event is — a simple visual flicker costs little, while a notification requiring reading comprehension costs much more, because reading itself occupies an additional processing stage, not just a simple orienting shift.
- If the capture event overlaps spatially with the current task (it happens right where the user is already looking), the disengagement-return cost drops significantly, because no real spatial shift is required.
Applying it
- When evaluating a popup prompt's real effect on the primary task, do not only measure "did the user notice it" — measure how long it takes for the user's performance to recover to its pre-interruption level after the interruption occurs.
- The return cost produced by unnecessary capturing prompts (auto-play ads, non-critical notifications) is a pure efficiency loss and should be counted as a cost of that design, not offset only against benefit metrics like click-through rate.
- If a prompt genuinely needs to capture attention, place it as close as possible to the current task's spatial location, reducing the disengagement-orienting cost of crossing the visual field.
- Verification: measure the user's speed on the primary task before and after receiving a capturing prompt, quantifying the time needed to return to baseline.
Related
- Same group: A5.07.1 Sudden onset and motion automatically capture attention · A5.07.3 Frequent capture leads users to actively block that region · A5.07.4 The larger the salience gap, the harder capture is to suppress · A5.07.5 Bottom-up capture happens early in processing, before content is semantically identified · A5.07.6 A task-irrelevant, highly salient element keeps consuming attentional resources
- Nearby: A5.08 Interruption cost and task resumption
- Search terms:
disengagement cost·inhibition of return·cueing paradigm
Cards in the same group
- A5.07.1Sudden onset and motion automatically capture attention
- A5.07.3Frequent capture leads users to actively block out that region
- A5.07.4The larger the salience gap, the harder capture is to suppress
- A5.07.5Bottom-up capture happens early in processing, before content is semantically identified
- A5.07.6A task-irrelevant, highly salient element keeps consuming attentional resources, even once known to be irrelevant