Reference record

What is notification fatigue?

Notification fatigue is the reduced attention people give to repeated alerts, especially when the alerts look, sound, and arrive in the same way. The result is practical: a reminder can remain technically delivered while becoming less likely to be noticed, read, or acted on.

Repetition changes the signal

An alert competes with work, conversation, movement, and other alerts. When its appearance predicts no immediate consequence, people learn to dismiss it with less inspection. Repetition can make the notification familiar enough to filter before its content has been considered. The reminder has not failed to arrive. It has become easy to classify as background.

Pielot, Church, and de Oliveira's An in-situ study of mobile phone notifications at MobileHCI (2014) examined notification volume, attention, and user responses. Their study supports the narrower point that delivery is not the same as attention for recipients. It did not test Funes's delivery review or establish that changing a channel or timing restores attention.

Dismissal is not acknowledgement

A dismissed alert may mean that the task is complete, that the person intends to return later, or that the alert was removed before it was understood. Treating every dismissal as success makes the system's records look cleaner than the user's memory. Repeated dismissal can also train a person to interact with the notification surface rather than the task itself.

Mark, Gudith, and Klocke's CHI study, The Cost of Interrupted Work (2008), found that interruptions change how people structure and resume work. Its results do not establish one universal notification schedule. They do support a conservative design principle: a reminder system should account for the cost of asking for attention, not count attention as free.

Variation can restore attention

Changing a reminder's timing, channel, wording, or surrounding context can make the next delivery less predictable. Funes uses that as a product rationale, not as a mechanism established by the studies cited here. Variation should have a purpose. Random noise is not a plan, and a new channel can create a new burden if it arrives at the wrong time. A useful system distinguishes a missed task from a person who is simply unavailable.

Iqbal and Horvitz's field study, Notifications and Awareness (CSCW, 2010), examined alert use and preferences in workplace settings. It is a reminder that interruption handling depends on context and user preference, not only on the urgency assigned by the sender.

Good notification design also gives the recipient a way to reduce unnecessary contact. Clear controls, sensible batching, and a visible acknowledgement state help a person decide what requires action. Without those controls, increasing the frequency of delivery can turn a memory aid into another source of avoidance. The system should learn from a missed acknowledgement without treating the person as a failed component.

Funes operational note

Funes records the delivery method, the acknowledgement, and the time between them. When a familiar channel produces no useful response, the service reviews the next delivery rather than sending the same message with greater confidence. The adjustment is operational. We do not describe it as a moral judgement on your attention.

Last updated: 28 May 2026. Related record: why reminder timing changes across a cycle.