Manufacturers discovered long ago that switching between different products on an assembly line creates “changeover time” — the downtime required to reconfigure equipment between runs. The solution was batch processing: running a full batch of one product before switching to the next.
The same principle applies to knowledge work. Every time you switch between types of tasks, you pay a mental changeover cost. Batching similar tasks eliminates most of this overhead and creates more focused, efficient work sessions.
When you respond to an email, then write a paragraph, then check Slack, then make a phone call, then return to writing — each switch costs you. The brain doesn’t instantly transition between different modes of thinking.
Writing requires a creative, expansive state of mind. Email processing requires a different orientation: reading, evaluating, and composing brief responses. Phone calls require verbal fluency and active listening. Each of these requires a different cognitive configuration, and switching between them repeatedly is genuinely inefficient.
Research consistently shows that this scattered approach produces worse output and takes longer than batched alternatives.
Tasks can be batched by type, tool, context, or mental mode. Common batching categories:
Communication batches: Email, Slack, text messages, social media replies. These are all consumption-and-response tasks that use similar cognitive resources.
Administrative batches: Scheduling, invoicing, filing, data entry. Routine, detail-oriented tasks that don’t require creative thinking.
Creative batches: Writing, designing, brainstorming, problem-solving. Generative tasks that benefit from a sustained expanded mental state.
Decision batches: Review and approve, evaluate options, make calls. Evaluative tasks that require judgment but not deep creation.
Learning batches: Reading, courses, research. Information consumption that benefits from an open, receptive mental state.
The biggest productivity gain for most knowledge workers is processing email in defined batches rather than responding in real time throughout the day.
Pick two windows — perhaps 9am and 3pm — and process all email during those windows only. Between those windows, email is closed. This alone can reclaim 1-2 hours of focused work time per day.
Create a 30-60 minute daily administrative block for all the small operational tasks: scheduling, tracking, filing, quick replies, expense reports. Do them all at once. This prevents administrative overhead from leaking into your deep work sessions throughout the day.
Batch recurring decisions into a weekly review and planning session rather than making them ad hoc throughout the week. This includes: what to work on next week, which requests to accept or decline, what to order or buy, what meetings to schedule.
If your work involves creating — writing, designing, coding, strategizing — protect a large daily block for this work and don’t let it be interrupted by communication or administrative tasks. This is your deep work block.
Batching also means closing tools that aren’t relevant to the current batch. If you’re writing, close email and Slack. If you’re in an admin batch, close your writing document. The tools themselves carry contextual cues that trigger associated behaviors.
This is an environmental design principle from habit science: your environment shapes your attention and behavior. Design your environment to support the batch you’re currently running.
If the idea of overhauling your workflow is daunting, start with just email batching. Set two specific windows for email today, and close it outside those windows.
Notice how it feels to have an hour of writing time that isn’t interrupted by an email notification. Notice how your email responses are better when you process them in a focused batch rather than one by one throughout a distracted day.
The principle scales. Once email batching is a habit, extend it to other task types. Gradually, your day becomes a series of focused, high-efficiency batches rather than a constant fragmented juggle.
Combined with time blocking, batch processing creates a complete daily workflow that dramatically reduces the hidden cost of context-switching.