After overload, users turn off all haptics

What it is

The usual end state of haptic overload is that users switch haptics off entirely. When it is unclear which vibrations matter and handling each one is unwanted work, disabling everything is the cheapest option. The system then loses a whole channel, along with the information it could have carried well.

Why it happens

Wholesale disabling is a rational choice, not misuse: without a way to separate categories, users cannot keep only the valuable part and must decide on aggregate cost. It is also an attention economics problem—each cue demands an interruption, and once cumulative cost exceeds benefit, abandoning the channel pays. The system-side loss is underestimated because the switch lives in settings, silently voiding every downstream haptic design that the designer never sees fail.

Studying it

Study the triggers of disabling through logs and interviews: record vibration frequency and content distribution in the window before users disable, and identify which cues drove the decision. Variables include total volume, availability of category-level disabling, and whether critical cues are identifiable. Outcomes include disable rate, whether users re-enable, and what triggers re-enabling.

Where it stops holding

Where a product uses very few haptics, users rarely bother to disable anything and wholesale muting is uncommon. When haptics are coupled to system silent or do-not-disturb modes, disabling may be a side effect rather than a choice, and the two must be distinguished. If a critical function depends on haptics with no substitute, user disabling carries more serious consequences and the design must guard against it.

Applying it

• Provide category-level disabling so "reduce noise" and "keep critical haptics" can coexist.
• Hold total haptic volume below the level that triggers wholesale abandonment, and monitor the disable rate.
• Explain at the switch what information will be lost, so the choice is informed.
• Verification: track disable rate and re-enable behavior; if disables cluster in particular time windows, locate the vibration sources in those windows and trim them.

Related

• Within the group: D3.08.1 Frequent haptic cues make users less sensitive to them · D3.08.3 The haptic budget should follow event importance
• Adjacent: D3.12.1 Haptics need a global off switch rather than forced always-on · D2.11.1 Users need to control sound by category rather than all-or-nothing
• Search terms: haptic mute · master switch · user workaround