Skip to content

Receiver Fatigue Survey

Receiver audit — instantiates Signal Value Preservation

Asks receivers directly how worn-down and inattentive a signal stream has made them — capturing the subjective fatigue and trust erosion that behavioral metrics alone miss.

Receiver Fatigue Survey is a periodic instrument that asks the receivers themselves — by survey or structured interview — how a signal stream is landing: whether they still notice it, trust it, feel overwhelmed by it, or have started tuning it out. Its distinguishing idea is that it measures the subjective, self-reported side of signal fatigue — perceived overload, annoyance, eroded trust — which behavioral dashboards cannot see until it finally shows up as action or inaction. Where a response dashboard watches what receivers do, the fatigue survey asks what they feel and believe, catching the erosion of attention and credibility while it is still an attitude, before it hardens into a signal nobody reads.

Example

A mobile app's engagement numbers still looked acceptable, but a fatigue survey of a standing user panel asked directly: how many of our notifications feel worth opening? Have you considered turning them off? Do you trust that a notification from us means something important? A large share reported feeling "spammed" and said they now swipe everything away unread — several were one annoyance away from disabling notifications entirely.[1] That subjective reading, invisible in the still-okay open rate, warned the team that the channel's credibility was nearly spent before the behavioral cliff arrived. They cut low-value pushes while there was still trust left to preserve.

How it works

The distinctive move is to elicit self-report on noticing, trust, overload, and intent-to-disable, segmented by receiver group and repeated on a cadence so trends are visible. It captures perceived attention cost and credibility erosion — leading, attitudinal indicators — rather than logged behavior, which is why it can flag a problem a quarter before the numbers do.

Tuning parameters

  • Cadence — one-off pulse vs. a recurring tracker. Recurring reveals trend and early erosion; one-off is only a snapshot.
  • Question framing — trust, overload, notice, intent-to-disable — which facets are probed. Broad catches more; focused stays comparable over time.
  • Panel vs. census — a standing receiver panel vs. sampling everyone. Panels track change per-person; censuses catch subgroup differences.
  • Segmentation — slicing by receiver type, tenure, or exposure. Fine segments locate where fatigue concentrates but need larger samples.
  • Self-report correction — how heavily to discount known survey biases; pairing with behavioral data anchors the subjective read.

When it helps, and when it misleads

Its strength is that it is a leading indicator — it catches credibility and attention erosion while it is still a feeling, and it surfaces why (annoyance, distrust, irrelevance), which behavior alone cannot explain. Its failure mode is that self-report is biased: people over- or under-state fatigue, and the loudest respondents dominate, so a survey read taken alone can mislead. The classic misuse is running the survey to confirm a decision already made, via leading questions that manufacture the answer. The discipline that guards against this is neutral wording, a standing panel for trend, and triangulation against the behavioral Receiver Response Dashboard rather than treating self-report as ground truth.

How it implements the components

  • receiver_feedback_panel — the survey is the receiver-feedback instrument: a standing channel for receivers to report how the signal lands.
  • receiver_attention_budget — it measures where receivers' attention is exhausted, surfacing the demand-side depletion the sender can't observe directly.
  • habituation_and_adaptation_monitor — it tracks, subjectively, whether receivers have begun tuning the signal out over time.

It does not measure behavior — whether receivers still act on the signal (receiver_interpretation_model) — that is the Receiver Response Dashboard; and it does not set the attention-budget policy or cap issuance (channel_scarcity_policy), which the Alert or Label Budget does.

Notes

The survey and the Receiver Response Dashboard are complements, not substitutes: one reads what receivers feel, the other what they do, and neither alone is trustworthy. Sentiment can sour before behavior moves, and behavior can collapse while everyone still says they're fine — the pair is most informative when the two readings disagree.

References

[1] Alert (or notification) fatigue is the documented desensitization that sets in when receivers face a high rate of low-value signals — well studied in clinical alarms and operational alerting alike. Because it is a state of the receiver, self-report reaches it earlier than behavioral counts do. ↩