Task Batching
Also known as: batching, batch processing tasks
Task batching means grouping similar small tasks, emails, invoices, calls, edits, and doing each group in one dedicated block instead of scattering them across the day. It helps with procrastination two ways: you stop paying the mental cost of constantly switching contexts, and a batch of ten tiny tasks becomes one startable unit instead of ten separate chances to stall.
| Origin | Borrowed from manufacturing's batch processing; popularised for knowledge work by productivity writers in the 2000s, notably Tim Ferriss's batching of email in The 4-Hour Workweek (2007) |
|---|---|
| Time required | No extra time; a way of arranging existing work |
| Best for | email overload, admin-heavy roles, shallow-task sprawl, protecting focus blocks |
| Difficulty | Easy |
How to use task batching
- Watch your week and list the small recurring tasks that interrupt it: messages, approvals, expenses, tidying files.
- Sort them into categories that use the same tools and mindset.
- Give each category a recurring block: email at 11:30 and 16:00, admin Friday morning, calls Tuesday afternoon.
- Outside the block, capture new items to a list instead of doing them immediately.
- Inside the block, run the list top to bottom without deciding between items.
- Protect the gaps this creates for your real, deep work; that is the point of the exercise.
Task batching as a named productivity method has not been directly tested. Its rationale rests on task-switching research, which is solid: decades of experiments show that switching between tasks carries measurable time and error costs, and that these costs rise with task complexity. Rubinstein, Meyer and Evans documented these switch costs in controlled experiments, and Mark's workplace observation studies found that interrupted work is resumed slowly and at attentional cost. What the lab work does not show is how large the real-world productivity gain from batching your email is; the mechanism is proven, the applied effect size is not.
Rubinstein, J. S., Meyer, D. E., & Evans, J. E. (2001). Executive control of cognitive processes in task switching. Journal of Experimental Psychology: Human Perception and Performance, 27(4), 763–797.
Monsell, S. (2003). Task switching. Trends in Cognitive Sciences, 7(3), 134–140.
Mark, G., Gudith, D., & Klocke, U. (2008). The cost of interrupted work: more speed and stress. Proceedings of CHI 2008, 107–110.
Common mistakes
- Batching by urgency instead of similarity. The gain comes from staying in one mode, not from doing urgent things together.
- Checking email between batches 'just in case'. A batch schedule you override on demand is no schedule.
- Letting batch blocks swallow the day. Batching exists to compress shallow work, not to give it more territory.
Related techniques
Time BlockingTimeboxingDeep Work
Frequently asked questions
What is task batching?
Grouping similar small tasks and doing each group in one dedicated block, so you handle email, admin or calls in a few concentrated sessions instead of constantly through the day.
Why does task batching work?
Mainly by cutting task-switching costs, which are well documented in cognitive psychology: every switch carries a time and error penalty, and interrupted work is resumed slowly. Batching also turns many tiny start decisions into one.
How often should I batch email?
There is no researched number. Two or three fixed times a day suits most office roles; the working rule is the fewest sessions your job genuinely allows, announced to colleagues so expectations match.