Context switching is the most expensive thing you do all day, and you don't get a bill for it. You feel it as a vague tiredness at 5pm and a sense that you were busy but didn't move anything forward. The number people throw around to explain this is "23 minutes." It's worth knowing where that number comes from, because the real finding is more useful than the myth.
Where the "23 minutes" number comes from
It traces to Gloria Mark's 2008 study, *The Cost of Interrupted Work: More Speed and Stress*. Her team shadowed people doing real knowledge work and measured what happened after an interruption. The headline figure — about 23 minutes and 15 seconds — is the average time before someone returned to the original task, after detouring through other work in between.
That's the part most people get wrong. It isn't "every Slack ping costs you 23 minutes of staring at the wall." It's that an interruption rarely sends you back to where you were. It sends you somewhere else first, and the trip back takes a while.
The part nobody quotes
Mark found something counterintuitive: after an interruption, people often worked faster. They compressed the task to make up for lost time. But they paid for that speed with higher stress, more frustration, and more time pressure.
So the cost of context switching isn't only minutes. It's the felt experience of always being slightly behind, compensating, never quite in the deep part of the work. That's the tax that doesn't show up on any clock.
The hidden tax is reconstruction
Here's the mechanism underneath the number. When you get pulled away, you don't just lose your seat — you lose your state:
- The eight tabs you had open for one comparison
- Where you'd scrolled to in a long doc
- The exact second of the video you were taking notes on
- The paragraph you'd highlighted
- The decision you were 80% of the way to making
None of that is written down. It's held in your head, and your head dumps it the moment a higher-priority thing arrives. When you come back, you rebuild it from scratch. The rebuild is the expensive part — not the interruption itself.
How to cut the reconstruction tax
You can't stop interruptions. You can make the trip back cheap. A few things that actually work:
- Externalize state before you switch. The instant you're pulled away, your working memory is the worst place to store where you were.
- Save the whole posture, not a URL list. A list of links tells you *which* pages. It doesn't tell you where you were *on* them, or what you were deciding. A list of links throws away the part that took the effort. (Here's what a tab list can't save.)
- Make resuming one action, not a ritual. If getting back in costs ten clicks, you'll open social media instead. That's not weak willpower; it's friction doing exactly what friction does.
What we built
We got tired of paying this tax, so we built UNIHODL to collect it back. It captures your exact work state — tabs, scroll position, video timestamp, selected text, and the decision you were forming — and restores all of it in one click. Free, with unlimited saves.
If you run a company and live in 40 tabs across a dozen half-finished decisions, the founder and operator angle is written for you.
The interruption was never the problem. The cold start was.