Batch reactive and administrative tasks into designated windows
Cluster email, logistics, and low-stakes decisions into two or three scheduled windows instead of responding continuously.
Key takeaways
- What it is: Cluster email, logistics, and low-stakes decisions into two or three scheduled windows instead of responding continuously.
- Why it works: Context-switching between reactive tasks and deep work carries a measurable attention cost — "attention residue" (Sophie Leroy's research) means that even after switching back, thought continues partially in the previous task. Batching keeps reactive processing in contained windows and protects focused time from constant interruption, reducing the total cognitive overhead of the same quantity of admin work.
- Evidence: Plausible mechanism, limited direct outcome data.
- Avoid: Checking email "just once quickly" outside the batch window, which resets attention residue and undoes the focus the batch window was protecting — the protocol only works if it is maintained.
Why it works
Context-switching between reactive tasks and deep work carries a measurable attention cost — "attention residue" (Sophie Leroy's research) means that even after switching back, thought continues partially in the previous task. Batching keeps reactive processing in contained windows and protects focused time from constant interruption, reducing the total cognitive overhead of the same quantity of admin work.
How to do it
- 1Designate two or three time windows per day for email and reactive messages (e.g., 9 am, 1 pm, 5 pm).
- 2Outside those windows, close the inbox and turn off notifications.
- 3When an incoming task arrives outside the window, add it to a list to process at the next batch window.
What the evidence says
MechanisticAttention residue research shows that partial task completion leaves cognitive activation that degrades subsequent task performance. Email batching is a practitioner application of this finding.
Honest caveat: The attention residue research establishes the cost of task-switching; the specific email batching intervention has not been tested in a dedicated RCT.
- — Leroy (2009), "Why is it so Hard to do my Work?", Organizational Behavior and Human Decision Processes
Common mistake
Checking email "just once quickly" outside the batch window, which resets attention residue and undoes the focus the batch window was protecting — the protocol only works if it is maintained.
IX Coach helps you map your current reactive task volume and design a batching schedule that is realistic for your role and communication norms, not a one-size template.
Practice this with IX Coach →