Here's an experiment Gloria Mark's team at UC Irvine actually ran: they cut a group of office workers off from email for a week and measured heart-rate variability. Focus went up. Stress markers went down. Task switching dropped by half. Nobody's building burned down.
You can't take the week, but you can take the mechanism. The stress wasn't caused by email existing; it was caused by email arriving continuously into an attention system that pays about 23 minutes of refocus time per interruption. Batching keeps the email and removes the interruptions.
What batching means precisely
Email gets processed in two to four fixed daily windows, and only then. Outside the windows the client is closed and notifications are off. Inside a window you process to zero decisions: answer the quick ones, convert the real work to tasks, log the waiting-fors, archive the rest. A workable default:
| Window | Length | Focus |
|---|---|---|
| 9:00 | 20 min | Overnight arrivals, plan the chase list |
| 13:00 | 20 min | Morning arrivals, quick replies |
| 16:30 | 15 min | Sweep to zero, set up tomorrow |
The specific times matter less than their fixedness. A brain that knows email happens at 1:00 stops monitoring for it at 11:40, and that background monitoring was the expensive part.
The urgency objection, handled
"But what if something urgent comes in?" Two honest answers. First, genuine emergencies don't travel by email; they phone, they message, they appear at your desk. Email is where things go when same-hour response is not actually expected. Second, for roles with real SLAs, create a VIP exception: notifications on for a handful of named senders (your manager, the on-call channel, that one client), batch everything else. The exception covers the risk without surrendering the day.
It also helps to say your rhythm out loud once, in a signature or a team charter: processed at 9, 1, and 4:30, same-day replies, call for urgent. Stated expectations end the guessing that drives people to resend and escalate. More on that in what people actually expect.
Making the windows cheap
Batching fixes when you process; it doesn't shrink what you process. Pair it with the volume layer (filters, unsubscribes) from the full system, and, if you want the windows shorter still, let Pidgy run the sort before you arrive: it reads your Gmail or Outlook inbox continuously and has the needs-you list, the waiting-fors, and the routine drafts ready, so a 20-minute window becomes a 5-minute review.
