Treat email as a pull channel, not a push channel

Check email on your schedule — not as a notification arrives, but at two or three designated times.

Why it works

Email is architecturally a push channel (sender decides when it arrives) but functionally most appropriate as a pull channel (recipient decides when to process it). When monitored continuously, email creates a permanent partial attention commitment — the brain keeps a thread ready for "something new might have arrived." Converting it to pull processing closes that thread between checking windows, freeing the full attentional resource for chosen work.

How to do it

1. Choose two or three specific times per day to process email (morning, post-lunch, late afternoon).
2. Close email between checking times — do not leave the application open.
3. At each checking window, process to zero (action, defer, delete) rather than reading and re-closing without deciding.
4. Communicate the checking cadence to frequent collaborators so they have accurate response-time expectations.

Evidence

Experimental work on email checking frequency found that participants who checked email less frequently reported lower daily stress without being perceived as less responsive by colleagues. Batched email processing also reduces total time spent on email compared with continuous monitoring. (rct)

Response-time expectations vary enormously by role and organizational culture; some positions have genuine rapid-response requirements that make scheduled-only checking infeasible.

Sources

• Kushlev & Dunn (2015), checking email less frequently reduces stress, Computers in Human Behavior

Common mistake

Scheduling email windows but leaving the application open in the background, which keeps the push dynamic active and prevents the attentional closure the practice is designed to create.