Excessive feedback is actively ignored

What it is

When a system frequently supplies low-value, repeated, or task-irrelevant prompts, people develop alert fatigue: they close, skip, mute, or cease noticing feedback. Feedback volume is not information sufficiency. When every prompt demands attention, states that genuinely need action are more likely to be drowned out.

Why it happens

Attention is scarce. Recurrent signals that provide no new action value teach people that ignoring them usually has no cost, and this strategy transfers to similar prompts. Interruptions also disrupt ongoing thought and entry, encouraging the shortest route back to the primary task—such as confirming without reading. Over time the system loses its ability to distinguish urgent from ordinary events, and important warnings are treated as background noise.

Studying it

Review live-use logs for prompt frequency, dismissal, recurrence, subsequent action, and missed critical events; do not count delivery alone. Compare reading, understanding, and response under different frequencies, grouping strategies, and priorities in simulated and real tasks. Interviews should uncover the filtering rules people create, such as which channels they mute or when they confirm automatically.

Where it stops holding

Reducing feedback does not mean silence. Critical safety, state-change, or intervention-needed information must remain available, though it need not interrupt every time. The value of one event differs by role: an operator may need an aggregated overview while a person executing a task needs an in-place cue. Putting all infrequent events into a digest can also delay truly urgent response.

Applying it

• Remove prompts with no clear action value, and aggregate repeated, predictable, or low-priority events into reviewable summaries.
• Use severity, clustering, and role to distinguish in-place feedback, gentle notice, and necessary interruption.
• Let people control frequency and channel while monitoring consequential events that were ignored, then iterate thresholds and wording.

Related

• Same group: B2.06.1 Every action needs perceptible information about its result · B2.06.2 Feedback must be timely; delay is attributed to nonresponse · B2.06.3 Feedback intensity should match action importance
• Nearby: B2.10 Notifications · B2.11 Error prevention
• Search terms: alert fatigue · notification overload · attention management