Attention Residue: The Hidden Cost of Context Switching

You finish working on Task A. You switch to Task B. You sit down at Task B and notice that, for some inexplicable reason, you cannot quite focus. Some part of your mind is still chewing on Task A. The cup of attention you brought to Task B is partly full of leftover Task A residue.

That experience has a name. Sophie Leroy, a professor at the University of Washington Bothell, called it "attention residue" in a 2009 paper that has become one of the most cited findings in modern workplace psychology. It describes a real cognitive cost that adds up in painful ways across a typical workday.

If you want a tool that helps structure your time around this finding, our Deep Work Timer supports the longer single-task blocks that minimise switching.

What Leroy actually found

In her original studies, Leroy gave participants a task to work on (a word puzzle) and then interrupted them to switch to a different task. Some participants were interrupted before completing the first task. Others were given time to finish.

When participants started the second task, their performance was measurably worse if they had been switched off the first task before completing it. The interrupted group showed slower reaction times, more errors, and less efficient processing on the new task. Leroy interpreted this as attention residue: cognitive activity related to the first task that lingered and consumed resources during the second.

The effect was larger when the first task was unfinished. It was also larger when the participants felt time pressure or had not had a chance to plan how they would return to the first task.

Subsequent work has refined the picture. Leroy and Schmidt's 2016 paper showed that the residue effect varies with personality and regulatory focus. People who are more goal-oriented and more focused on completing what they start tend to experience larger residue effects. People who switch more flexibly experience smaller residue, though the cost is not zero for anyone.

What this means in practice

The size of the residue cost depends on several factors.

Was the first task complete? Switching at a natural stopping point produces much less residue than switching mid-thought.

How cognitively demanding was the first task? Hard tasks produce more residue than easy ones.

How different is the new task? Switching from writing to coding produces more residue than switching from one writing task to another similar writing task.

How long is the new task? Brief new tasks suffer most from residue. Long sessions allow residue to dissipate.

What is your physical state? Tired, stressed, or hungry, you experience more residue from any switch.

The cumulative effect across a workday is the part that should worry knowledge workers. Each switch adds some residue. Multiple switches compound. By mid-afternoon, you may be carrying residue from a dozen recent task switches, each one consuming a small slice of attention.

This is why some days you feel like you "worked hard" but produced nothing meaningful. Most of your cognitive resources were spent paying the switching tax, not on the work.

Related: the literal switching cost

Attention residue is closely related to but distinct from what cognitive psychologists call "task switching costs". Rubinstein, Meyer, and Evans' 2001 paper measured the time cost of switching between simple cognitive tasks (categorising numbers as odd or even, then switching to categorising them as more or less than five). Even for trivial tasks, switching slowed performance by hundreds of milliseconds per switch and increased error rates.

For complex real-world tasks, the switch costs are much larger. Some estimates put the total switching cost at 20 to 40 percent of a typical knowledge worker's productive time. The number is hard to measure precisely, but the order of magnitude is well-supported.

Gloria Mark and colleagues' 2008 ACM paper on workplace interruptions found that after a typical interruption, it took workers about 23 minutes on average to return to their original task. Twenty-three minutes. Multiplied across a day with several interruptions, the math is brutal.

What modern work environments do wrong

The default architecture of modern knowledge work is hostile to focus.

Instant messaging culture. Slack, Teams, and email all assume that messages can arrive at any moment and should be checked frequently. Each glance at the messages is a switch, even if you don't reply.

Meeting fragmentation. Days with meetings every 30 to 60 minutes leave no continuous blocks long enough for the residue from the previous meeting to dissipate.

Open offices. Visual movement, ambient conversation, and unpredictable interruptions all force micro-switches.

Multi-project workloads. Many roles require working on three to five projects simultaneously. Switching between them throughout the day produces sustained residue.

Performative responsiveness. Many workplaces reward fast responses to messages, which incentivises constant switching even when nobody needs the immediate response.

None of these are designed to be hostile. They evolved organically from the assumption that knowledge workers can multitask without cost. The research is clear that they cannot.

What to do about it

The findings on attention residue point toward several practical changes.

Finish before you switch. When possible, take a task to a natural stopping point before moving on. The natural stopping point can be small: finishing a paragraph, completing a function, closing out a decision. Small completions matter more than perfect completion.

Batch similar work. Doing all your email at once produces less residue than scattering email through the day. Same with calls, code reviews, or any category of similar tasks. Batch by type.

Protect long blocks. A 90-minute block on one task minimises switches and gives residue time to dissipate within the block. This is the case for Deep Work over Pomodoro for hard cognitive tasks.

Plan the return. If you must stop a task before completion, take 30 seconds to write a "next step" note. Where exactly to resume. What problem to tackle next. This significantly reduces residue when you return.

Limit project count. Working on six projects in parallel produces more cumulative switching cost than working on two at a time and sequencing the others. Where you have control, prefer fewer concurrent projects.

Defend recovery time after deep work. After 90 minutes of intense focus, take a real break. A 15-minute walk produces deeper recovery than a 5-minute check-of-email.

Where Pomodoro fits

The Pomodoro Technique is sometimes criticised for forcing switches every 25 minutes, which seems counter to the attention residue finding. The criticism is partly right.

For deep cognitive tasks (writing complex documents, debugging hard problems, designing systems), Pomodoro's 25-minute blocks are too short. The setup cost approaches the block length, and the cumulative residue across breaks adds up. For these tasks, longer blocks beat Pomodoro, as our Deep Work vs Pomodoro piece explores.

For shallow but valuable work (email, code reviews, administrative tasks, studying familiar material), Pomodoro's structure does help. The setup cost for these tasks is low, so the 25-minute block contains real work. The forced breaks prevent the fatigue that would otherwise degrade performance.

Both methods agree on one thing: do not switch within a focus block. Whether the block is 25 minutes or 90, finish what you started before opening Slack.

The unfair reality of compatible vs incompatible interruptions

Not all interruptions are equal. Some research suggests that "compatible" interruptions (where the interrupting task is similar to the ongoing one) produce smaller residue than "incompatible" ones.

A programmer who pauses to answer a quick coding question from a colleague experiences less residue than the same programmer pausing to answer a question about a marketing campaign. The cognitive systems involved are similar in the first case; the brain does not have to fully reset.

This has a practical implication for team management. If interruptions are unavoidable, batching compatible interruptions together (one "questions hour" per day for similar topics) reduces total switching cost compared to randomly scattered interruptions throughout the day.

A realistic estimate of your own switching cost

If you want to estimate how much your switching is costing you, try this exercise for two days.

On day 1, work as you normally do. Note (just roughly) the number of distinct context switches you make. Count each task change, each email check, each notification glance, each conversation.

On day 2, deliberately batch your work into a few longer blocks. Email at three set times. Slack at two set times. One 90-minute block on your hardest task in the morning. One 90-minute block in the afternoon.

Compare what you actually produced on each day. For most knowledge workers, day 2 produces measurably more high-value output despite "feeling" less busy.

The "feeling busy" of day 1 is largely the cost of attention residue, paid in cognitive effort that did not produce work.

When attention residue is not the bottleneck

For some roles, attention residue is not the limiting factor on productivity. Front-line customer service, on-call medical work, and certain operational roles require continuous responsiveness, and the work itself is structured around small repeated interactions rather than sustained focus.

In these roles, the attention residue research is less directly applicable. The work has been designed around interruption tolerance, and the cognitive load of each task is intentionally bounded.

For most knowledge work, however, attention residue is one of the most underrated forces shaping daily productivity. The cost is invisible day to day but compounds dramatically across weeks and months.

FAQ

For related reading, see our pieces on Deep Work vs Pomodoro, flow state triggers, and time blocking. The full menu of focus tools sits in our focus hub.