Notification Overload

Notification overload is a volume problem: too many alerts arriving as a variable stream, so attention keeps paying a switch tax even when you never open the phone.

Notification overload — a large cartoon phone with a face next to a person at a desk, MUTE BATCH PARK CLOSE rings, mustard line The ping is the switch.

Last updated: 5 September 2026
Reviewed by: The Growth Reads editorial team
Read time: 16 minutes
Sources: 9 peer-reviewed sources
Books referenced: 2
The short answer

Notification overload is a volume problem: too many alerts arriving as a variable stream, so attention keeps paying a switch tax even when you never open the phone. A bare ping can disrupt an attention task about as much as using the device. This page is the pile-up, not screen time and not leftover focus from the last file.

Key takeaways

  • A cell-phone notification that people did not look at or handle still disrupted a sustained-attention task, and the size of that drop was comparable to the costs reported when people actively use a phone (Stothart, Mitchum & Yehnert, 2015).
  • When 221 students spent one week with alerts on and the phone in reach, then one week with alerts off and the phone away, they reported more inattention and restlessness in the alerts-on week — a non-clinical symptom score, not a diagnosis (Kushlev, Proulx & Dunn, 2016).
  • In a two-week field experiment (n=237), delivering notifications in three predictable batches a day improved attention, mood, stress, and sense of control versus the always-on stream; hourly batching did not (Fitz, Kushlev, Jagannathan, Lewis, Paliwal & Ariely, 2019).
  • Fifteen Android users logged a mean of 63.5 notifications a day, mostly from messengers and email, and typically viewed them within minutes even on silent — a small 2014 observational picture of volume, not a personal quota (Pielot, Church & de Oliveira, 2014).
  • The mere presence of your own smartphone on the desk reduces available working memory and fluid intelligence even when the phone is silenced and face down; another room beats a pocket (Ward, Duke, Gneezy & Bos, 2017).

What notification overload actually is

Notification overload is too many alerts arriving as a variable stream, so attention keeps paying a switch tax it did not choose. The unit is the ping — a sound, a badge, a banner, a lock-screen line — not the hour you later spend in the app. Cary Stothart, Ainsley Mitchum and Courtney Yehnert ran the cleanest lab test we have of that unit. Two hundred and twelve undergraduates started a Sustained Attention to Response Task. Analyses used 166 people after exclusions (the most common: the person looked at or handled the phone). A program sent a real-looking call or text from the participant’s own number during the second block. People who never touched the device still made more commission errors than the no-notification group. The authors judged that drop comparable in size to the costs in studies where people actually talk or text. Opening the phone is optional. The tax is not.

That is the ownership of this page. The parent in the focus cluster is how to focus better — the beam: one named output and fewer switches. This child is the incoming stream that keeps nominating a new goal. The rest of the productivity library treats other parents — morning edges, discipline, decisions, habits — but the mechanism here is volume and delivery, not a 5 a.m. identity and not a grit speech. Cal Newport’s A World Without Email is the workplace language for the same pile-up: a hyperactive hive mind that treats every message as a live conversation. The book is not a trial. The delivery schedule is.

How is notification overload different from interruption, attention residue, and screen time?

Notification overload is the incoming volume. An interruption is any break. Attention residue is what the last unfinished task still does after you have already switched. Screen time is minutes on a glowing surface. Those four phrases share a phone and they do not share a page. Collapsing them is how this URL would rewrite neighbours it is not allowed to own.

Phrase What it names What this page does with it
Notification overload Too many alerts, arriving as a variable stream The keyword. Volume and delivery.
Interruption Any break — a person, a ping, a thought A ping is one kind. Not every interruption is a notification.
Attention residue Task A still running after you start Task B A consequence of a switch. Owned by the sister page.
Screen time Minutes on a glowing surface A later count. You can pay the ping tax with the screen off.

Sophie Leroy’s 2009 experiments sit on attention residue: leave Task A unfinished, and thoughts about A keep running so Task B gets a worse version of you. A notification can cause that switch. This page does not rewrite her design or her fix. The live sister is the residue protocol — finish or park with a ready-to-resume next action. This page only needs the incoming stream that keeps creating unfinished switches. How to reduce screen time is the minutes page. Single-tasking is the load rule once the stream is quieter. Do not flatten four URLs into a phone-settings listicle.

Landscape chart comparing always-on notification streams, three predictable batches a day, and silent-off — the delivery schedule is what changes the attention tax.
Same phone. The delivery schedule is the tax. Chart © thegrowthreads.com
Tall illustrated shareable: a person at a desk next to a phone throwing notification bubbles, with the four volume cuts — mute, batch three times, park the chat, move the phone.
Save and share. Diagram © thegrowthreads.com

Why the pile-up happens

The pile-up happens because alerts are designed as a variable reward, because work chat copied that design, and because the phone stays in the same room as the work. Fitz and colleagues put the slot-machine line in the paper for a reason: an unpredictable ping is more compelling than a scheduled one. Their two-week Android field experiment (237 people, four conditions) is the schedule test. Always-on was the control. Hourly batches barely moved the main outcomes. Three batches a day — predictable windows — left people feeling more attentive, more in control, less stressed, and in a better mood. Turning notifications off entirely did not give those same gains and raised anxiety and fear of missing out. The useful setting is not “never.” It is “not whenever the server feels like it.”

Martin Pielot, Karen Church and Rodrigo de Oliveira then showed what “whenever” looks like in the wild. Fifteen English-speaking Android users, one week, a logging app plus a diary: a mean of 63.5 notifications a day, mostly messengers and email. People typically viewed them within minutes, silent mode or not. Social pressure in personal chat was a stated reason. More notifications tracked more negative emotion and, for messages and social updates, more felt connection. That is a small 2014 observational log, not a law of nature and not your personal quota. Use it as a picture of volume. Do not use it as a target to beat.

The four volume leaks

Four ordinary leaks keep the stream fat: always-on defaults, work chat treated as a live conversation, badge hunger, and a phone that never leaves the desk. None of them require a character flaw. They require a device that ships with alerts on.

  1. Always-on defaults. Apps ask for permission once and then speak whenever they like. Stothart, Mitchum and Yehnert’s participants did not tap anything. The ping was enough to pull sustained attention off a dull, exacting task. In our experience the default is the leak: if you never chose a window, the manufacturer chose “now.”
  2. Work chat as a live conversation. Email and messengers inherited the same interrupt. Kostadin Kushlev and Elizabeth Dunn’s 2014 field experiment on email — 124 adults assigned to check three times a day versus as often as they wanted — found that the frequent checkers reported more daily stress. Newport’s hive-mind language is the workplace version: a culture that treats every message as a conversation in progress will keep minting pings even after you mute Instagram. The channel is the leak, not the emoji pack.
  3. Badge hunger. Pielot, Church and de Oliveira watched people open notifications within minutes, silent or not. A red count is a goal. It is also a residue factory: you leave the file, you peek, you do not finish the peek, you come back worse. That last step is Leroy’s page. This page only needs the badge that caused the leave.
  4. The phone in the room. Ward, Duke, Gneezy and Bos measured the object, not the sound. Own phone on the desk, silenced, face down, still reduced available working memory and fluid intelligence versus the same phone in another room. A mute switch next to the mug is not the finding. Distance is.

Why it costs more than it feels like

A single ping feels free because it is short, but the bill is a switch, leftover attention, and a day that never quite starts. Joshua Rubinstein, David Meyer and Jeffrey Evans modelled the switch itself in 2001: executive control has to shift the goal and then load a new rule set, and both stages take measurable time, more so when the new task is complex. A notification is a forced goal-shift you did not schedule. Gloria Mark, Daniela Gudith and Ulrich Klocke then showed the mood of the catch-up: 48 people writing under interruption finished as fast or faster than uninterrupted people, and paid for it in stress, frustration, time pressure and effort. Speed after a Slack banner is not proof the leave was cheap.

Kushlev, Proulx and Dunn added the week-scale version. Two hundred and twenty-one University of British Columbia students, general pool, not an ADHD clinic, spent one week maximising interruptions (alerts on, phone in reach) and one week minimising them (alerts off, phone away), order randomised. They reported more inattention and hyperactivity symptoms — an 18-item checklist scored as a continuum — in the alerts-on week. Higher inattention then tracked lower productivity and well-being. The authors were explicit: this is not a claim that phones cause ADHD, and it is not a treatment study. Read it as a delivery-schedule effect on how scatterable a non-clinical week feels. Do not read it as a diagnosis.

Two honest caveats. Stothart, Mitchum and Yehnert is a lab SART with undergraduates and a one-session ping, not a week of Slack. Fitz and colleagues is a two-week Android field experiment recruited on Mechanical Turk — useful for schedule, not a licence to promise that three batches will raise your output by a number the paper does not give as a headline percentage. Pielot, Church and de Oliveira is fifteen people in 2014. Volume has moved. The mechanism — variable pings, fast checks, a social pull — has not needed a new name.

Johann Hari’s Stolen Focus is the wider attention story: environments that keep nominating new targets. This page only needs the notification layer of that story. If the stream stays always-on, every later focus trick is applied to a day that already leaked. The parent beam on how to focus better still matters. It cannot out-grit a phone that speaks sixty times before lunch.

How to cut the volume without a monastery

Cut the volume with a mute for the block, three named windows, one parked work channel, and a phone that is not on the desk. This is not a six-step ladder and it is not a diagnosis. It is the smallest set of marks that match the studies above. Fitz and colleagues already ran the “turn it all off” condition. People got more anxious and more afraid of missing out. The useful design is a few predictable deliveries, not a cave.

Mute the stream for the block. Alerts off — sound, vibrate, banners — while one named output is live. Stothart’s participants were not weak. They were doing a dull, exacting task when a real-looking ping arrived. If the block cannot survive a banner, the banner should not be in the room. Write it as an if–then: After I sit, at this chair, I turn alerts off until the next named window.

Batch three times, not hourly. Fitz, Kushlev and colleagues’ hourly condition did not beat always-on on the main outcomes. Three times a day did. Pick clocks you can keep — 11:00, 14:00, 16:30, or whatever matches the job — and let the rest of the stream wait. Kushlev and Dunn’s three-times-a-day email checkers reported less daily stress than people who checked whenever they wanted. The number three is not magic. Predictable and few is the finding. A ping every hour is still a variable stream with a nicer name.

Park the work chat. One channel, one window. Newport’s hive mind is a culture problem wearing a notification badge. You cannot rewrite a whole company from a play article. You can stop treating every @ as a live conversation. A status others can see — “heads-down until the 14:00 batch” — is the social version of a window. If the job is genuinely on-call, make the emergency a phone number, not every channel you have ever joined.

Put the phone in another room. Ward, Duke, Gneezy and Bos’s desk-versus-other-room gap is why “silent but next to the mug” under-solves. Kushlev, Proulx and Dunn’s better week was alerts off and the phone away. Distance is cheaper than a new app. The live sister how to stay on task is the switch protocol once a ping has already landed. This page only needs the stream that keeps landing them.

What are the common mistakes?

The usual mistakes treat mute, hourly inbox-zero, or a new app as the mechanism, and leave the stream always-on.

  • Treating mute as distance. Ward and colleagues measured a silent, face-down phone on the desk. Presence still taxed working memory. Another room is the finding.
  • Hourly “inbox zero.” Fitz and colleagues’ hourly batches did not beat the control on the main well-being and attention outcomes. Three windows did. A ping every hour is still a slot machine with a timetable.
  • Turning everything off and calling it virtue. The no-notification arm in the same experiment raised anxiety and fear of missing out. A cave is not the useful condition.
  • Counting screen time and ignoring the ping. You can pay Stothart’s tax with the screen off. Minutes are a different page.
  • Rewriting attention residue into a settings menu. Leroy’s leftover Task A is a finish-or-park problem. The sister page owns it. Muting does not park a half-written paragraph.
  • Leaving work chat on “notify on every message.” Kushlev and Dunn’s frequent email checkers were more stressed. A channel that pings on every keystroke is always-on with a company logo.
  • Copying the focus parent into a notification article. How to focus better is the beam. This page is the stream. Do not publish a second 6-step focus system under this slug.

When it is more than a habit

If the job is genuinely on-call, or attention trouble sits across weeks and rooms, a batch window will not recreate a lab SART. A&E, incident response, a sick child, a role that is only Slack — those are design constraints. The studies above still describe the mechanism. They do not claim that one person’s if–then overrides a contract or a floor plan.

This page is not a health article and it is not a diagnosis. Kushlev, Proulx and Dunn measured a symptom checklist in a general student pool for two weeks. That is a scatterability score under two phone settings. It is not ADHD, not a cause, and not a treatment. Persistent, cross-context attention trouble that does not move when the phone leaves the room is a different layer — take that to a qualified professional. Attention residue is the sister for the leftover task. How to focus better is the parent beam. This page is only the incoming stream.

What does the evidence actually show?

Every figure above traces to a published paper or to a book used as language, not as a trial. Here is the short version of what each study supports — and what it does not.

Study Design & size What it found Used here for
Stothart, Mitchum & Yehnert (2015), JEP:HPP Lab SART; 212 recruited, 166 analysed; call / text / no-notification A notification people did not handle still raised commission errors; authors compared the size to active phone-use costs The ping is the tax, not the tap
Kushlev, Proulx & Dunn (2016), CHI Within-subjects, 221 students, one week alerts-on vs alerts-off Higher inattention and hyperactivity scores with alerts on; not a clinical sample A week of pings feels more scatterable. Not a diagnosis
Fitz, Kushlev, Jagannathan, Lewis, Paliwal & Ariely (2019), CHB Two-week Android field RCT, n=237; always-on / hourly / 3× day / off 3× day improved attention, mood, stress, control vs control; hourly ≈ control; off raised FoMO Predictable few windows, not hourly, not a cave
Pielot, Church & de Oliveira (2014), MobileHCI One-week log + diary, 15 Android users Mean 63.5 notifications/day; viewed within minutes, silent or not A picture of volume. Small, old, observational
Ward, Duke, Gneezy & Bos (2017), JACR Experiments on smartphone presence (desk vs pocket vs other room) Own phone on the desk reduced available working memory and fluid intelligence even when silent and face down Distance beats a mute switch
Kushlev & Dunn (2014), CHB Field experiment, 124 adults, email 3×/day vs unconstrained More frequent checking, more daily stress Email batching is a volume cut
Leroy (2009), OBHDP Lab experiments on task switching Unfinished switches leave attention residue that impairs the next task Why a peek can leave the file worse. Sister page owns the fix
Mark, Gudith & Klocke (2008), CHI Lab, 48 people, interrupted vs uninterrupted writing Interrupted people finished faster, with more stress, frustration, time pressure and effort Speed after a banner is not a cheap leave
Rubinstein, Meyer & Evans (2001), JEP:HPP Lab task-switching, four experiments Goal shift then rule activation; both take time, more so when the new task is complex Why a ping is a forced goal-shift

Frequently asked questions

What is notification overload?

Notification overload is a volume problem: too many alerts arriving as a variable stream, so attention keeps paying a switch tax. Cary Stothart, Ainsley Mitchum and Courtney Yehnert found that a bare ping — a call or text the person did not look at — disrupted a sustained-attention task about as much as studies of actually using the phone. This page is the pile-up. It is not screen-time minutes, and it is not leftover focus from the last file. Opening the phone is optional. The tax is not.

Does a notification still cost me if I never open it?

Yes, on the best available attention task we have. Stothart, Mitchum and Yehnert analysed 166 undergraduates on a Sustained Attention to Response Task. People who received a call or a text, and who did not look at or handle the phone, still made more commission errors in the second block than the no-notification group. The authors compared that drop to the size of costs in active phone-use studies. A silent badge you never tap is not free. It is a new goal nomination.

Is batching notifications better than turning them all off?

In Nicholas Fitz, Kostadin Kushlev, Ranjan Jagannathan, Terrel Lewis, Devang Paliwal and Dan Ariely’s two-week field experiment (n=237), three predictable batches a day beat the always-on stream on attention, mood, stress, and sense of control. Turning notifications off entirely did not give those same gains and raised anxiety and fear of missing out. Hourly batching barely moved the main outcomes. The useful setting is a few named windows, not a monastery and not a ping every hour.

How is notification overload different from attention residue?

Notification overload is the incoming stream. Attention residue is what the last unfinished task still does to the next one after you have already switched. Sophie Leroy’s 2009 experiments are the residue page: thoughts about Task A keep running and Task B gets a worse version of you. A ping can cause a switch that then leaves residue, but the two pages do not own the same keyword. Link across. Do not collapse them. How to focus better is the parent beam those two children sit under.

Will silencing my phone on the desk fix it?

Silence removes the sound. It does not remove the object. Adrian Ward, Kristen Duke, Ayelet Gneezy and Maarten Bos found that the mere presence of your own smartphone reduced available working memory and fluid intelligence even when the phone was silenced and face down. Another room beat a pocket; a pocket beat the desk. Kushlev, Proulx and Dunn’s “alerts off and phone away” week is the pair: mute plus distance. A face-down phone next to the mug is the condition Ward already measured.

How many notifications is too many?

There is no lawful number. Martin Pielot, Karen Church and Rodrigo de Oliveira logged one week for 15 Android users and reported a mean of 63.5 notifications a day, mostly messengers and email. That is a small, 2014, observational log — useful as a picture of volume, not a personal quota. The cost evidence is about delivery, not a magic count: a single unexpected ping (Stothart) and an always-on stream versus three windows (Fitz). If the stream is variable and you did not choose the window, you are already in the tax.

Does this mean I have ADHD if pings scatter me?

No. Kushlev, Proulx and Dunn used an 18-item inattention and hyperactivity symptom checklist with 221 students from a general university pool, not a clinical sample, and they said so. A higher score for one week of alerts-on is not a diagnosis, not a cause of ADHD, and not a treatment claim. This is a productivity page about a delivery schedule. Persistent, cross-context attention trouble that does not move when the phone leaves the room is a different layer — take that to a qualified professional, not to a mute switch.

How do I cut notification overload at work without looking unavailable?

Name the window the way you would name a meeting. Fitz and colleagues’ useful condition was three predictable batches, not radio silence. Park the work chat in one channel and one window; Cal Newport’s A World Without Email is the language for a hive mind that treats every ping as a live conversation. A status others can see — “heads-down until 11, then Slack” — is the social version of a batch. Always-on is not the same as being a good colleague. It is a delivery schedule you did not choose.

Sources

  1. Stothart, C., Mitchum, A., & Yehnert, C. (2015). The attentional cost of receiving a cell phone notification. Journal of Experimental Psychology: Human Perception and Performance, 41(4), 893–897. doi:10.1037/xhp0000100
  2. Kushlev, K., Proulx, J., & Dunn, E. W. (2016). “Silence Your Phones”: Smartphone notifications increase inattention and hyperactivity symptoms. In Proceedings of the 2016 CHI Conference on Human Factors in Computing Systems (pp. 1011–1020). doi:10.1145/2858036.2858359
  3. Fitz, N., Kushlev, K., Jagannathan, R., Lewis, T., Paliwal, D., & Ariely, D. (2019). Batching smartphone notifications can improve well-being. Computers in Human Behavior, 101, 84–94. doi:10.1016/j.chb.2019.07.016
  4. Pielot, M., Church, K., & de Oliveira, R. (2014). An in-situ study of mobile phone notifications. In Proceedings of the 16th International Conference on Human-Computer Interaction with Mobile Devices & Services (pp. 233–242). doi:10.1145/2628363.2628364
  5. Ward, A. F., Duke, K., Gneezy, A., & Bos, M. W. (2017). Brain drain: The mere presence of one’s own smartphone reduces available cognitive capacity. Journal of the Association for Consumer Research, 2(2), 140–154. doi:10.1086/691462
  6. Kushlev, K., & Dunn, E. W. (2014). Checking email less frequently reduces stress. Computers in Human Behavior, 43, 220–228. doi:10.1016/j.chb.2014.11.005
  7. Leroy, S. (2009). Why is it so hard to do my work? The challenge of attention residue when switching between work tasks. Organizational Behavior and Human Decision Processes, 109(2), 168–181. doi:10.1016/j.obhdp.2009.04.002
  8. Mark, G., Gudith, D., & Klocke, U. (2008). The cost of interrupted work: More speed and stress. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 107–110). doi:10.1145/1357054.1357072
  9. Rubinstein, J. S., Meyer, D. E., & Evans, J. E. (2001). Executive control of cognitive processes in task switching. Journal of Experimental Psychology: Human Perception and Performance, 27(4), 763–797. doi:10.1037/0096-1523.27.4.763

The books behind this

Related articles

Go deeper

How this article was researched

The Growth Reads editorial team writes from primary sources: the books themselves and the peer-reviewed literature behind the claims. The SART notification experiment, the two-week alerts-on versus alerts-off student study, the Android batching field experiment, the 15-person notification log, the smartphone-presence experiments, the email-checking field experiment, the attention-residue experiments, the interrupted-writing study, and the task-switching model above were checked against the original papers or their published abstracts and are quoted with design and, where the source supports it, the direction of the effect. Percentages the papers do not state as headline effects are not invented here. Stothart, Mitchum and Yehnert (2015) is a one-session undergraduate lab task, not a week of Slack. Fitz and colleagues (2019) is a two-week Mechanical Turk Android trial — useful for schedule, not a personal KPI. Pielot, Church and de Oliveira (2014) is flagged as fifteen people because that is the sample. Kushlev, Proulx and Dunn (2016) is flagged as a non-clinical symptom score because that is what the design supports. Newport’s A World Without Email and Hari’s Stolen Focus are cited as language for hive-mind culture and leaky attention environments, not as trials.

This article contains no medical advice and no diagnosis. Nothing above should be read as a claim that notifications cause ADHD, or that a mute switch treats a clinical attention condition.

How we work: every article on The Growth Reads is built from the books in our library plus the research they rest on, and is reviewed and date-stamped when the evidence changes. Read our full methodology.