The core research
Gloria Mark’s lab at UC Irvine studied knowledge workers in office settings, measuring interruption frequency and recovery time. The headline finding: after an interruption, workers take an average of 23 minutes and 15 seconds to return to the original task at full focus.
The interruption itself is brief (a Slack notification, a “got a sec?” interruption, an email check). The cost is the recovery, which dwarfs the interruption duration. This is why context switching is a hidden tax — the cost doesn’t show up in the moment, it shows up in the hour that followed.
What’s actually happening cognitively
Three layers compound:
- Working memory clearing. The task you were in had loaded context (what you were thinking about, where you stopped, what was next). Switching requires unloading that.
- New context loading. Whatever you switched to has its own context that has to load.
- Re-engagement. Returning to the original task requires reloading its context plus rebuilding the cognitive momentum, not just remembering where you stopped.
The 23-minute average is recovery to the same depth of engagement. Recovery to a basic re-orientation is faster — often 2-5 minutes. The expensive recovery is back to flow state.
Why “just checking” is more expensive than it feels
Checking email or Slack feels like a 30-second action. It’s actually a 30-second action plus a 23-minute recovery cost. A professional who checks email 15 times per day pays roughly 5 hours of recovery cost — more than the email volume itself.
This is the math that justifies batched email processing. Checking email 4 times per day instead of 15 times saves roughly 3 hours of recovery cost per day, at no real loss of responsiveness for most professional contexts.
How AI assistants reduce context switching
The interruption that triggers a switch is often “did anything important come in?” The implicit question: should I drop what I’m doing? Most of the time the answer is no, but you can’t know that without checking.
A proactive AI assistant inverts the model. The assistant checks email continuously and surfaces only the items that warrant interruption. The user no longer interrupts themselves to check — the assistant flags the few moments that actually justify a switch. Context switching cost drops proportionally to how well the assistant filters.
Where alfred_ fits
alfred_ runs continuous triage and surfaces only the small subset of email that requires user judgment — typically 5-15 items per day from a 100+ message inbox. The user doesn’t need to check the inbox for the other items; they’re handled or queued. The reduction in user-initiated email checks substantially reduces context switching cost over a week.
What context switching isn’t
It isn’t multitasking — true simultaneous task execution is mostly impossible for cognitive work. Context switching is sequential task swapping with a transition cost. It also isn’t always bad: brief switches to recover from focused work (a walk, a stretch, a non-cognitive break) restore capacity. The expensive switches are between cognitive tasks at depth.
