Heuristic
Batch by setup state, not only by task label
The useful batch is the one that avoids rebuilding the same state.
When it fits
- Several small tasks require repeated setup such as opening the same system, entering the same workspace, making similar calls or preparing the same tools.
When to avoid it
- Do not batch merely to reduce the number of calendar blocks. Urgency, dependency, fatigue and customer delay can outweigh setup savings.
Why it matters
Group work when tasks share a meaningful setup: the same application, repository, physical location, people, permissions, equipment or mental rule set. 'Admin' is often too broad; five tasks called admin may require five different contexts. Start with the repeated setup you want to avoid, then choose a batch small enough that waiting or fatigue does not become the new cost. Task-switching research supports treating switches as real work, but it does not justify batching everything into large blocks.
An example
Reviewing several tickets in the same system can share filters, terminology and permissions; mixing a ticket, a call, a purchase and a code review under 'small tasks' does not.
Check your result
Every member of the batch shares a named setup cost, and the batch has a reasoned end condition.
Keep this limit in mind
- Do not batch merely to reduce the number of calendar blocks. Urgency, dependency, fatigue and customer delay can outweigh setup savings.
Connected ideas
Useful withTreat a rule switch as a setup cost
Evidence and sources
An integrative review reports performance costs in many dual-task and task-switching conditions compared with appropriate single-task controls.
Switching can be necessary and adaptive; the review does not imply that uninterrupted work or large batches are always optimal.