Why Does Multitasking Make Me So Tired (When I'm Not Doing Anything Hard)
You spent the day in low-stakes meetings and emails, and you're more wiped out than after deep work. Here's what your brain was actually doing — and how to stop.
You spent the day on relatively easy things. Six small meetings. Forty messages. A bunch of admin. Nothing intellectually heavy. By 4 p.m. you're more wiped out than you'd be after a day of actual hard work — and you can't quite explain why. The exhaustion feels disproportionate to what you actually did, which makes it feel like a personal failing on top of being tired.
It isn't. Switching between many small things has a real cognitive cost that doesn't show up as 'difficulty' but does show up as fatigue. Your brain isn't tired from any one task — it's tired from loading and unloading the context for fifty of them. Once you understand the mechanism, you can recognize it, predict it, and partially defuse it. Here's what's actually going on, and what to do about it.
Recognize the cost is in the switching, not the tasks
The tasks themselves were easy. What was expensive was every transition between them — pulling context for a new conversation, swapping mental models, rebuilding the thread of where you were. Each transition costs energy regardless of how easy the underlying task is. Forty switches between easy tasks is more tiring than two switches between hard ones. Naming this stops the 'why am I so tired, I didn't even do anything' loop.
Watch for invisible switches
Some switches don't feel like switches. Reading an email that mentions a different project pulls you into that project's mental space, even briefly, even if you don't take action. Looking at the calendar to remind yourself of a meeting reloads the meeting context. These small re-loadings happen dozens of times a day and contribute to the fatigue without registering as work. Once you start noticing them, you'll see how much of your day is invisible switching.
Cap the number of unique projects per day
Most people can hold context for three or four distinct projects in a day without significant switching cost. Above that, fatigue compounds fast. Look at your day: are you touching seven projects? Eight? You don't have to push them all forward. Pick the three or four that need real attention, and explicitly defer the rest to tomorrow. Reducing project count per day is one of the highest-leverage moves available.
Stop pretending email is one task
'Doing email' isn't one task — it's twenty different small contexts. Every email you read pulls you into a different project, person, decision. That's why an hour of email is more draining than an hour of deep work. The fix: don't 'do email.' Open it three times a day, in concentrated batches, with a clear stopping point. The same volume hurts less when it's not constantly tagged onto everything else.
Recover by going single-thread, not by going slack
When you're fried from switching, the instinct is to do nothing. The actual recovery move is doing one thing for a sustained stretch. Read a long article. Watch a movie. Take a walk and let your mind settle on one thread instead of bouncing. The fatigue isn't from effort — it's from fragmentation. The cure isn't rest, it's coherence. Even thirty minutes of single-thread time restores more than an hour of zoning out.
Cap the switching that's wearing you out
Batch Flow audits your real day, identifies where the invisible switching is, and builds a structure that gives you back coherence — without making you a hermit.