What is Context Switching? The Hidden Cost of Jumping Between Tasks

Context switching is the act of shifting attention from one task or project to another — answering a Slack ping mid-report, hopping between three projects in an afternoon, "quickly checking" email during deep work. Borrowed from computing (where a CPU pays a real cost to swap processes), the term names the most underestimated tax in knowledge work.

The cost is not the seconds spent switching — it's what happens after. Psychologist Sophie Leroy called it attention residue: when you switch tasks, part of your attention stays stuck on the previous one, degrading performance on the next. Research on interrupted work (Gloria Mark, UC Irvine) found it takes around 23 minutes to fully return to a task after an interruption; American Psychological Association summaries put the productivity loss from heavy multitasking at up to 40% of productive time.

The Symptoms

• Busy, exhausting days that produce nothing you can point to
• Reading the same paragraph three times after checking a notification
• Every project 80% done, nothing shipped
• Feeling most productive at 7am or 9pm — the only unfragmented hours

How to Cut the Switching Tax

1. Batch shallow work. Handle email and messages in 2–3 fixed windows instead of continuously (task batching).
2. Block real work. Give demanding tasks protected 60–120 minute blocks (time blocking) and treat pings as scheduled, not instant.
3. Theme your days. Assigning days or half-days to one project (day theming) turns dozens of small switches into one big one.
4. Close loops before switching. When you must switch, write one line — where you stopped, what's next. It's the cheapest antidote to attention residue.
5. Limit work in progress. Fewer active projects means structurally fewer switches; that's half the point of Personal Kanban and an honest weekly plan.

You can put a number on your own tax with the free distraction cost calculator, then design next week around fewer, longer blocks in a weekly planner.

Related terms: Deep Work · Task Batching · Day Theming