I didn’t believe in batching for a long time. It sounded like the kind of tip that works in a productivity book and nowhere near a real day. Then I actually timed my week, roughly, and found something uncomfortable: I was doing the same categories of small work over and over, scattered through the day, and paying a switching cost every single time. Batching, once I tried it properly, gave me back close to an hour a day. Here’s what it actually looks like, because the concept is simple and the practice has a few traps.
The problem is switching, not the work
A batch of similar tasks done together is faster than the same tasks done one at a time, spread out. Not a little faster. A lot. The reason isn’t the tasks themselves, it’s the gap between them. Every time I stopped writing to fire off one email, I paid to leave writing and paid again to come back, and that round trip cost more than the email did.
Once I saw the day as a series of expensive switches rather than a series of tasks, batching stopped being a tip and started being obvious. Group the like things. Pay the switch once. That’s the whole idea.
What I actually batch
Email and messages. Twice a day, roughly 11:30 and 4, I do all of it in one pass. The rest of the day it’s closed. This was the hardest to accept and made the biggest difference, because I’d been checking mail maybe 30 times a day, and 30 tiny interruptions is a shredded day even if each one is short.
Calls and meetings. I try to stack them on 2 days and keep the others clear. A day with a meeting at 10, one at 1, and one at 3 isn’t a meeting day, it’s a day with no usable work in it, just 3 stumps of broken time between calls. Bunched together, they leave real blocks intact on either side.
Admin. The invoices, the forms, the small account chores, the receipts. All of it waits for one weekly session where I sit down and grind through the pile in admin mode. Done together they take maybe 40 minutes. Sprinkled through the week as they occur, the same tasks used to cost me double, because each one dragged me out of something better.
Errands. Same logic, offline. One trip that hits the post office, the shop, and the thing I need to drop off beats 3 separate trips, and I plan them that way now instead of leaving the house every time something comes up.
Where batching goes wrong
Two traps, both of which I fell into.
The first is batching too rarely. If I only did email once a day, genuinely time-sensitive things waited too long and people got stuck. Twice a day turned out to be my number: infrequent enough to protect focus, frequent enough that nothing important rots. The right interval depends on the work, and you find it by watching what actually breaks.
The second is batching things that shouldn’t wait. Not everything survives being held for a batch. If someone’s blocked on me and needs an answer in the hour, that’s not batch material, that’s now. Batching is the default for small recurring work, not a religion. The point is to protect focus, and holding a genuinely urgent thing hostage to a schedule does the opposite.
The quieter payoff
The hour a day is real and it’s what got me started. But the thing that kept me batching is subtler. My days stopped feeling frantic. When email happens twice instead of thirty times, when meetings live on 2 days instead of leaking into all 5, the day has shape. There are stretches where I’m doing one thing and stretches where I’m doing the small stuff, and they don’t bleed into each other.
That shape is worth as much as the time. The scattered version felt like being nibbled to death by tiny things all day. Batching gathers the small stuff into a few honest sessions and hands the rest of the hours back, clear and whole. Group the like things, pay the switch once, guard the blocks in between. It’s about the most useful habit I’ve got.