High-intensity feedback for low-consequence actions creates persistent interference

What it is

Alert overuse applies high-intensity feedback—dialogs, sound, vibration, flashing, full-screen scrims, or forced interruption—to low-consequence, reversible, nonurgent operations. One emphatic confirmation may feel responsive, but in frequent work it repeatedly breaks reading, entry, and flow. People learn not “this is important” but “the system always steals attention,” then defend themselves by muting, ignoring banners, or mechanically dismissing. Truly important signals get pulled into the same noise pool.

Why it happens

High salience costs attention switching, action interruption, visual/auditory occupancy, and emotional arousal. Low-consequence events usually need only evidence that they happened; a local state change is enough. Extra sound, flash, and blocking do not improve decision quality and accumulate task-resumption time. Repetition produces habituation and alert fatigue, lowering sensitivity to the channel as a whole. Each notice may appear delivered, while the system-wide signal–risk mapping has failed.

Studying it

Compare local static confirmation and strong interruption in frequent low-consequence work. Measure task time, input error, workload, mute/dismissal behavior, and detection of genuinely high-priority events. Include long sessions and mixed events: novel animation may test well briefly while concealing fatigue. Watch for unread dialogs, reflexive closure, and attempts to bypass settings; they reveal interference better than one-off satisfaction.

Where it stops holding

Low consequence is not a permanent ban on salience. First use, learning a critical rule, a user-requested result, or a task highly dependent on a small state can temporarily warrant visibility. Public safety, compliance, and accessibility may need redundant channels. Judge by event frequency, current attention load, and reversibility rather than dimming every success. Reducing intensity cannot become silent failure or missing evidence.

Applying it

• Audit frequent feedback; downgrade reversible confirmation to object-level change, light state, or reviewable summary rather than dialogs, sound, or flash.
• Treat user-requested, first-occurrence, and escalating-risk cases differently from routine flow so teaching and abnormal paths do not share one intensity.
• Measure interruption count and primary-task resumption in high-frequency workflows, not only single-notice visual impact.
• Monitor notification disabling, muting, and immediate dismissal; these overload signals should trigger de-escalation or aggregation.

Related

• Within the group: D1.15.1 Consequence-proportionate feedback · D1.15.3 Low intensity understates high risk · D1.15.4 Product-wide intensity consistency
• Adjacent: D1.09.3 Multiple flashes erase priority · D2.10 Priority arbitration for multiple alarms
• Search terms: alert fatigue · interruption cost · notification overload