The real cost of context switching
· 5 min read

The real cost of a context switch is not the moment you glance at the other thing — it is the reload afterwards, when you have to rebuild everything you were holding in your head before the glance. The glance takes a second. The rebuilding is what quietly eats the afternoon.
This is why context switching feels cheap while it is happening and expensive only in retrospect, at five o’clock, when the day is somehow gone and the hard task is somehow still open.
You pay for the reload, not the glance
Hold a piece of real work in your head — a document half-argued, a bug half-cornered, a plan half-formed — and you are holding more than the words on the screen. You are holding what you were about to do next, which approaches you have already ruled out, where the tricky part is, and a half-formed sentence that exists nowhere except in your head.
None of that is written down, because writing it all down would take longer than the work. It lives in working memory, and working memory does not pause when you switch away. It drains. Answer one quick message and you return to find the structure partly collapsed: the next step is foggy, the ruled-out paths look open again, the held sentence has gone. So you re-read, re-derive, re-climb — and the re-climbing is the cost. The message took a moment; being back took much longer, and nothing on any clock recorded the difference.
The cost is invisible because switching feels like work
Nobody experiences a context switch as slacking. Answering the message was work. Checking the ticket was work. That is precisely what makes the habit so durable: every individual switch is defensible, and the price is paid later, diffusely, as a general sense of having been busy all day to no effect.
A day of constant switching produces a distinctive signature — lots of things touched, nothing finished, and a tiredness out of proportion to anything accomplished. The tiredness is real. It is the cost of a dozen reloads, experienced as one long afternoon. This is the fog that makes office pomodoro use feel so different from working at whim: not that the timer makes you faster, but that it stops you paying the reload tax a dozen times before lunch.
A bounded session is a contract against switching
The pomodoro’s countdown looks like the whole mechanism, but the deeper one is the boundary itself. When you start a session on one named task, you have signed a small contract: for this bounded stretch, everything else waits. Not forever — that would be unreasonable, and unreasonable promises get broken. Just until the bell.
The contract works because it converts an open question into a closed one. Without it, every arriving thought demands a fresh decision — deal with this now or later? — and each decision is itself a small switch. With it, the answer is pre-made: later, and later has a concrete time attached. The thought goes on the scrap of paper beside the keyboard and loses most of its power on the way down, because a written-down thing stops needing to be remembered, and being remembered was most of its noise.
In PetPomo the contract has a witness, which helps more than it should. The cat lies down when the session starts; abandoning the session means abandoning it mid-nap. Nothing terrible happens — the cat gets sad, nothing is lost — but the switch is no longer free and frictionless, and a switch with even a feather of friction on it gives you the half-second in which to choose not to.
Give the shallow work a session of its own
The messages, the small approvals, the five-minute errands — none of it is illegitimate work, and pretending you can ignore it forever is how the contract gets broken. The fix is not to resist shallow work but to batch it: give it its own session, with its own start and its own bell, and do all of it at once.
Batching wins twice. Each individual reply escapes its own reload cost, because replying to twelve messages in a row keeps you in one shallow context instead of yanking you through twelve deep-to-shallow round trips. And the deep work gets what it actually needs, which is not more hours but unbroken ones — a distinction that matters most when the hours are scarce, as anyone hunting focus between meetings already knows. One clean session in a fragmented day outweighs a whole morning of interleaved everything.
The tax, measured
The reload cost is not a productivity-blog invention; it is one of the most consistently measured effects in attention research:
| Finding | Key numbers | Source |
|---|---|---|
| Interrupted office work takes a long time to resume | Field studies found workers took on the order of 23 minutes to return to an interrupted task | Mark, Gudith & Klocke, CHI (2008) |
| People compensate by working faster — and pay in stress | Interrupted work was completed faster but with significantly higher stress, frustration and time pressure | Mark, Gudith & Klocke, CHI (2008) |
| Task switching carries measurable time costs even in the lab | Switch costs rose with task complexity; repeated switching can consume a large share of productive time | Rubinstein, Meyer & Evans, JEP: Human Perception and Performance (2001) |
| Attention doesn’t fully move on — part of it stays behind | “Attention residue” from an unfinished task measurably degrades performance on the next one | Leroy, Organizational Behavior and Human Decision Processes (2009) |
Leroy’s finding is the scientific version of this article’s opening claim: you pay for the reload, not the glance — and you start paying before you even notice you switched.
The notification question
Which leaves notifications, the industrial machinery of the context switch. The uncomfortable truth is that a notification does its damage even when you do not act on it. The buzz you heroically ignore still lands, because ignoring it takes a decision, and the decision is itself the switch — small, but you have already paid for the glance-sized part.
So during a focus session the goal is not resisting notifications but not receiving them: phone face down and silent, the noisy tabs closed, the chat app quit rather than minimised. This feels drastic until you remember the contract’s other clause — it ends. The bell rings, the messages get their turn, and anything genuinely urgent has a phone number. A session timer is, in the end, just a machine for making “not now” both honest and temporary.
Context switching will never cost nothing; work is interruptible and life is not tidy. But the tax is mostly optional, and the way to stop paying it is not discipline in the moment — it is a boundary set before the moment arrives. Sign the small contract, put the thought on paper, and let the bell decide when the world gets you back.
Comments
Loading comments…
Keep reading 🐾

What your focus stats actually tell you — and what they don't
Focus time tracking stats are a mirror, not a scoreboard. Which numbers deserve your trust, which ones flatter you, and how to read a week kindly.

Making the Pomodoro Technique survive an office job
The Pomodoro Technique was designed for people who control their own time. Here is how to make it survive Slack, meetings and an open-plan office.

One task per session: the rule that makes pomodoro work
Pomodoro sessions fail when they carry three tasks. Why naming one task before you press start matters more than the timer itself, and how to slice big work.