Batching and Its Limits
Grouping similar work to avoid switching costs. Works well for a narrow class of tasks and is widely applied to tasks where it makes things worse.
Batching means doing similar things together rather than as they arrive. The logic is sound and the application is frequently wrong. Teams investigating the same pattern can use the service-desk workflow to see where working time is being absorbed, then discuss the surrounding process; the record should reveal friction without turning ordinary pauses into a performance verdict.
Where it works
Low-switching-cost, repetitive work: email, invoices, expenses, filing, small approvals.
Work where setup is expensive and reusable: anything requiring a tool, a place or a state of mind that takes time to enter.
And errands, which is where the concept originated and where it is unambiguous.
The common factor: the items are interchangeable and individually short.
Where it fails
Work requiring depth. Batching three demanding tasks does not remove switching between them; they remain different problems.
Anything time-sensitive. Batched email means somebody waits, and if the waiting blocks them your batch has moved the cost rather than removed it.
Work whose items are not actually similar. "Calls" is not a category if one is a negotiation and one is a scheduling confirmation.
And anything where the batch grows faster than you process it, which converts a small recurring cost into a periodic ordeal.
The email case specifically
Batching email is the standard recommendation and it works for many people.
The cost lands on others, and whether that is acceptable depends on your role: for reactive work it is not.
Twice a day is the arrangement most people settle on, and the argument for it is the switch count rather than the time spent.
Announce it if others depend on you, which converts an unpredictable delay into a known one and removes most of the objection.
Batch size
Large batches feel efficient and produce their own problems: fatigue, declining quality, and a block long enough to displace other work.
Most batching benefit arrives early — grouping four items captures most of what grouping twenty does, without the drag.
Prefer several small batches to one large one for anything requiring attention.
The accumulation trap
A batch is a queue, and queues need capacity.
If the arrival rate exceeds what you clear, the batch is not a method but a backlog with a name.
Watch the size at the start of each batching session: growing means the approach is not working, whatever the theory says.
What to batch, practically
Administration, which is the clearest case and is covered in its own note.
Communication, with the caveats above.
Anything requiring a specific tool or location.
And decisions of the same kind, which is underused: making six similar small decisions together is measurably easier than making them scattered.
What not to batch
Creative or analytical work of different kinds.
Anything where a delay has a cost to somebody else that exceeds your saving.
And your one protected block, which should contain a single thing.
What to check
What are you currently batching, and are the items genuinely similar?
Is any batch growing week on week?
Who pays for your batching delay, and do they know about it?
And have you batched something that needs depth, where it is costing you rather than saving?
Watch the batch size
A batch is a queue and queues need capacity.
If it grows week on week, the approach is not working whatever the theory says, and you have converted a small recurring cost into a periodic ordeal.
Worth keeping in mind
Announce the delay if others depend on you. Converting an unpredictable wait into a known one removes most of the objection to batching and costs one sentence.
In short
Most batching benefit arrives early: grouping four items captures most of what grouping twenty does, without the fatigue and the declining quality that a large batch brings..
The point
Batch administration, communication with caveats, anything needing a specific tool, and decisions of the same kind.
Not creative work, not anything time-sensitive to others. For a complementary perspective on work, measurement or planning, consult Todoist.