What does it mean that context switching has a hidden cost?

Every time you switch tasks, you pay a recovery tax — between 10 and 25 minutes of degraded cognition while your brain reloads the previous context. This cost is invisible because you feel busy the entire time.

Example: You are writing a design document. Forty minutes in, you hold the system's constraints in your head — three APIs, a race condition, a backwards-compatibility requirement. Your phone buzzes: a Slack message about an unrelated production alert. You glance at it for five seconds, decide it's not your problem, and return to the document. Except your brain doesn't return. It's now running two threads — the design and the alert — and it takes you 23 minutes to fully reload the design context you held moments ago. The five-second glance cost you a half hour of depth.

Try this: Choose one workday this week and track every task switch. Each time you shift from one task to a meaningfully different one — checking email during a writing session, responding to Slack during code review, answering a phone call during analysis — mark the time. At the end of the day, count your switches. Multiply the count by 15 minutes (a conservative midpoint from the research). Compare the result to your total work hours. The gap between how much time you thought you had and how much the switching consumed is your hidden cost made visible.