Task Batching: Stop Letting Small Jobs Eat the Whole Week
Seven tasks, none longer than four minutes. The day is gone and not one of them is done.
Book the appointment. Send the photo. Cancel the subscription. Return the parcel. Reply to the message from Tuesday. Find the receipt. Ring the garage.
Seven tasks. Not one of them takes longer than four minutes. It is now Thursday and none of them are done.
Small tasks are not expensive because of how long they take. They are expensive because each one needs its own start - its own decision, its own app, its own gathering of the bits you need - and starting is the part that costs. Task batching works because it buys a single start for eight jobs instead of eight starts for eight jobs.
Why the small ones are the hardest
It looks backwards until you count the right thing.
For a four-minute task, the work is a rounding error and the activation cost is the whole price: deciding to do it, remembering what it involves, finding the number, opening the thing, working out where you left off. That overhead is roughly the same whether the task takes four minutes or forty.
They are also individually postponable in a way real work is not. Nothing bad happens today if you do not cancel that subscription, so it survives another day, and another, until eleven of them are running quietly in the background as a low hum of things not done - which is its own kind of tiredness.
And each one drags you into a different context. Phone, browser, password, wallet, shoes. Switching between contexts costs attention every time, and a day of seven small tasks is really a day of seven setups.
Batch by mode, not by topic
The instinct is to group by subject - all the house things, all the money things. That is the wrong axis.
Group by what the task needs from you, because that is the setup you only want to do once:
- Voice: anything that means talking to a human. Bookings, the garage, the clinic, the bank.
- Screen admin: forms, cancellations, invoices, uploads, anything with a login.
- Out of the house: returns, the post office, the pharmacy, the thing that has to be handed to someone.
- Household: the ten-minute physical jobs that need hands and no decisions.
A phone call and an online form are the same topic and completely different tasks. A call to the garage and a call to the dentist are different topics and the same task - same voice, same nerve, same warm-up.
Build the list all week, do it in one sitting
The batch only works if the list is already written when the slot arrives, so capture as things occur to you and put each one on the right mode list instead of doing it immediately.
That is the useful half of a capture habit: the thought "I must cancel that" at nine at night becomes a line under screen admin rather than either a 3 a.m. worry or a badly-timed attempt.
Write each one as a first physical action - "ring garage, number in contacts" rather than "car" - because at batch time you want to be executing, not deciding.
Give each mode a slot
A batch without a time is just a longer list. Put the four modes into the week where they actually fit and keep them in the same place, so they become the answer to "when will this happen" for everything small.
For most people that is something like: one admin hour a week, one calls block during working hours, one errand loop at the weekend, one short household sweep. Fold the choosing into your weekly planning, and hold the slots as blocks in the calendar rather than intentions.
Spend five minutes setting up
The difference between an hour of work and an hour of hunting is the five minutes before.
Get everything in front of you first: the list, the tabs open, the documents, the card, the reference numbers, the phone charged. For an errand loop, that means the parcel, the returns label and the bag by the door the night before - the doorway system makes this nearly automatic.
Then work down the list without re-deciding the order.
Put the phone calls first
If your batch includes calls, do them first, while the warm-up you paid for is still hot and before the afternoon closes the offices.
Calls are the highest-friction item for a lot of people, and doing three in a row is far easier than doing three across three days, because the first one does the hard part - getting past the resistance to speaking to a stranger - and the second and third arrive with it already paid.
Give the batch an end, not a goal
Set a timer and stop when it goes. Sixty minutes of admin, not "admin until it is finished", because "until finished" is an open-ended promise and open-ended promises do not get started.
Whatever is left goes back on the list for next week, which is what timeboxing is for and is not a failure - you were never going to clear it all, and eight things done is eight things done.
Make it survivable
Batches are boring by design. That is the trade: you concentrated all the tedium into one place so the rest of the week is clean, and now you have an hour of pure tedium to get through.
So bring something. Music or a podcast that does not compete for words, a coffee that only happens during this, or another person on a call doing their own list - body doubling is unusually effective for batches, because the tasks are simple enough that company does not disrupt them.
What not to batch
Deep work, obviously. But also:
Anything with a deadline before the slot - if it is urgent, it does not go in the batch, it goes in today. Batching becomes a way of hiding things if you let something wait three weeks for its group.
And the emotionally heavy one. The difficult call, the letter about money, the message to the person you have been avoiding: those deserve their own moment with their own preparation, and burying one in the middle of a list of small jobs usually means it quietly does not get done while everything around it does.
The short version
Small tasks cost activation, not time, so stop paying eight starts for eight jobs. Group by what the task needs from you - voice, screen admin, out of the house, household - rather than by subject. Capture into those lists all week, give each mode a fixed slot, and spend five minutes gathering everything before you begin. Do the calls first, timebox the block and let the rest roll to next week. Bring music or another person, and keep urgent and emotionally heavy things out of the batch entirely.
Keep reading
Frequently asked questions
What is task batching?
Grouping several small tasks that need the same thing from you and doing them in one sitting, so you pay one start instead of eight. It works because a four-minute task costs almost nothing in work and almost everything in activation - deciding, remembering, finding the number, opening the app. Batch by mode rather than by topic: voice, screen admin, out of the house, household.
How do I stop small tasks piling up?
Capture them the moment they occur to you, on to the list for the mode they belong to, instead of trying to do them immediately or trusting memory. Write each as a first physical action - "ring garage, number in contacts" rather than "car". Then give each mode a fixed weekly slot: an admin hour, a calls block, an errand loop, a short household sweep. The list is what makes the slot work.
How long should a batch be?
Give it an end rather than a goal: set a timer for forty-five or sixty minutes and stop when it goes, instead of working "until it is finished". Open-ended promises do not get started. Whatever is left rolls to next week, which is not failure - you were never going to clear it all, and eight things done is eight things done.
What should not go in a batch?
Anything urgent - if it has a deadline before the slot, it goes in today, because batching can quietly become a way of hiding things for three weeks. Deep work, which needs a long uninterrupted run rather than a list. And the emotionally heavy item: the difficult call, the letter about money, the message you have been avoiding. Buried in a list of small jobs, that one reliably does not get done.
