Answering one email, then patching a bug, then jumping on a quick call, then back to the email thread you half-forgot: this is how most knowledge workers spend their day, and it is quietly expensive. Every time you switch between unrelated tasks, your brain pays a tax that you rarely see on any invoice but always feel by 5 p.m. Task batching is the discipline of refusing to pay it.
The idea is simple: instead of interleaving different kinds of work, you group similar tasks together and handle them in dedicated blocks. All your calls in one stretch. All your invoicing in another. All your shallow admin in a third. You stop forcing your mind to constantly reload a new context.
The Hidden Cost of Switching
When you move from one task to another, your attention does not arrive cleanly. Part of it lingers on what you were just doing. Sophie Leroy, a professor at the University of Washington, named this attention residue in a 2009 paper in Organizational Behavior and Human Decision Processes. Her experiments showed that people who switched tasks under time pressure performed worse on the new task because a portion of their improve your focus was still stuck on the previous one.
The numbers around context switching are often inflated online, so treat the dramatic claims with skepticism. What is well established is more modest but still meaningful: switching has a measurable cost in time and accuracy. Research by Joshua Rubinstein, David Meyer, and Jeffrey Evans, published by the American Psychological Association in 2001, found that even brief mental "set-shifting" between tasks added time and that the penalty grew with task complexity. You do not lose 23 minutes every time you glance at Slack, but you do lose something, and it compounds across dozens of switches a day.
Switching is not free movement between tasks. It is a series of small re-orientations, each one charging your attention a fee you never agreed to pay.
How Batching Fixes It
Batching works because it lets you stay in a single mental mode. Writing requires a different posture than approving expenses, which requires a different posture than brainstorming. When you keep one mode running, you skip the warm-up cost over and over. You also build momentum: the second invoice is faster than the first, the fifth email reply faster than the second.
There is a practical bonus, too. Batching makes your day legible. When admin lives in a fixed window, it stops bleeding into your deep-work hours, and you stop checking the same systems repeatedly "just in case."
Step One: Audit Your Tasks
For one week, write down everything you actually do, not what you think you do. Be granular. You are looking for patterns. After a few days you will notice that your work falls into recognizable families:
- Communication: email, Slack, comments, replies to messages
- Administrative: invoicing, expense reports, scheduling, form-filling
- Creative or deep: writing, designing, coding, strategy
- Analytical: reviewing data, reading reports, planning
- Errands: small physical or logistical tasks that pile up
Step Two: Group Smartly
The obvious way to batch is by task type, but type is not the only axis. Three criteria matter, and the best batches usually satisfy more than one:
- By type: all the same kind of work (every reply, every call).
- By tool: tasks that use the same app or environment. If you have your design software open and your assets loaded, do all the design work before you close it.
- By energy: match the batch to your physiology. Demanding creative batches belong in your peak hours; mindless admin belongs in your afternoon slump, when your judgment is poorer anyway but the work needs little of it.
Step Three: Assign the Blocks
Now place the batches into your week. A workable default for many people looks like this:
- Morning (peak focus): one or two long blocks of deep, creative work, protected from interruption.
- Midday: a single communication batch to clear messages.
- Mid-afternoon: an admin batch for the low-energy slump.
- End of day: a short planning batch to set up tomorrow.
Inside a batch, a timed interval keeps you honest. Many people run their admin or communication batches as a couple of focused sprints with a short break between them; a tool like Pomodomate is well suited to fencing off that window so the batch does not quietly expand to swallow the afternoon.
The Communication Batch Deserves Special Mention
Email and chat are the worst offenders precisely because they masquerade as urgent. Most are not. Batching communication into two or three checkpoints a day, rather than a continuous trickle, is one of the highest-leverage changes you can make. Cal Newport argues this point forcefully in Deep Work (2016): the constant availability that feels productive is often the very thing destroying your capacity for valuable, undistracted output.
A practical setup:
- Close your email client and chat app outside the batch windows.
- Turn off notification badges and sounds; they invite the switch you are trying to avoid.
- Tell colleagues your response windows so urgency has a known channel (a call) and everything else can wait.
Batching Is Not the Same as Time Blocking
The two are often confused. Time blocking means assigning a specific task to a specific slot on your calendar: "10:00–11:00, write the proposal." It is about when a given task happens. Task batching is about grouping similar tasks so they run together; the grouping comes first, and you may then time-block the batch.
In practice they pair well. You batch your tasks by type and energy, then drop those batches onto the calendar as blocks. Batching decides the contents; time blocking decides the schedule. You can do either alone, but together they remove most of the friction from a day.
Where Batching Falls Short
Batching is a tool, not a religion. Genuinely urgent work taking breaks the rule, and it should. If a client outage lands at 11 a.m., you do not wait for the afternoon admin block. The goal is to make switching a deliberate choice rather than a reflex, not to become rigid. Some roles, like frontline support, are inherently interrupt-driven and batch poorly; for those, batch the work you can control around the work you cannot.
Frequently Asked Questions
How many batches should a day have?
Fewer than you think. Aim for three to five blocks covering deep work, communication, and admin. Too many narrow batches recreates the switching problem you set out to solve.
What if a task does not fit any batch?
Keep a single "miscellaneous" block for genuine one-offs. If items keep landing there, that is a signal a new recurring batch is forming, and you should name it.
Does batching work for meetings?
Yes, and it is underused. Clustering meetings into two or three days, or into the back half of each day, protects whole mornings for uninterrupted work instead of leaving your calendar perforated with isolated thirty-minute holes.
I work in a reactive job. Can I still batch?
Partly. You cannot batch the interruptions themselves, but you can batch your proactive work: handle all your follow-ups, reporting, and planning in dedicated windows so they do not bleed into the reactive chaos.
