Task Batching and the 25/5 Rule: Choosing and Doing, Together

What each one is actually for

Task Batching

Task batching means grouping same-type tasks into one dedicated block instead of scattering them through the day: all your invoicing in one twenty-minute stretch, all your phone calls back to back, all your writing in one sitting, rather than doing one of each every hour. The reasoning is that every time you switch from one kind of task to a different kind, your attention doesn't fully leave the first task — some of it lags behind for a period after you've already moved on, quietly dragging down how well you do the second task — and batching simply arranges your day so you pay that cost far fewer times.

25/5 Rule

The 25/5 Rule is a forced-choice exercise: write out twenty-five things you want to accomplish, then circle only the top five. The instruction that makes it work isn't 'do the top five first' — it's actively avoid the other twenty at all costs until the top five are done, treating them as things you have deliberately decided not to do right now rather than a backlog waiting for spare time. The point is that having twenty additional 'someday' goals sitting visible and unresolved quietly competes for attention even while you're supposedly working on the top five, and the rule removes that competition by treating the other twenty as closed, not merely deprioritized.

What you get out of pairing them

Used alone, each practice solves only half the actual problem of a scattered day. Batching makes you efficient inside whatever block of time you're in, but it has nothing to say about whether that block is even pointed at something that matters — you can batch your way through a day of twenty low-value tasks with excellent technique and finish exactly where you started. The 25/5 Rule tells you which five goals deserve your time, but says nothing about how you actually spend a given afternoon working on one of them — you can have a razor-sharp five-goal list and still burn half your energy on the hidden cost of switching between three different sub-tasks of goal number two every twenty minutes. Together, the 25/5 Rule answers is this worth doing at all right now, and batching answers now that I've decided it's worth doing, how do I not waste the time I've committed to it. Either question asked without the other leaves real time on the table.

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.

What 25/5 Rule rests on

• Constraint increases follow through observational studies
  Fixing the set of allowed choices in advance, before the moment of decision, produces more consistent follow-through than deciding in the moment.
• Cognitive load limits effective goal count observational studies
  Pursuing too many goals at once dilutes attention and reduces the odds of succeeding at any single one.
• Prioritization by elimination focuses effort practitioner report
  Actively identifying and avoiding lower-priority items rather than merely ranking them protects attention and resources for the top few.

Where they actually meet

Both practices work by removing a decision from the moment you'd otherwise have to make it. The 25/5 Rule removes the daily decision of which of my many goals should I work on right now by settling it in advance, once, on paper. Task batching removes the constant micro-decision of what should I switch to next by settling the day's shape in advance too — this block is for calls, this one is for writing — so you're not negotiating with yourself task by task. Neither is really about willpower in the moment; both are about pre-deciding so there's nothing left to negotiate once you're actually working.

The principle underneath both

Deciding something in advance, before the moment where a weaker version of you would have to decide it under pressure or fatigue, produces more consistent follow-through than deciding case by case. This shows up twice here at two different altitudes: the 25/5 Rule pre-decides which goals are even in play, and task batching pre-decides which kind of task a given hour is for. Skip the first and you're constantly renegotiating your priorities; skip the second and you're constantly renegotiating your focus, even once your priorities are settled.

What that makes the real goal

If pre-deciding is what's doing the work, the actual goal is to arrive at the start of any given hour with both questions already answered — what's worth working on, and what kind of work this specific block is for — so the only decision left in the moment is execution itself, not selection. A day built this way spends its decision-making budget once, in advance, rather than dozens of times over, tired, under a deadline.

Other practices that serve the same goal

Several other approaches attack this same two-layer problem, some with harder evidence than either practice here has for itself. Calendar time-blocking, scheduling specific hours for specific work in advance, does the batching half more rigidly by attaching it to the clock rather than to a loose intention. The Ivy Lee Method, a 1918 productivity technique that asks you to write exactly six priorities for tomorrow, in order, before you leave work today, does the elimination half in an even more constrained form than the 25/5 Rule's five. Kanban boards used in software teams enforce a hard limit on how many tasks can be 'in progress' at once, a mechanical version of the same avoid-the-rest instruction. None of these has been tested specifically as a combination the way this page is describing it, but each one is aimed at the identical target: fewer live options, decided ahead of time.

A tradition that already does this

The Ivy Lee Method predates both of these by roughly a century and is worth naming directly, because it already combines the two halves in one simple instruction: at the end of each workday, write down the six most important things to accomplish tomorrow in order of true importance, then work on only the first one until it's complete before moving to the second. That's a five-goal-style elimination, six rather than five, fused directly to a one-thing-at-a-time execution rule, which is essentially what pairing the 25/5 Rule with task batching is trying to recreate with two separate named techniques instead of one.

Batch the work that serves each of your five, not the five goals themselves

Once your top five are circled, the natural mistake is to still bounce between all five goals across the day — an hour on goal one, then goal two, then back to one — which recreates the switching cost the 25/5 Rule was never designed to solve. Instead, look at the actual tasks each goal generates this week and group by task type across goals, not by goal itself: if goals one and three both require phone calls this week, batch those calls together in one block regardless of which goal they serve; if goals two and four both need focused writing, batch that writing together. The 25/5 Rule tells you these five goals and only these five deserve time; batching then tells you the smartest order to actually spend that time inside the week you've got.

Force the elimination before you decide what to batch

The failure mode of task batching alone is building a beautifully organized day around the wrong things — a clean block of batched email, batched calls, batched admin, none of which touches what actually matters this month, because nobody made you choose. Before you plan tomorrow's batches, run the harder version of the 25/5 move on the task list itself, not just your big goals: write down everything currently competing for a batch slot this week, circle the handful that actually connect to a real priority, and consciously mark the rest as not this week. A perfectly efficient batch of unimportant work is still unimportant work done efficiently.

Monday, 9am, looking at a list of forty-one open items

You open your task list and it's forty-one lines long, and your instinct, the one that's cost you entire weeks before, is to start sorting them into tidy batches: all the emails together, all the calls together, all the small admin together, so at least you'll move through them efficiently. Instead you stop and do the harder thing first. You write out the actual five outcomes you're trying to produce this month — not forty-one tasks, five outcomes — and you circle them. Looking back at your forty-one lines, maybe nine of them connect to those five circled outcomes. You cross out the other thirty-two, not as later, but as decided-against for this week. Then, and only then, you batch: the calls that serve those nine into one block at 10am, the writing into a protected two hours after lunch. You get through fewer total tasks today than you would have batching all forty-one. You get through more of what was actually going to matter a month from now.

When this is worth reaching for

Your batching is already good — the day is organized, the blocks run on schedule, nothing about your execution is the problem — and your actual priorities still aren't moving, which is efficiency without progress: a well-run day that isn't advancing what actually matters. Or ask yourself right now, without checking a list, what your top five goals are; if you can't answer cleanly, the elimination step has quietly lapsed even while the batching habit itself stayed intact.

Where this does not apply

If your actual problem is that you don't have five identifiable goals yet — you're in an exploratory season, testing several directions before committing — forcing a hard five-and-avoid-the-rest cut can foreclose options you genuinely need to keep open a while longer; batching alone, without the elimination step, is the more honest fit for that season. And if your work is inherently reactive, like most frontline support or on-call roles, where the day's tasks aren't yours to schedule into batches or defer against a five-goal list, neither half of this pairing has much to grab onto; the constraints that make both practices work assume a degree of control over your own schedule that not every job actually has.

What the evidence does and does not support

The cost of switching between different kinds of tasks is reasonably well documented in cognitive-psychology research, including controlled experiments showing slower and less accurate performance right after a switch. The claim that deciding things in advance beats deciding under pressure has decent observational support but is harder to isolate experimentally, since people who plan well ahead often differ from people who don't in other ways too. The 25/5 Rule itself, as a named technique, is mostly known through a single popular anecdote rather than through any study of the technique specifically; nobody has measured whether pairing it with batching outperforms either alone, and given how anecdotal the 25/5 Rule's own evidence base is, that's a genuinely open question rather than a gap in an otherwise well-studied combination.