The hidden tax on every task switch

You sit down to write the launch email. A Slack ping pulls you into a bug. Ten minutes later you are back on the email, except you are not, not really. Some part of your head is still chewing on the bug. The words come slower. You re-read the same sentence twice.

That fog has a name, and a body of research behind it.

Attention residue

The psychologist Sophie Leroy coined the term “attention residue” to describe what happens when you switch tasks: a piece of your attention stays allocated to the task you left, which reduces the working memory and focus available for the one in front of you (Leroy, 2009).

Two findings make this matter for anyone running real work:

1. It does not fade quickly. The performance drop persists through the next task rather than clearing after a brief adjustment. You do not “settle in” after a minute. You work degraded for a while.
2. Unfinished work is worse. The residue is strongest when the task you left was incomplete or time-pressured. Since almost no real task is ever truly “done” when you switch, this is the normal case, not the exception.

Leroy’s explanation is that we have a deep need for completion, so the brain holds onto open loops even when we consciously try to move on.

The re-entry cost on top

Residue is the invisible part. There is also a visible, measurable part: the time it takes to climb back into a task after you leave it. Research compiled by the American Psychological Association put the productivity loss from chronic switching as high as 40 percent, and Gloria Mark’s research at UC Irvine found it takes about 23 minutes to fully re-immerse after an interruption (summary).

Stack residue and re-entry together and the popular advice to “timebox a bit of everything” starts to look expensive. Every boundary you cross, you pay twice: once in degraded focus, once in reload time.

What this means for your day

The practical takeaway is not “never switch.” It is “switch deliberately, and rarely, and never inside a block of real work.” Concretely:

• Treat a focus block as belonging to one project. The moment you cross into a second project, the meter starts running.
• Minimize the number of distinct projects you touch in a single day. Two projects means at least one expensive switch. Four projects is death by a thousand re-entries.
• Protect the boundary, not just the time. Thirty quiet minutes on one thing beats sixty minutes split across two.

How 6s is designed around it

We treat the switch, not the task, as the thing to manage.

• Focus is project-scoped. Start the clock and you are working one project’s next move. There is no blended list inviting you to bounce between contexts mid-session.
• A work-in-progress nudge. When you have more than three active projects, 6s names the attention-residue tax directly and suggests pausing a few, because the cost of holding many open loops is exactly what Leroy described, scaled up to project level.
• One next move per project. Instead of a wall of tasks pulling your attention in ten directions, each project shows the single action to take next. Fewer open loops on screen means less residue in your head.
• Idle-aware timing. If you drift off mid-session, the clock notices and stops, so “time on task” reflects real, undivided attention rather than a tab left open while your mind wandered elsewhere.

Switching feels free in the moment. It is one of the most expensive things you do all day. 6s is built to make the cheap path, staying with one thing, also the easy one.