Batching is usually sold as a scheduling trick: do all your writing on Monday, all your editing on Tuesday, and get more done. It works, but not for the reason people give. The saving is not time; it is the cost of switching between modes of thinking, and once you understand that, most batching advice starts to look wrong.
The failure mode is a batch plan that groups tasks by output — all articles on Monday — while ignoring the fact that drafting an article and outlining one use different parts of your attention. Those should never share a block.
What batching actually saves
Every switch between kinds of work has a warm-up cost. Drafting requires holding an argument in mind; editing requires holding a standard in mind; research requires holding a question in mind. Moving between them means loading a new context, and the cost is not just the minutes — it is that the first ten minutes of any block are worse work than the last ten.
That is the real saving: fewer warm-ups means a higher proportion of your time is spent in the part of each block where you are actually good. It is a quality argument that happens to produce a speed result, which is why batching that only chases throughput tends to disappoint.
The wrong way to batch
The standard advice is to batch by deliverable: write four articles on Monday, edit them on Tuesday, publish on Wednesday. It reads well and it fails, because "writing four articles" is four different kinds of work performed in sequence — deciding, gathering, outlining, drafting — and you spend the day switching between them four times instead of once.
The second wrong way is batching by tool or by calendar slot rather than by mental mode. "Content day" is not a batch; it is a container in which every mode appears. If a block contains more than one mode, it is not a batch block, whatever the calendar says.
Batch by cognitive mode
Four modes are worth separating. Each one needs different inputs and produces different fatigue.
- Deciding. Choosing topics, claims and angles. Needs a list of candidates and a willingness to reject most of them. Short blocks work best.
- Gathering. Collecting examples, notes and specifics. Low intensity, and it benefits from being done in one pass across many pieces so that the searching is done once.
- Drafting. Producing prose. The most demanding mode and the one most damaged by interruption.
- Finishing. Editing, checking facts, formatting, titles, publishing. Higher volume, lower intensity, and best done when you are not at your sharpest.
The natural order for a batch of four pieces is deciding for all four, then gathering for all four, then drafting each one, then finishing each one. Notice that the drafting and finishing stages still loop per piece — that is deliberate, because drafting four pieces in a row at a consistent standard is not realistic.
A realistic week
A shape that survives contact with a normal week looks like this. One short block for decisions, where you commit to the claims for everything you plan to publish. One block for gathering, collecting the material for all of those pieces while your notes are open. Then one drafting block per piece, on separate days if you can, each protected from everything else. Then a single finishing block at the end for editing, titles and publishing.
The asymmetry is intentional: decisions and gathering are batched across the whole set, drafting is not. If you must compress, compress the gathering. If you must expand, expand the drafting.
Keep one slot per week empty. Batches overrun, and a plan with no slack gets abandoned the first time something takes twice as long as expected.
Protecting the deep work block
The drafting block is the one that must be defended, and defending it is mostly about what you refuse. No messages during it, no research, no opening the analytics. Anything that needs a decision gets written on a list and handled in the next block.
Two practical protections work better than willpower. Write the first sentence of the piece before the block starts, so you begin inside the work rather than staring at a blank page. And set an end time rather than an output target, because a target with no ceiling is how a ninety-minute block becomes a five-hour one that ruins the next day.
Using AI inside a batch
AI fits the batching model unusually well, but only in specific positions. It is useful in the deciding block for generating candidate angles you can reject quickly. It is useful in the finishing block for tightening, and for producing alternative titles to choose between.
It is worst in the drafting block, which is exactly where people put it. Handing the drafting to a model while you wait does not save the mode-switch cost; it replaces the highest-value mode with a review mode that has its own cost. If the drafting block is the one you defended, do not fill it with reviewing someone else's sentences.
Where it genuinely helps: use it to shorten a drafting block by producing a structural draft from your gathered notes, then rewrite it yourself. The output is a starting point that removes the blank-page cost without removing the writing.
The quality risk
Batching has one real danger, and it is not burnout — it is uniformity. When four pieces are planned and produced in the same session, they inherit the same assumptions, the same structure and often the same opening move. Readers notice before you do, because they see the output in sequence.
Guard against it at the deciding stage: if all four claims come out in the same shape, replace two of them. And at the finishing stage, read the pieces in the order they will be published, which is the only moment when repeated patterns are obvious.
The second risk is that a bad decision propagates across the whole batch. Batching by mode concentrates decisions, so one wrong choice — a topic that is not actually interesting, an angle nobody cares about — now affects four pieces instead of one. Check the claim after the first draft rather than after the fourth.
When to stop batching
Batching stops paying when the pieces stop being similar in size. If one article is a small explainer and the next is a substantial guide, forcing them into the same schedule means either the small one absorbs a whole expensive block or the large one gets a block it cannot finish.
It also stops paying when the queue disappears. Batching assumes a backlog of several pieces at similar stages; with a single piece in flight it becomes pure overhead, and you are better off working on the one thing. Keep a deliberate buffer of one or two pieces in progress — enough for the modes to separate, small enough that the batch stays reviewable.
The honest summary: batch the thinking, batch the gathering, batch the finishing, and keep the writing blocks single-purpose. The plan that tries to batch everything is the plan that gets abandoned in week two.