Context switching is not the enemy. Invisible switching is.
Some switches are how good work happens. The dangerous ones are the ones you never notice you made.
The productivity internet has decided context switching is a sin. Every switch costs you, the story goes, so the goal is to eliminate them. It's a tidy message, and it's wrong in a way that makes people feel worse without helping them.
Plenty of switches are exactly how good work happens. You look up a reference, you step away to think, you check one fact and come back. Those are deliberate, in service of the task, and usually fine. Treating them as failures just adds guilt to a normal working day.
The problem is the reflex switch
The switches that quietly wreck a day are the ones you don't decide to make: the reflexive alt-tab to Slack between two lines of code, the inbox check you don't remember initiating. They're cheap individually and invisible in aggregate — which is exactly why they accumulate.
And they have a tail. When you jump away mid-task, part of your attention stays stuck on what you left — "attention residue" — and it drags on whatever you turn to next, especially when the first thing felt unfinished. So the reflex switch costs you twice: once to leave, and again to fully arrive somewhere else.
- 1.Leroy (2009) — Attention residue — Leroy, S. "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.
- 2.Rubinstein, Meyer & Evans (2001) — Task-switching costs — Rubinstein, J.S., Meyer, D.E. & Evans, J.E. "Executive control of cognitive processes in task switching." Journal of Experimental Psychology: Human Perception and Performance, 27(4), 763–797.
You can't manage a switch you didn't notice you made.
Make it visible, then decide
The fix isn't a vow to never switch. It's visibility. Once you can see which switches were reflexes and which were choices — and which hour of your day they cluster in — you can cut the ones that aren't earning their place and keep the ones that are. That's a decision you get to make, not a rule imposed on you.
Tomorrow, find your single most fragmented hour and ask one honest question about it: which of those switches did I actually choose? Keep those. Notice the rest.
FocusMirror privately tracks where your focus goes on macOS — blocks, not scores, and one thing to sharpen tomorrow.
You were busy all day. So why can't you say what you actually did? The gap is usually fragmentation, not laziness.
A single number is the most-requested feature we'll never build. Here's the case against it.