Shallow work is the plankton of the modern workday: individually tiny, collectively capable of feeding an entire ecosystem of lost hours. Answering a quick email, approving a small request, updating a spreadsheet cell, renaming a file, confirming a meeting; none of these tasks is hard, none takes long, and that is precisely the trap. Because each one is small, we do them the moment they appear, and the moments they appear are scattered across the whole day. The result is a workday ground into confetti, where no stretch of time is ever fully yours. Batching, the old manufacturing idea of grouping similar work and doing it in dedicated runs, is the most effective counterattack ever devised for this problem, and it translates to knowledge work almost perfectly.

Why Small Tasks Do Outsized Damage

The direct time shallow tasks consume is the smallest part of their cost. The larger cost is fragmentation. Every time you break from substantive work to handle a two-minute chore, you pay a switching toll on both sides: the wind-down as you disengage, and the wind-up as you claw your way back into the original task. A dozen two-minute interruptions do not cost twenty-four minutes; they can hollow out two hours of what would have been focused time. Worse, the interruptions rarely arrive alone: one quick check of the inbox surfaces three new small tasks, each of which feels easiest to handle immediately, and the spiral quietly feeds itself.

There is also a subtler cost: shallow work is seductive. It offers instant completion, a little dopamine tick of doneness, while deep work offers slow, ambiguous progress. Given a free moment, the mind reaches for the easy win, and a day of easy wins can feel busy while accomplishing nothing that mattered. Batching does not just save minutes. It removes the constant availability of the easy win, which quietly reshapes what your day defaults to.

The Core Move: From Continuous to Scheduled

Batching rests on one decision: shallow work happens at scheduled times, not continuously. Instead of processing email as it arrives, you process it in two or three dedicated windows. Instead of doing each administrative chore when you notice it, you write it down and do the whole pile in one admin block. The work still gets done, often faster, because similar tasks share mental context; twelve emails answered in one sitting take far less total effort than twelve answered across twelve interruptions.

The psychological shift is from responder to operator. A responder's day is shaped by whatever arrives; an operator runs scheduled processes. Nothing about the work itself changes, only its timing, and yet the difference in how the day feels is dramatic. Long, unbroken stretches reappear as if by magic, because they were always there, just shredded.

Build Your Batching Windows

Start by inventorying your shallow work for a couple of days. Every time you do something small, jot a word about it. Patterns will emerge, and most people's shallow load sorts into a few families: communication, administration, planning and scheduling, and errands or physical chores. Each family gets a window.

  • Communication: two or three fixed windows daily for email and messages, such as late morning, after lunch, and end of day.
  • Administration: one block, a few times a week, for invoices, expenses, forms, and filing.
  • Scheduling and coordination: folded into a communication window, or a short daily slot for calendar wrangling.
  • Errands and chores: grouped into a single run rather than scattered across the week.

Place windows in low-energy parts of your day, since shallow work is famously undemanding; spending your sharpest morning hour on email is like using a scalpel to open mail. Guard your peak hours for the work that actually needs a brain at full power. It helps to write the windows into your calendar as real events at first; after a few weeks the rhythm becomes automatic and the entries can quietly go.

Capture Instead of Doing

Batching lives or dies on one habit: when a small task appears outside its window, you capture it instead of doing it. Keep a running list, paper or digital, that serves as the intake tray for every stray chore, and develop the reflex of writing rather than acting. The task costs you five seconds now and gets handled properly later, inside its batch.

The classic objection is the two-minute rule, the advice that anything under two minutes should be done immediately. That rule is sound when you are already processing your inbox; inside a batch window, absolutely, knock the tiny things out on the spot. But applied during focus time it becomes a license for constant interruption, because everything claims to be two minutes. The refinement is simple: the two-minute rule applies within batching windows, and the capture rule applies everywhere else. Together they cover every case without sacrificing your focus. When a window opens, review the capture list and work it in order of dread, biggest avoidance first, so the list never becomes its own source of procrastination.

Manage Expectations Around You

The biggest fear about batching is that other people expect instant responses. The fear is usually overblown, but it should be managed rather than ignored. Most correspondents care about reliability far more than speed; a person who always answers within a few hours is easier to work with than one who sometimes replies in seconds and sometimes vanishes for days. Batching, done consistently, actually improves your reputation for responsiveness because it makes you predictable.

Help the transition along with a few explicit signals. Tell close collaborators that you check messages at set times and how to reach you if something is genuinely urgent, such as a phone call. If your role truly demands rapid response in some channel, batch everything else and keep only that one channel live. And give the change a couple of weeks before judging it; most people discover the flood of supposed emergencies never arrives, and the few real ones find them anyway. An auto-reply or a short status line noting your response windows can even do the signaling for you, without a single awkward conversation.

Protect the Batch From Becoming the Day

Batching has a failure mode of its own: the windows expand. Email hour becomes email morning, and the admin block swells to fill whatever it touches, because shallow work is infinitely elastic and always feels vaguely virtuous. The defense is hard edges. Give each window a fixed end time, and when the timer sounds, stop, even with items remaining. Unfinished shallow work rolls to the next window; that is the system operating, not failing.

It helps to define done by time rather than by emptiness. The goal of a communication window is not inbox zero; it is the most important responses handled within the allotted minutes. Some weeks everything clears, other weeks a residue rolls forward, and both are fine. The moment you let a batch run long to reach emptiness, you have handed control of your schedule back to the inflow, which is exactly what batching exists to prevent.

Final Thoughts

Shallow work cannot be eliminated, and it does not need to be. It needs to be contained. Move it from a continuous drizzle into a few scheduled downpours, capture strays instead of chasing them, set expectations with the people around you, and keep hard edges on the windows so the containment holds. What you buy with this modest reorganization is the rarest commodity in modern work: long, unbroken stretches of attention. The small stuff will still get done, probably faster than before. The difference is that it will finally be working for your day instead of eating it.