What Constant Notifications Actually Do to Attention
Every notification is small. The cumulative cost to a working mind is not. Here is what actually happens between the buzz and the return to what you were doing.
A phone buzzes on the desk. You don't look at it straight away — you're mid-sentence, mid-thought, mid-something. But some part of your attention has already left the room. It is standing by the door, waiting to see what that was. By the time you finish the sentence, you've written a slightly worse version of it than the one you started.
This is the part of notifications that gets missed in most conversations about them. The damage isn't really the interruption itself. It's the several minutes on either side of it — the anticipation before, and the residue after — that quietly erode the quality of whatever you were doing.
The cost isn't the glance, it's the gap
Gloria Mark's research group at UC Irvine has spent years studying interruptions in real workplaces, and one number from that work has become well known for good reason: after an interruption, it can take around 23 minutes to return to the original task with full depth. Not every interruption costs that much — plenty are trivial and we recover in seconds — but the pattern holds up: the more demanding the task, the longer the runway back into it.
What makes notifications different from other interruptions is that many of them don't require any action at all. A calendar reminder needs a response. A promotional push from a shopping app needs precisely nothing. But your attention doesn't know that until it has already checked. The checking is the cost, not the content.
The notification doesn't have to be important to be disruptive. It only has to arrive.
Anticipation is doing more work than you think
There is a second, quieter mechanism running underneath the obvious one. Once you know notifications can arrive at any moment, some low-level part of your attention starts monitoring for them, even in the silence. This is the anticipation effect, and it's been studied specifically in relation to phone notifications: simply expecting a message — whether or not one comes — measurably taxes working attention.
This explains something that pure interruption-counting can't: why turning a phone face-down but leaving it on the desk still seems to cost something, even during a long stretch when nothing actually buzzes. The mind isn't just responding to notifications. It's holding a small amount of processing capacity in reserve, permanently on standby, for something that might happen.
- Anticipation — attention partly reserved for what might arrive
- Signal — the buzz, banner, or badge
- Interruption — attention leaves the current task
- Resolution — check, respond, or dismiss
- Residue — a slower, partial return to the original task
- Reset — anticipation resumes almost immediately
Phantom checking and the habit that outlives the trigger
Most people who work on a laptop with a phone nearby will recognise phantom checking: picking the phone up, unlocking it, finding nothing there, and putting it down again, all without quite deciding to. This isn't really about notifications at all by that point — it's a learned motor habit, built up over thousands of repetitions of check-reward, that now fires on its own, independent of whether anything is actually waiting. The notification trained the habit; the habit no longer needs the notification.
What this does not mean
It would be easy to conclude that notifications are simply bad and should be eliminated. That's neither realistic nor, for most people, desirable — some notifications genuinely matter, and knowing that a courier has arrived or a child's school has messaged is worth a small attentional tax. The goal isn't zero interruption. It's matching the interruption to the actual urgency, which for most apps on most phones has never been properly set up in the first place. Almost every app defaults to "everything is important," because that serves the app, not you.
In real life
Consider two people working on the same kind of report. One has every app pushing notifications by default — email, three social platforms, a shopping app, a news app, a game they downloaded once. The other has turned off everything except messages from a small named list of people. Neither is more or less "distractible" by temperament. But one of them is spending a large amount of attention every day on things that were never worth interrupting for, and one isn't.
What to notice
Over the next few days, notice the gap between a notification arriving and you actually needing to act on it. Most of the time that gap is hours, not seconds. Noticing this repeatedly is what makes the audit above feel worth doing — it stops being a vague discipline and starts being an obvious correction to something that was never designed with your attention in mind in the first place.
A thought to keep
Nothing about a notification is neutral by accident. Someone decided it should interrupt you immediately rather than wait. You're allowed to decide differently.
Worth passing on?
Send this to someone who might want it too.
