How to Batch Your Work

A typical knowledge-work day involves dozens of context switches. You start on a proposal, then reply to a Slack message, then join a call, then try to return to the proposal, then check email, then remember a task you promised someone. By the end of the day you have been busy for eight hours and genuinely done maybe ninety minutes of real work.

The cost is not just time. Every switch between different kinds of thinking carries a reorientation tax. Your brain needs a few minutes to fully load the context of the new task. Do that enough times and the whole day becomes transition rather than traction.

Task batching is the habit that addresses this directly.

What batching actually means

The idea is straightforward: group similar types of work together and do them in a single block. Instead of replying to emails as they arrive throughout the day, you batch all email replies into one or two windows. Instead of scheduling calls whenever requested, you have two or three days where calls happen and the rest where they do not.

Similar tasks use similar mental modes. Writing uses a different part of your thinking than reviewing, which is different again from admin or relationship maintenance. When you switch between these modes constantly, you never get deep into any of them. When you batch them, you build momentum within each mode.

Common batches worth creating

Email and messages are the obvious starting point. Two windows a day, one in mid-morning and one late afternoon, is enough for most people. The world almost never needs an answer within the hour, and the assumption that it does is mostly habit rather than reality.

Calls and meetings batch well together because they require the same social, verbal mode of thinking. Some people dedicate Tuesday and Thursday to calls and protect Monday, Wednesday and Friday for focused work. Others do mornings for deep work and afternoons for anything that involves other people.

Admin tasks such as invoicing, scheduling, filing and replying to low-priority requests take up odd fifteen-minute slots throughout the week. Batched into one or two hours on a fixed day, the same volume of work takes less time and leaves the rest of the week cleaner.

How to build this into weekly planning

The weekly reset is where batching goes from aspiration to structure. When you review your calendar at the start of the week, you are looking not just at what you have committed to but at where different types of work land.

Are your calls scattered across every day? Could you move three of them to Tuesday afternoon? Is your creative or strategic work happening in the morning, when focus is sharpest, or getting pushed to whatever time is left after everything else? These are questions worth asking before the week starts, not on Friday when it is too late.

The weekly blueprint that comes out of a good reset should include some version of batching as a structural choice, not just a list of tasks. Which days are deep-work days. Which afternoons are for calls. When email gets checked.

Start with one batch

You do not need to redesign your whole schedule at once. Pick the one thing that fragments your day the most, usually email or meetings, and batch just that to start. After a week or two you will notice the difference in how much consecutive focus time you have. Then you can add another batch.

Most people who try this find that two weeks in, they cannot imagine going back to the reactive way. The day feels different when it has structure rather than just urgency.

Related: How to time block your week · How to protect your focus time · How to deal with distractions