Forcing one dominant sense discards useful information from the others

What it is

Collapsing a conflict into one dominant sense discards valid information from the others. To make channels agree, systems sometimes keep only the dominant channel's version and drop the rest. Contradiction disappears, but so does the corroborating evidence other channels supplied.

Why it happens

The other channels are often valuable precisely where the dominant one fails: haptic confirmation still arrives when vision is occluded, and visual cues remain readable in noise. Forced unification binds system behavior to one channel's availability, so when that channel fails, everything fails with it. Unification also hides the conflict itself, removing the system's chance to notice a problem such as a mis-calibrated sensor. Consistency is necessary, but it should be achieved by fixing the source of inconsistency rather than deleting non-dominant information.

Studying it

Compare unification and correction strategies for robustness: run both while the dominant channel fails and measure task success, error type, and fault discoverability. Variables include failure type (occlusion, noise, sensor fault), redundancy level, and task criticality. Include time to fault detection, since masking conflict delays discovery of systemic problems.

Where it stops holding

When a channel is genuinely supplying wrong information, ignoring it beats keeping it, and unifying while fixing the source is correct. When the other channel carries exactly the same information (pure redundancy), dropping it loses no information but still affects availability, since the dominant channel can fail. If the system cannot tell which side is right, surfacing both and asking the user beats unilateral unification.

Applying it

• Keep the other channels' independent information and use it to cross-check the dominant channel rather than overwrite it.
• When conflict is detected, fix the source instead of hiding the non-dominant evidence.
• When neither side can be adjudicated, present the conflict and request confirmation.
• Verification: with the dominant channel failing, measure task success and fault detection time; a clear decline or long-undetected fault means the unification over-depends on one channel.

Related

• Within the group: D4.07.1 Systems usually trust vision first when channels conflict · D4.07.4 Adjudication should let users perceive that a conflict occurred
• Adjacent: D4.07.2 Dominance is not fixed and depends on task and individual · D4.08.1 Redundancy improves delivery in high noise or high load
• Search terms: redundancy · fault detection · single point of failure