← Blog

Focus, explained

Does notification batching help you focus? What the evidence says

Notification batching is the simple idea of turning off interrupt-driven pings and checking your messages in a few scheduled clusters instead — on your timetable, not the sender's. It sounds almost too obvious to need research. But the research is what makes the case sharp: a single notification costs far more than the second it takes to glance, and knowing exactly where that cost comes from tells you how to batch well.

By ComunAI · 6 July 2026 · ~6 min read

The ping costs you even if you ignore it

The intuitive defence of leaving notifications on is "I'll just ignore the ones that don't matter." The evidence complicates that. In a controlled study, Cary Stothart and colleagues had people perform a demanding attention task while their phone occasionally received a call or text they were told not to answer. Simply receiving the notification — without picking up the phone — was enough to make performance worse, with more errors on the trials around the alert.¹ Evidence: Moderate The ping doesn't wait for you to act; it pulls a slice of attention the moment it lands.

That fits what we know about switching more broadly. Organisational psychologist Sophie Leroy showed that after your attention moves to something new, part of it stays stuck on the thing you just left — attention residue — and you perform worse until it clears.² Evidence: Strong A notification is a tiny, involuntary switch: it drags residue onto your task whether or not you reply. (We unpack that seam-by-seam cost in Single-Tasking vs. Multitasking.)

And getting back is slower than it feels

Even when you do decide to check, the real expense is on the way back. In a field study of information workers, Shamsi Iqbal and Eric Horvitz tracked what happened after email and messaging interruptions and found a substantial resumption lag — a stretch of reorienting, often spent reopening windows and rebuilding context, before real work resumed.³ Evidence: Moderate Ten interruptions don't cost ten glances; they cost ten glances plus ten reorientations. Batching attacks exactly that multiplier: cluster the checks and you pay the re-entry toll a few times a day instead of a few times an hour.

Interruptions don't just slow you — they cost effort

There's a twist worth being precise about. Gloria Mark and colleagues found that people interrupted mid-task often finished it in less total time — but they paid for that speed: they reported working faster under more stress, higher frustration, and greater effort.⁴ Evidence: Moderate So the fair framing isn't "interruptions always make you slower." It's that a constant interrupt stream taxes you — you compress the work by spending more of yourself on it. Batching is a way to stop paying that tax all day long.

Does batching actually help — or just feel tidy?

The most direct test targets email. Kostadin Kushlev and Elizabeth Dunn had people limit themselves to checking email just three times a day for a week, then compare it to a week of unlimited checking. Restricting checking left people feeling less stressed overall.⁵ Evidence: Moderate It's one focused study on one channel, so hold it lightly — but the direction lines up with everything above: fewer, planned check-ins beat a steady drip of interruptions. What the research does not show is a guaranteed productivity number, and you won't find an invented one here.

How to batch well

The evidence-based bottom line

Notification batching isn't a life hack that promises a tidy percentage. It's a way of aligning your attention with how it actually works. A ping costs you the moment it arrives, the return trip costs more than the glance, and a day of interruptions is paid for in stress and effort even when the work still gets done. Batching swaps that all-day drip for a few deliberate check-ins — and hands the rest of the day back to one task at a time. The move is unglamorous but reliable: decide when you'll look, silence the rest, and let the work have your attention in between.