I Batched My Whole Week. Here's What Happened.

I Batched My Whole Week. Here's What Happened.

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.

Quick Answer

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:

• The constant low-grade exhaustion of switching dropped sharply
• Each kind of work got better, because I stayed in one mode
• I finished more while somehow feeling less rushed
• Some friction showed up too, and it was worth managing
• The rhythm made my whole week easier to plan

The hidden tax I was paying all day

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.

Photo by freestocks.org on Pexels

How I actually carved up the week

I didn't want a complicated system. I gave each weekday a theme and let it shape everything else.

• Monday — planning and admin. The boring necessary stuff, all in one place, out of the way for the week.
• Tuesday and Wednesday — deep work. My two best days, fully protected for the hardest creative work. No meetings if I could help it.
• Thursday — meetings and calls. Everything that needed other people, stacked into one day.
• Friday — review, loose ends, lighter work. Tie off the week, prep the next one.

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.

What got better, almost immediately

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

Photo by Pew Nguyen on Pexels

The friction nobody mentions

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.

Would I keep doing it?

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:

1. Pick one type of work and give it a dedicated block. Start with meetings or email — the easiest to batch.
2. Protect one half-day for deep work. No switching, no meetings, one task.
3. Notice the difference for a week before changing more. Let the results convince you.
4. Stay flexible on genuine urgency. Batching is a default, not a cage.

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.

The bottom line

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.

Key Takeaways

• Batch similar tasks into dedicated days (e.g., Monday for admin, Tuesday/Wednesday for deep work) to eliminate the hidden cost of task-switching, which drains energy and reduces focus
• Protect deep-work days by grouping meetings/calls into a single day (e.g., Thursday), creating long, uninterrupted blocks for high-quality output
• Start small: pick one task type (e.g., email or meetings) and batch it into a single block for a week to experience the benefits before scaling the system
• Accept that some tasks resist batching (e.g., daily touchpoints) and keep a small daily slot for them—flexibility prevents rigidity from breaking the system
• Use batching to create a memorable week: each day leaves a clear mark (e.g., 'Tuesday was writing'), making it easier to plan, improve, and avoid the blur of scattered work
• Trust the default: when interruptions arise, ask 'Which day does this belong to?' instead of breaking focus—most things can wait, but genuine urgency should override the batch