Riding Out a Reaction Without Breaking Your Batch

What each one is actually for

90-Second Rule

The interruption that ends a batch most often comes from inside you rather than through the door: a flare of irritation at the fourth invoice, a spike of anxiety about something in the email you just processed, and all at once a completely different kind of task looks appealing. The 90-Second Rule, drawn from neuroanatomist Jill Bolte Taylor's account of her own stroke recovery, puts a measurable length on that flare. Any single emotional surge is first and foremost a chemical event: your body releases a burst of hormones with a natural lifespan of roughly ninety seconds before it clears from your bloodstream on its own, provided nothing renews it. The practice is to notice the physical sensation the moment it starts — heat in the face, a tight chest, a racing pulse — and simply let that specific wave run its course without adding new thoughts that would trigger a second wave. If you are still furious after five minutes, the rule's claim is that you are now reacting to your own thinking about the event, not to the original chemical surge, which has already passed. The part worth testing for yourself is what happens to the appeal of that other task once the ninety seconds are up: quite often the urge to switch was the wave wearing the costume of a decision, and it leaves when the wave does.

Task Batching

Task batching means grouping every task of the same type — all your emails, all your phone calls, all your invoice entries — into one dedicated stretch of time instead of doing one of each as it occurs to you throughout the day. Picture blocking 9:00 to 9:30 for nothing but email, rather than checking it in the gaps between six other kinds of work. The practice only works if you protect the block: no slipping in a different kind of task because it feels quicker, since that is exactly the interruption the method exists to prevent, and each unprotected slip costs you the settling-in time you just paid to enter the batch in the first place. Most people who try it discover the real difficulty is not remembering to batch, it is resisting the pull of a different, easier-looking task the moment the current one gets hard.

What you get out of pairing them

What you get from putting these together is a batch that survives contact with something upsetting. Without the 90-Second Rule, a single hostile message during your email block does not just cost you the time to reply — it costs you the rest of the block, because you are now carrying residual anger into every message that follows, reading neutral requests as more hostile than they are. With it, the wave passes, you finish the batch you started, and the reply you eventually send — inside the same block or in a later one — is the one you would have written on a calm day, not the one written mid-surge.

What 90-Second Rule rests on

• Interoceptive attention randomised trials
  Directing sustained attention to internal bodily sensations increases awareness of the body's state and changes how that state is experienced.
• Acceptance reduces struggle randomised trials
  Allowing an internal experience to be present without resisting or acting on it reduces the psychological struggle that resistance would otherwise intensify.
• Physiological arousal self resolves if unfed plausible mechanism
  An emotional chemical surge has a limited biological duration and will subside on its own if not renewed by continued thought.

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 treat a state — an emotional surge, a particular kind of attention — as something with a shape and a duration, not as a permanent condition you are stuck managing forever. The 90-Second Rule trusts that the chemical wave of anger has an end if you stop restarting it. Task batching trusts that the mental state suited to email is different from the state suited to deep writing, and that state costs something real to rebuild every time you re-enter it. Neither method asks you to suppress or eliminate the state. Both simply refuse to interrupt it with something incompatible before it is done.

The principle underneath both

A process with a natural arc — a hormonal surge working its way out of the bloodstream, a mental mode settling into a particular kind of attention — gets more expensive every time something incompatible is layered on top of it before it finishes. Left alone to run its course, both resolve on their own terms, faster and more cheaply than if they are constantly restarted by a new trigger or a different kind of task.

What that makes the real goal

If the cost comes specifically from restarting an unfinished process, then the goal in both cases is the same: protect whatever is currently running — a wave of arousal, a stretch of same-type work — from being interrupted by something that would force it to start over. Framed that way, this stops being about anger management or scheduling specifically. It is about recognizing when you are mid-process and refusing to let something else cut in line.

Other practices that serve the same goal

Several better-studied practices are built around this exact same refusal to interrupt a process mid-arc. Urge surfing, developed for addiction relapse prevention, has someone notice a craving and mentally 'surf' it — observing the physical sensation rise, peak, and fall — rather than acting on it or fighting it, on the same premise that an unfed urge has a limited lifespan; it has real trial support in substance-use treatment. Deep work practices, popularized in productivity writing, protect long uninterrupted blocks specifically to avoid the same attention-residue cost that task batching is built around. And the STOP skill taught in dialectical behavior therapy (DBT) — stop, take a step back, observe, then proceed — inserts the same kind of pause before acting that the 90-Second Rule asks for, aimed at any strong urge rather than anger specifically.

A tradition that already does this

Neither of these is a new idea dressed up. Urge surfing already applies the ninety-seconds logic to cravings instead of anger, and predates this framing of it by decades. Task batching, for its part, is a personal-time borrowing of batch processing — the much older manufacturing and computing principle that grouping identical operations together avoids paying a setup cost every time you switch to a different one. Both practices are downstream of the same two older insights; this page is just naming the moment they collide.

Use the ninety-second wait to protect the block

When something in your batch triggers a real reaction — an email that reads as an attack, a request that feels unfair — do not respond and do not leave the block. Notice where the reaction shows up in your body, jaw, chest, or stomach, name it silently as 'this is the wave, not the message,' and keep your hands off the keyboard for a slow count that takes roughly ninety seconds. Then go back to processing the rest of the batch in order. You can return to the triggering message at the end of the block, once the physiological surge has genuinely passed, and you will very often find the reply you would have sent in the first ninety seconds is not the one you send now. The batch survives because you did not let one item pull you out of 'processing' mode and into 'reacting' mode, which is its own kind of task-switch with its own cost.

Batch the messages likely to trigger you

If you already know that certain categories of message reliably spike a reaction — a particular client, a family thread, performance feedback — do not process them interleaved with neutral requests throughout the day. Put them in their own dedicated slot, later in the day or after something that already puts you in a settled state, rather than letting them ambush you between two calm tasks. This does for your emotional baseline what batching already does for attention: instead of resetting your nervous system's baseline every time a loaded message appears at a random point in the day, you contain that resetting to one predictable window, and the rest of your day gets to run without carrying residue from a surge you did not see coming.

9:14am, inbox batch, message six of twenty

You are twelve minutes into your batched email block, moving through requests at a decent pace, when message six is from a colleague who copied your manager on a complaint about something you did correctly. Your face gets hot before you have finished the second sentence. The old move was to fire back a defensive reply right there, which would have taken you out of processing mode for ten minutes of drafting and redrafting, and probably escalated things. Instead you close the message without responding, put your hands flat on the desk, and count slowly to ninety while the specific physical sensation — the heat, the tight jaw — does what it is going to do regardless of what you think about it. At ninety seconds it has visibly eased. You open the message again, note there is actually a real handoff detail buried in the complaint that is worth addressing, flag it to answer at the end of the batch rather than now, and move to message seven. The batch finishes on schedule.

When this is worth reaching for

Skip this if your batches are entirely low-stakes — filing, data entry — where nothing emotionally loaded is likely to show up; adding a ninety-second ritual to a block that was never going to be disrupted is just extra ceremony around it. Reach for it when the batch itself carries risk — inbox processing, reviewing feedback, going through comments on something you made — and especially once you can already name which recurring batch, on which day, tends to be the one where a single message derails the rest of your morning.

Where this does not apply

If the reaction you are having is not a short chemical surge but a sustained, accurate signal that something is genuinely wrong — a pattern of disrespect, a real safety issue, a decision that actually needs to be reversed — waiting ninety seconds and returning to the batch is the wrong move, because it treats a real problem as noise to be waited out. And if your task-switching problem is not about batching type of work but about genuinely not having enough time in the day, no amount of protecting the block will fix a schedule that has more committed hours than actual hours. Neither practice is a substitute for addressing the underlying cause once you have correctly identified which kind of problem you actually have — the wait and the block both buy you time to think clearly, not an answer in themselves.

What the evidence does and does not support

The individual mechanisms carry decent, if uneven, support: directing attention to bodily sensation, the practice underneath the 90-Second Rule, and letting an internal state be present without acting on it are both supported by controlled research in different traditions, though the specific ninety-second timeframe is closer to a popularized rule of thumb from one person's account than a number established across studies. That switching between dissimilar tasks carries a measurable cost is well-supported experimentally; that grouping similar tasks together produces deeper engagement is more observational and anecdotal. Nobody has run a study on using one to protect the other mid-block — this is a reasoned application of two separately-evidenced ideas, not a tested technique in its own right. Treat the pairing as a plausible tactic worth trying for a week or two and judging on your own results, not as something with its own research trail behind it.