IX Coach

Attention Residue: Why Switching Tasks Costs More Than You Think

The hidden cost of task-switching and how to reduce it

Attention Residue: Sophie Leroy’s 2009 Paper, Explained

Attention residue, coined by organizational behavior researcher Sophie Leroy in her 2009 paper "Why is it so hard to do my work? The challenge of attention residue when switching between work tasks" (Organizational Behavior and Human Decision Processes, 109(2), 168-181), refers to the partial attention that stays on a previous task after you switch to a new one. Even when you’ve physically moved on, part of your cognitive bandwidth remains occupied processing the unfinished or interrupted task — degrading performance on the new task. Leroy’s original lab experiments support the effect; applied consequences (meeting performance, creative work quality) are plausible extensions.

Sophie Leroy published "Why is it so hard to do my work?" in 2009, documenting how switching from an unfinished task to a new one leaves residual cognitive activity on the first task. The effect is distinct from simple distraction: the residue operates even when you’ve made a deliberate, willing switch. Its practical implications are significant — every interruption carries a hidden tax, and most modern knowledge work environments generate interruptions constantly. The practices below operationalize what research and experience suggest helps.

Practices

How these practices connect

Attention residue comes from open cognitive loops: when a task ends without a completion signal, part of working memory keeps allocating to it even while a new task is underway. Every practice here works by closing that loop through a different lever — the task itself, the environment around it, the transition between tasks, or the social exchange the task was part of. None of them treat willpower or discipline as the mechanism; they all treat the loop's closure as the mechanism.

Is closing browser tabs basically the same thing as finding a stopping point?

They target the same residue but at different layers. Reaching a stopping point closes the cognitive loop inside your head — the task itself feels complete or has a clear next step. Closing tabs and documents removes the external cues that would otherwise keep reactivating that loop from outside. Doing the first without the second means the task still whispers at you every time you glance at the open tab; doing both removes the residue from two directions at once.

Should I clear small tasks first or block off time for deep work first?

Do both, in that order: clear small tasks, then enter the protected block. Batching small tasks to completion first means the large task starts with a clean slate instead of carrying residue from interruptions handled mid-session. The protected window then prevents new small tasks from intruding once the large task is underway. Reversing the order defeats the point — a distraction-free block that opens with three unfinished quick tasks still starts contaminated.

Do you have to follow these steps in order?

No single sequence is required, but two pairs have a natural order. Small tasks should be cleared before a large focus block begins, not handled mid-block, because handling them mid-block is what generates the residue the block is meant to prevent. A transition ritual comes after a stopping point is reached, not instead of one — the transition gives residue time to dissipate once the task is actually closed. Outside those two pairings, the practices are independent and can be adopted in any order.

Why doesn't just taking a break between tasks fix attention residue?

Because a break is not automatically low-demand, and it is the demand level of the transition that determines whether residue actually dissipates. Checking email or Slack during a break introduces new content that generates its own residue rather than clearing the old task's residue, so time passes but nothing is resolved. A transition only works when it stays low-cognitive-demand — a short walk, a breath, a brief closure note — so the previous task's activation can settle before the next one begins.

Does attention residue only affect the person switching tasks, or does it spread to other people?

It spreads. When a task is collaborative, an open loop exists on both ends — the person who completes the work and the person who requested it and is waiting to hear back. If the requester gets no closure signal, they carry an unresolved loop about whether the work is happening, which frequently surfaces as a follow-up interruption that then generates residue in the person who was working. A brief explicit completion signal closes the loop on both sides at once, which is why it functions as a residue-reduction practice for the whole working relationship, not just for the individual.

Why would I bother counting how often I switch tasks?

Because most people cannot accurately name their own switching pattern without counting it, since brief switches like glancing at a phone or a tab feel automatic rather than countable. A week-long count converts that invisible habit into a visible pattern, which is the precondition for deciding what to actually change — including which of the other practices here addresses your specific highest-switch periods. Without that audit, it's easy to apply a fix like protected blocks to the wrong part of the day.

If I can only do one of these, which one matters most?

There isn't a single practice that dominates, because they intervene at different points in the same process: before the switch (stopping points, batching small tasks), during protected time (blocking distraction), in the environment (closing tabs), in the gap between tasks (transitions), and in coordination with others (closure signals). Measuring your switching frequency first is the one practice that tells you which of the others would address your actual pattern, since it reveals your specific high-switch periods and trigger categories rather than assuming a generic fix.

How do you choose between these?

Start with what the situation actually permits. If you control your calendar and the interruption source is external, block off a protected window — it removes residue at the source rather than managing it after the fact. If interruptions are unavoidable (an open-plan office, an on-call role), focus instead on what you control at the point of switching: reach a stopping point, close the tabs and documents tied to the task you're leaving, and take a brief low-demand transition before starting the next thing. If the task queue itself is the problem — small requests keep landing mid-focus — sequence your day so small tasks are cleared before the large one starts rather than during it. If the work is collaborative, add a closure signal regardless of which other practice you're using, since it prevents residue from re-entering through a follow-up interruption. When none of this feels applicable yet, spend a week counting switches first — the pattern it reveals will point at which lever is actually worth pulling.

What these approaches do not settle

Reaching a stopping point and blocking distraction windows both rest on Sophie Leroy's 2009 observational findings; the rest — closing tabs, designing transitions, signaling completion to a team, counting your own switches — are practitioner extensions of the residue and Zeigarnik mechanisms rather than practices Leroy herself tested. Several of them also assume a degree of control the reader may not have: protected blocks need organizational permission, five-minute transitions are impractical in fast-switching or high-urgency roles, and self-counting switching frequency changes behavior while you're measuring it, so treat the resulting number as a directional estimate, not a precise baseline.

Practice this with IX Coach

Practice this with IX Coach

Frequently asked questions

Attention Residue: Sophie Leroy’s 2009 Paper, Explained

Attention residue, coined by organizational behavior researcher Sophie Leroy in her 2009 paper "Why is it so hard to do my work? The challenge of attention residue when switching between work tasks" (Organizational Behavior and Human Decision Processes, 109(2), 168-181), refers to the partial attention that stays on a previous task after you switch to a new one. Even when you’ve physically moved on, part of your cognitive bandwidth remains occupied processing the unfinished or interrupted task — degrading performance on the new task. Leroy’s original lab experiments support the effect; applied consequences (meeting performance, creative work quality) are plausible extensions.

How do you reach a clear stopping point before switching tasks?

Leroy found that residue is lower when a task is complete or when the person has a clear plan for how to continue. A natural stopping point — a completed section, a saved draft with a clear next sentence, a filed note — creates a cognitive bookmark that reduces the brain’s background processing of the unfinished task. The residue mechanism is related to the Zeigarnik effect: the brain keeps incomplete tasks active; bookmarking reduces the sense of incompleteness.

How do you block focused work in windows protected from interruptions?

Residue is generated by switching; eliminating interruptions during key work periods eliminates residue at the source. Protected windows allow a task to build and maintain the deep engagement state in which working memory is fully allocated to the current task. Research on flow and deep work convergently shows that high-quality output depends on sustained periods of uninterrupted focus rather than accumulated hours with frequent interruptions.

How do you batch small tasks to completion before starting large ones?

Switching from a large, unfinished task to handle a small task creates residue on the large task. Reversing the sequence — completing small tasks first, then entering the large task — means the large task begins with a clean slate rather than accumulated residue. This also exploits the Zeigarnik mechanism inversely: completing small tasks closes their loops, preventing them from intruding during large-task focus.

How do you close browser tabs, apps, and documents between tasks?

Open tabs and files are visual cues that maintain activation of the previous task’s context. The brain uses environmental cues as external working memory — open tabs serve as reminders that keep the previous task partially active. Closing them removes the environmental residue, complementing the cognitive residue reduction of reaching a stopping point. This is environment design applied at the task-switching level.

How do you design transitions between tasks, not just the tasks themselves?

The residue from a completed or interrupted task dissipates over time, but the speed of dissipation depends on cognitive engagement. Jumping immediately from task A to task B at peak urgency keeps both in active competition. A brief, low-demand transition — a short walk, a deliberate breath, a written closure note — allows residue to settle before the new task begins. This is an active strategy for managing what would otherwise be a passive degradation.

How do you signal clearly when you’re done with a request before moving on?

Collaborative work generates residue in both parties. When a collaborator sends a request and receives no closure signal, they carry an open loop ("did they receive it? Have they started? Will they need me?"). Clear closure signals — a brief completion message, a status update — close the loop for both parties simultaneously, reducing the system-wide residue load and the resulting follow-up messages that generate further interruptions.

How do you track your task-switching frequency for one week?

People systematically underestimate how often they switch tasks, because many switches are brief and feel automatic (glancing at a phone, checking a tab). Self-monitoring converts an unconscious habit pattern into a visible behavior, which is a precondition for intentional change. The week-long audit also reveals the specific high-switch periods and trigger categories (notification types, meeting patterns, specific colleagues) that generate the most residue.

Is closing browser tabs basically the same thing as finding a stopping point?

They target the same residue but at different layers. Reaching a stopping point closes the cognitive loop inside your head — the task itself feels complete or has a clear next step. Closing tabs and documents removes the external cues that would otherwise keep reactivating that loop from outside. Doing the first without the second means the task still whispers at you every time you glance at the open tab; doing both removes the residue from two directions at once.

Should I clear small tasks first or block off time for deep work first?

Do both, in that order: clear small tasks, then enter the protected block. Batching small tasks to completion first means the large task starts with a clean slate instead of carrying residue from interruptions handled mid-session. The protected window then prevents new small tasks from intruding once the large task is underway. Reversing the order defeats the point — a distraction-free block that opens with three unfinished quick tasks still starts contaminated.

Do you have to follow these steps in order?

No single sequence is required, but two pairs have a natural order. Small tasks should be cleared before a large focus block begins, not handled mid-block, because handling them mid-block is what generates the residue the block is meant to prevent. A transition ritual comes after a stopping point is reached, not instead of one — the transition gives residue time to dissipate once the task is actually closed. Outside those two pairings, the practices are independent and can be adopted in any order.

Why doesn't just taking a break between tasks fix attention residue?

Because a break is not automatically low-demand, and it is the demand level of the transition that determines whether residue actually dissipates. Checking email or Slack during a break introduces new content that generates its own residue rather than clearing the old task's residue, so time passes but nothing is resolved. A transition only works when it stays low-cognitive-demand — a short walk, a breath, a brief closure note — so the previous task's activation can settle before the next one begins.

Does attention residue only affect the person switching tasks, or does it spread to other people?

It spreads. When a task is collaborative, an open loop exists on both ends — the person who completes the work and the person who requested it and is waiting to hear back. If the requester gets no closure signal, they carry an unresolved loop about whether the work is happening, which frequently surfaces as a follow-up interruption that then generates residue in the person who was working. A brief explicit completion signal closes the loop on both sides at once, which is why it functions as a residue-reduction practice for the whole working relationship, not just for the individual.

Why would I bother counting how often I switch tasks?

Because most people cannot accurately name their own switching pattern without counting it, since brief switches like glancing at a phone or a tab feel automatic rather than countable. A week-long count converts that invisible habit into a visible pattern, which is the precondition for deciding what to actually change — including which of the other practices here addresses your specific highest-switch periods. Without that audit, it's easy to apply a fix like protected blocks to the wrong part of the day.

If I can only do one of these, which one matters most?

There isn't a single practice that dominates, because they intervene at different points in the same process: before the switch (stopping points, batching small tasks), during protected time (blocking distraction), in the environment (closing tabs), in the gap between tasks (transitions), and in coordination with others (closure signals). Measuring your switching frequency first is the one practice that tells you which of the others would address your actual pattern, since it reveals your specific high-switch periods and trigger categories rather than assuming a generic fix.

Research

Related concepts

Articles that cover this