Using Do It Tomorrow to enhance Task Batching

What each one is actually for

Do It Tomorrow

Do It Tomorrow is built around one specific discipline: once your day's list is set, it's closed for the day, and any new task or request that lands on you gets written onto tomorrow's list instead of today's, however urgent it feels when it arrives. The felt urgency of a new request is the exact thing the system doesn't trust, because almost everything that feels urgent in the moment it lands turns out to have been fine to handle the next day, and if you let every one of them onto today's list, today's list never actually gets finished — it just keeps growing. The list you close today is a promise you can actually keep, because nothing can be added to it after the fact to break that promise.

Task Batching

Task batching starts from a simple observation: switching from one kind of task to a different kind costs you something every single time, even for tasks that individually take thirty seconds. Instead of checking email as it arrives, taking a call whenever it rings, and answering a message the moment it appears — each one interrupting whatever you were doing before it — you set aside one block for all your email, another for all your calls, another for administrative odds and ends, and you handle each category only during its own block. The goal isn't fewer total tasks; it's fewer total switches between different kinds of task, because the switching itself, not the tasks, is where a surprising amount of the day's effort actually goes.

What you get out of pairing them

What Do It Tomorrow buys you is a list you can genuinely finish, which sounds small until you notice how rare it is — most task lists never get to zero because new items keep landing on top of old ones all day, so the feeling of being behind never actually lifts even on a productive day. What task batching buys you is getting more out of the exact same number of tasks, because part of your attention stays tangled up in whatever you just switched away from for a period afterward — researchers call this attention residue — so five two-minute emails answered as five separate interruptions across a day cost you more total focus than the same five answered back to back in one sitting. Put the two together and the reason to bother becomes concrete: a closed list protects the time you'd spend finishing today's work from being fragmented by new arrivals, and batching protects the quality of that same time from being fragmented by switching between different kinds of task — one guards the boundary of the day, the other guards what happens inside it.

What Do It Tomorrow rests on

• Implementation intention closes intention action gap randomised trials
  Pre-committing to a specific situational cue paired with a specific response lets the behavior fire automatically when the cue occurs, without depending on in-the-moment willpower.
• Closed lists reduce overwhelm practitioner report
  A fixed bounded list of tasks rather than an ever-growing open list reduces the felt overwhelm of an infinite to-do list.
• Deferred capture protects commitment practitioner report
  Writing newly arriving tasks onto tomorrow's list rather than acting on them immediately protects today's already-committed plan from being derailed by reactivity.

What Task Batching rests on

• Attention residue degrades subsequent performance observational studies
  Part of a person's attention stays on the task just left behind for a period after switching which impairs performance on the new task.
• Batched focus enables deeper engagement practitioner report
  Protecting an uninterrupted block of time for one kind of work allows a depth of engagement that fragmented attention across many task types does not allow.
• Task switching imposes cognitive cost randomised trials
  Moving attention between dissimilar tasks carries a measurable cognitive cost each time it happens even when each individual task is simple.

Where they actually meet

Both practices are, underneath their different names, the same move applied at a different grain. Do It Tomorrow decides in advance which day a new demand gets handled on, so the decision of "when do I deal with this" never has to be made in the reactive heat of the moment it arrives. Task batching decides in advance which block of today a given kind of demand gets handled in, for exactly the same reason. Once you see the closed list as a batching decision made at the scale of a day — everything new today gets batched into tomorrow — the two stop looking like separate techniques and start looking like the same discipline, deferral of a decision about timing, applied at two different resolutions.

The principle underneath both

Deciding in advance which window of time a category of demand will be handled in, rather than deciding in the moment the demand shows up, keeps that demand from redirecting your attention the instant it arrives. It doesn't matter whether the category is "anything new today" or "anything that's an email" — the mechanism is identical: a pre-made rule about timing removes a hundred small in-the-moment judgment calls, and in-the-moment judgment calls about urgency are exactly where most days quietly come apart.

What that makes the real goal

The objective both are built around is keeping a chunk of committed time — a day's plan, or a single focused block inside it — intact against a stream of incoming demands that will otherwise chip away at it one item at a time, each one individually reasonable to attend to right now, and collectively fatal to ever finishing anything.

Other practices that serve the same goal

Time blocking more generally, assigning specific calendar slots to specific categories of work in advance, pursues the identical objective and has wide practical use in productivity writing, though most of its support is practitioner-reported rather than experimentally controlled. Processing email or messages at two or three fixed checkpoints a day instead of continuously, sometimes called batch-processing your inbox, is a narrower version of task batching aimed at a single channel, with observational workplace research linking constant inbox-checking to measurably higher reported stress. A firm daily cutoff on new commitments — some version of "nothing gets added to today after 9am" — is close to Do It Tomorrow's closed list under a different name, and shows up independently across several time-management traditions that never cited each other, which is itself a sign the underlying move is doing real work rather than being one author's idiosyncratic preference.

A tradition that already does this

Batch production in manufacturing — running one identical operation across an entire set of parts before switching the machine over to the next operation, rather than running each part through every operation individually — solved this same problem for physical work over a century ago, for the same reason: the changeover cost between different operations, paid once per batch instead of once per item, was recognized early as the thing eating the factory's actual throughput. Do It Tomorrow and task batching are that same manufacturing logic, aimed at a single person's attention instead of a machine's tooling.

Using Do It Tomorrow to enhance Task Batching

Task batching's most common failure isn't disagreeing with the idea — almost everyone agrees switching costs are real — it's that a new request lands in the middle of a protected block and feels too urgent to leave for the next batch, so the block gets broken anyway, and after a few broken blocks the whole batching habit quietly stops. The concrete move is to import Do It Tomorrow's closed-list discipline directly into each batch: once a block for calls, or email, or admin work has started, it's closed the same way a day's list is closed, and anything new that shows up gets written down for the next scheduled batch of its type rather than acted on immediately, no matter how it feels in that instant. The skill Do It Tomorrow spends its whole system training — distrusting felt urgency and writing the thing down instead of reacting — is exactly the skill that makes a batch survive contact with the rest of a normal day.

Using Task Batching to enhance Do It Tomorrow

A day working from Do It Tomorrow's closed list still has one weak point: tomorrow's list fills up with whatever arrived in whatever order it arrived, and if you then work it top to bottom, you're doing a call, then an email reply, then some admin paperwork, then another call — switching task type constantly, just a day later than you would have without the system. The concrete move is to batch tomorrow's list before starting on it: before you touch anything, sort the items by type — all the calls together, all the emails together, all the quick admin items together — and work each group in its own block. Do It Tomorrow already did the hard part, protecting these items from being handled reactively the day they arrived; task batching finishes the job by making sure the day you do handle them isn't just yesterday's chaos with a twenty-four hour delay stapled onto it.

Tuesday morning, eleven items on yesterday's overflow list, sorted before the first one gets touched

You closed Monday's list at 9am the way you always do, and by 5pm eleven new things had landed on you anyway — three phone messages, four emails that needed real replies, two expense receipts to log, and two small requests from a colleague. All eleven went onto tomorrow's list instead of derailing Monday, which used to be the end of the discipline for you. Tuesday morning, instead of opening the list and starting from the top, you spend ninety seconds sorting the eleven items into three groups by type before doing anything. You do the three calls back to back first, while your energy for talking is highest, then the four emails in one sitting, then the two receipts and two small requests together as one short admin block. By 10:15 the entire overflow list is gone, and it took noticeably less than the four separate attention resets it would have taken working it in its original, arrival-order shape — the same eleven items, sorted before you started rather than during.

When this is worth reaching for

Small, varied demands arrive constantly and unpredictably — client work, management, support roles, anything with a real inbox and a real phone — because that's exactly the condition where an unprotected day dissolves into pure reaction, and where the overflow list, once deferred, is heterogeneous enough that sorting it by type before working it actually saves something real.

Where this does not apply

If a day's incoming demands are already a single type — a role where genuinely everything that lands is, say, a support ticket of roughly the same shape — there's nothing left to batch by type; Do It Tomorrow's closed list still helps, but layering batching logic on top of an already-uniform list adds a step that does nothing. And for anything that's a genuine emergency rather than merely urgent-feeling, deferring it to tomorrow's list is actively the wrong move; both practices assume most incoming demands only feel urgent, and neither one is a substitute for judgment about the rare case where something really can't wait a day.

What the evidence does and does not support

That pre-committing to a specific cue-and-response plan lets a behavior fire without relying on in-the-moment willpower has strong randomized trial support and is one of the better-replicated findings in behavior-change research generally. That switching between different kinds of task carries a measurable cost, separate from the difficulty of the tasks themselves, also has solid experimental backing from cognitive psychology. Where the evidence thins out is the specific claims each named system makes about itself: that a closed list reduces felt overwhelm, and that a batched block enables deeper engagement than a fragmented one, are both widely reported by practitioners of these exact systems but haven't been isolated and tested as their own controlled variables — the underlying mechanisms they're built on are solid, but the packaged systems themselves are practitioner wisdom, not trial results. Sorting a deferred list by type before working it, the specific combination described on this page, is a direct application of well-supported switching-cost research to a well-supported deferral habit, but nobody has run that exact combined experiment.