Frequent false editing indicators lead users to abandon the signal
Aliases: awareness cue fatigue · false-positive habituation · signal distrust
What it is
Alarm fatigue in awareness cues occurs when repeated “someone is editing” signals without real overlap teach users not to change behavior. The loss extends beyond individual false alarms: declining predictive value changes the user's general policy, so a true conflict is also ignored. Volume contributes, but the defining problem is weak correspondence between signal and needed action.
Why it happens
Users learn the probability of conflict after a cue and the cost of yielding. If most cues arise from distant edits, ghost states, or irrelevant formatting, responding creates waiting without benefit, making disregard rational. Stronger color, motion, or sound can recapture attention briefly but cannot repair low precision and may accelerate habituation.
Studying it
Longitudinal tasks can vary false-positive prevalence and conflict consequence, tracking cue response, yielding on true conflict, waiting, and trust across trials. Field evaluation should compute precision and recall, stratified by scope and collaborator relationship. Click rate alone cannot distinguish a useless cue from an alternative coordination strategy.
Where it stops holding
Rare high-consequence work may tolerate more false alarms, but needs graded severity. Nonresponse can reflect lack of an actionable option rather than distrust. Brief usability tests miss trust decay; strong first exposure does not imply durable effectiveness.
Applying it
- Emphasize cues only when edit scopes may overlap; leave other activity as inspectable background.
- Fix scope, timeout, and connection inference before making a low-precision signal louder.
- Provide actions to inspect, contact, or continue with an explicit merge consequence.
- Measure precision, response decay, and true-conflict yielding over multiple work cycles.
Related
- Same group: V2.06.1 Cues support yielding rather than blocking · V2.06.2 Cues must appear when editing starts · V2.06.3 Cues need local scope · V2.06.4 Retention time determines accuracy
- Adjacent: V2.02 Workspace awareness · V4.03 Notification and subscription granularity
- Search terms:
alarm fatigue·false positive·awareness cue trust
Cards in the same group
- V2.06.1An editing indicator should support voluntary yielding rather than block modification
- V2.06.2The indicator must appear when editing begins, not after a conflict
- V2.06.3The indicator must locate activity to a specific passage rather than the document alone
- V2.06.4How long an indicator persists after input stops determines its accuracy