For most of my career, every day looked the same: a little bit of everything. Some writing, some meetings, some admin, some email, all blended together into a smoothie of half-focus. I felt busy from morning to night, and I couldn't have told you what I'd actually accomplished.
Then I tried something that felt almost reckless. Instead of doing a bit of everything every day, I gave each day one job. Monday for one kind of work, Tuesday for another, and so on.
I expected it to feel rigid. Instead it felt like someone had cleared a fog I didn't know I'd been living in. Here's what actually happened.
Batching means grouping similar tasks together and doing them in dedicated blocks, instead of switching between different kinds of work all day. It works because switching between task types carries a hidden cost, and batching eliminates most of it.
What I found after a week of batching:
Here's the thing nobody warns you about a varied day: every switch costs you.
When you jump from writing to a meeting to email to a different project, your brain doesn't switch cleanly. A piece of your attention stays stuck on the last thing while you try to start the next. That residue is real, and it's expensive. You're never fully in any task, because you just left another one and you're already bracing for the next.
I'd always assumed a varied day was efficient. I was "making progress on everything." What I was actually doing was paying a small attention tax on every single transition, dozens of times a day, and wondering why I ended each day fried with little to show. The cost of that switching is well documented — the American Psychological Association has written extensively about how task-switching quietly eats into both speed and accuracy. Eliminating it was one of the bigger wins in the productivity system that finally survived my burnout.
A day of switching feels productive and isn't. You're busy paying the toll between tasks, not arriving anywhere.
Batching attacks this directly. Stay in one type of work and there's nothing to switch from. The residue never builds. You sink into the task and stay there.
I didn't want a complicated system. I gave each weekday a theme and let it shape everything else.
The rule wasn't rigid to the minute. Things bled over sometimes. But the theme set the default, and the default did the heavy lifting. When something came up, I'd ask "which day does this belong to?" instead of doing it right now and shattering my focus.
The meetings part alone was worth the whole experiment. Pulling them into one day meant my deep-work days had long, unbroken stretches — the kind where the good work actually happens, and the natural home for the 90-minute blocks I now build my best work around.
The first full week, three things stood out.
First, the mental tiredness dropped. By Friday I wasn't the wrung-out husk I usually was. Less switching meant less of that specific drain, and it was a bigger share of my fatigue than I'd ever realized.
Second, the work itself improved. Spending a whole block writing, I'd warm up and hit a depth I never reached in scattered 30-minute windows. The same was true for every batch. Staying in one mode let me actually get good at the mode for a few hours.
Third, I stopped feeling behind on everything at once. When email had its own slot, I didn't feel guilty ignoring it during deep work — it had a time, and that time wasn't now. The nagging sense of a dozen neglected fronts mostly disappeared.
| Before batching | After batching |
|---|---|
| A bit of everything, all day | One kind of work per block |
| Constant switching fatigue | Steadier energy through the week |
| Shallow progress on many things | Deep progress on one thing at a time |
| Always vaguely behind | Each thing had its slot |
It wasn't all clean wins. Batching has real downsides, and pretending otherwise would be dishonest.
The biggest one: urgency doesn't respect your themes. Something genuinely needs handling on a deep-work day, and you either break the batch or make someone wait. I had to get comfortable with reasonable delays — most things can wait a day, but some truly can't, and rigidity there would've been foolish.
The second: some work just doesn't batch well. A few things need a little attention every day, and forcing them into one block makes them worse. I learned to keep a small daily sliver for those rather than jam everything into a theme.
The third was internal. On a meetings day, part of me itched to do "real work" instead. I had to trust that the deep-work days would come and that protecting them required spending this day on the people-stuff. Discipline, basically. The friction was real but manageable, and the gains outweighed it easily.
A week in, the answer was an obvious yes, and I've kept a version of it since.
The honest summary: batching didn't add hours to my week. It made the hours I had go further by killing the switching tax I'd been paying without noticing. I traded the false comfort of touching everything every day for the real satisfaction of finishing things.
If you want to try it, you don't need to overhaul your whole week at once:
The fog I cleared wasn't a lack of effort. It was a lack of structure. Giving each day one job was the structure I'd been missing.
One last thing worth saying: batching changed how I felt at the end of the week, not just what I produced. I used to reach Friday unable to point to anything specific I'd done, just a vague sense of having been busy and tired. Now each day leaves a clear mark — Tuesday was the writing, Thursday was the people, Monday cleared the decks. The week has a shape I can actually remember, which makes it far easier to know what to keep, what to cut, and what to plan for the next one. That legibility turned out to be a quiet gift of its own. A week you can describe is a week you can improve.
If giving your week a shape appeals to you, it's worth exploring how batching slots into a broader, more sustainable way of structuring your time.
Q: What if my job is too reactive to batch? Even reactive jobs usually have some controllable time. Batch what you can — process email in two blocks instead of all day, group the calls you do control. You won't get a perfectly themed week, but reducing switching even partway helps a lot.
Q: Won't people be annoyed if I'm not always available? Less than you'd fear. Most things can wait a day, and people adapt quickly to "I do calls on Thursdays." For genuine emergencies, stay reachable. The goal is fewer needless interruptions, not becoming a hermit.
Q: How big should a batch be? Big enough to get past the warm-up and into real depth — usually at least 90 minutes, ideally a half-day for deep work. Tiny batches don't capture the benefit, because you barely settle in before it's over.
Q: What about tasks that need daily attention? Keep a small daily slot for those rather than forcing them into a theme. Batching is for grouping similar work, not for ignoring things that genuinely need everyday touch. A little flexibility keeps the system realistic.
I spent years doing a little of everything every day and ending each one exhausted with nothing finished. Giving each day a single job didn't make me work harder. It made the work land.
Stop doing a bit of everything every day. Do one thing well, then the next. The switching was the tax all along.
If your days feel like a blur of half-focus, try giving just one of them a single job this week. You might be surprised how much fog lifts when you stop paying the toll between tasks.
I spent years saving the hardest task for when I 'felt ready.' Doing it first instead quietly fixed my focus, my dread, and my output.
I tracked every distraction for a week and was horrified by what I found. Then I fixed the three that mattered most.
I tried every budgeting app and spreadsheet and quit them all within a month. Here's why budgets fail and the boring system that finally stu…
Comments
Sign in to join the conversation
No comments yet. Be the first to share your thoughts!