You already know that multitasking reduces performance. What you may not have considered is that you do not need to multitask to pay that cost. Switching between different types of work throughout the day, even if you do so sequentially, produces a similar form of depletion: the brain does not fully release the previous context before entering the next one.

Task batching is the practical answer to this problem. The idea is simple: tasks of the same type go together, in dedicated blocks, rather than scattered throughout the week.

The hidden cost of switching task types

The cost of switching tasks has two components. The first is direct transition time: the minutes it takes to close what you were doing, orient yourself to the new task, and rebuild the context. The second, and more important, is residual attention cost: even after starting the new task, part of the mind continues processing the previous one.

Imagine a typical morning: at nine you reply to emails, at ten you try to write a report, at eleven you have a call, at half past eleven you return to the report, at noon you review a colleague’s document, at half past twelve you try to pick up the writing again. Every switch has a price, and those prices accumulate.

What batching does is not eliminate task switches but group the transitions. Instead of five or six context changes before lunch, you have one or two. The saving is not trivial: cognitive psychology research estimates that full recovery of attention after an interruption can exceed twenty minutes.

What batching is and how it works

Batching means identifying the categories of work you perform regularly and assigning them dedicated time blocks, rather than responding to each task as it appears.

The difference from conventional time blocking lies in the grouping criterion. Time blocking assigns specific tasks to calendar slots. Batching first groups by cognitive type and then schedules the block.

What does “same cognitive type” mean? Tasks that use the same mental capacities and require similar modes of attention. Replying to emails and managing Slack messages are the same type (reactive written communication). Drafting an article and preparing a presentation are the same type (content creation). Reviewing invoices, filling in forms, and managing subscriptions are the same type (administrative work).

In practice, the flow is: first collect everything you need to do in each category, then process it all in a single dedicated block, then close that category until the next scheduled block.

Which types of tasks benefit most

Not all tasks respond equally well to batching. Those that benefit most are tasks with a high start-up cost that do not require an immediate response.

Written communication: email, Slack, messages, document comments. Instead of responding every time a notification arrives, process everything in blocks of 30 to 45 minutes two or three times per day. The latency cost for most professional messages is minimal.

Content creation: writing, design, preparing presentations, analysis that requires sustained thinking. These are the most valuable blocks and the ones most damaged by interruptions. They usually work best during hours of highest cognitive energy.

Administrative tasks: invoicing, filing documents, updating records, bureaucratic tasks. These are necessary but mechanical. Grouping them into a weekly or fortnightly block prevents them from interrupting higher-value work.

Calls and meetings: whenever possible, grouping meetings into a couple of days per week frees up long stretches on the remaining days for deeper concentration work.

Tasks that do not benefit from batching are those that genuinely require an immediate response: emergencies, urgent matters with third-party dependencies, or anything where delay has real consequences. For these, batching does not apply, but they are usually the minority in any workflow.

How to design your week with batching

The first step is to map your work by category. Spend ten minutes listing everything you do regularly and group it by type. Most people identify between four and six distinct categories.

The second step is to assign each category to a time in the week according to its cognitive demand and your own energy pattern. Tasks requiring the most concentration and creativity go to peak performance moments (for many people, early morning). Communication tasks and administrative work can be done during medium or low energy periods.

An example of a basic weekly structure:

  • Monday and Wednesday mornings: creative or analytical work (notifications off).
  • Tuesday and Thursday: meetings and calls grouped in the morning, administrative work in the afternoon.
  • Friday: weekly review, outstanding emails, planning for the following week.

For email processing: two blocks per day of 30 to 45 minutes. One mid-morning, one at close of day. No checking email when you open your computer in the morning and no checking before sleep.

The third step is protecting the blocks. A creative work block that accepts interruptions is not a block: it is fragmented time with a different label. Protection requires disabling notifications, communicating your availability to the team, and if necessary visibly blocking the calendar.

The most common mistakes when starting out

Blocks that are too long. Three hours of email in a row is exhausting and unnecessary. Communication blocks rarely need more than 45 minutes. Creative blocks tend to perform better in sessions of 90 to 120 minutes with a break in the middle.

Mixing incompatible categories. “Pending work” is not a batching category: it is a label for heterogeneous tasks that will keep producing context switches. The grouping must be by cognitive type, not by urgency or project.

Having no capture system for what comes up. If an urgent email arrives during a creative block and you have nowhere to note it, the anxiety of leaving it unaddressed interrupts you anyway. A simple capture system (a note, a single inbox) resolves this without breaking the block.

Excessive rigidity. Batching is a structure that serves the work, not the other way around. If an urgent meeting falls during a creative block, move the block. Flexibility is part of the design, not a failure of the system.

Batching is not a sophisticated technique. It is the application of a simple idea: doing the same type together produces less depletion than scattering it. Implemented consistently over two or three weeks, most people reclaim between one and two hours of genuine attention per day.