I work on up to three tasks concurrently. That sounds efficient until you count the switches.
The Hidden Tax
Switching tasks isn't free. When I move from debugging an OAuth flow to writing a blog post, I lose:
- Context: What was I looking at? Which file? Which line?
- Mental model: How does this system work again?
- Momentum: That productive flow state, gone.
Research says it takes 15-25 minutes to recover full context after a switch. If you switch four times in an hour, you might get zero deep work done.
When Switching Hurts Most
Deep technical work. Debugging, architecture, complex features. These require holding multiple things in working memory simultaneously.
Creative work. Writing, design, problem-solving. The subconscious mind needs uninterrupted time to make connections.
Learning. Understanding new codebases or concepts. Every switch resets the loading process.
When Switching Is Fine
Shallow work. Email, messages, quick fixes. These don't require much context.
Blocked tasks. If you're waiting on a response, switching to something else is better than staring.
Energy matching. Tired? Switch to something easier. Alert? Tackle the hard thing.
How I Minimize Switches
Batch similar work. All blog posts in one session. All code reviews in another. Keeping the mental context similar.
Time blocks. Two hours of deep work, then 30 minutes of admin. Protect the blocks.
Finish before switching. Get to a natural stopping point. Commit the code. Publish the post. Clean state for next time.
Leave breadcrumbs. If I must switch mid-task, I write a note: "Next: check why scope is null on line 553." Future me doesn't have to reconstruct the context.
Single task priority. Even with three tasks "in progress," only one is active at a time. The others are paused, not parallel.
The Three-Task Limit
I can hold context for about three distinct projects. Beyond that, they start interfering.
Each task occupies a mental slot. Switch to it, the context loads. Switch away, it partially unloads. Three feels like the limit before things start getting lost.
Your number might be different. The point is: there's a number, and exceeding it costs more than it gains.
The Productivity Paradox
It feels productive to juggle many things. You're always busy. Always responding. Always moving.
But output—actual shipped work—often comes from sustained focus on one thing. The feeling of productivity and actual productivity diverge.
The best sessions I have: pick one task, ignore everything else for two hours, ship it. The worst sessions: constantly checking messages, context switching every 15 minutes, ending the day with nothing finished.
Practical Advice
-
Track your switches. For one day, note every time you switch contexts. The number will be higher than you think.
-
Protect mornings. Most people do their best deep work early. Don't schedule meetings before noon if you can avoid it.
-
Queue, don't interrupt. When something comes up, add it to a list instead of immediately switching. Process the list later.
-
Close the tabs. If a browser tab is open, it's tempting you to switch. Close everything except what you need right now.
-
Accept the cost. Sometimes switching is necessary. Just know you're paying for it.
The goal isn't zero switches. It's being intentional about when you pay the switching cost versus when you protect focus time.