Users should be able to override the default arbitration for a situation

What it is

Users should be able to override the default arbitration for a specific situation. Defaults are set for general cases, but a user may be in a state where only one event class matters—waiting for a critical notification, for instance. A temporary override lets them reallocate attention to the current need without changing global settings.

Why it happens

The mismatch between default rules and individual situations comes from information asymmetry: the designer does not know what the user is waiting for, and the user does. A temporary override feeds that information back into arbitration so results fit the user's need. Compared with changing settings globally, an override has a defined scope and will not keep affecting other situations afterwards, which is why users are willing to use it. It requires stating the scope—this instance only, until manually restored, or by category—and displaying the active override, or users may forget to restore it.

Studying it

Measure actual use and consequences of overriding: record whether critical events arrive after an override, whether users restore defaults, and whether they forget to restore long-term. Variables include the reachability of the entry point, the scope setting, and situation type. Outcomes include use rate, restore rate, and critical-event miss rate, the last testing whether overrides are misused.

Where it stops holding

When the override's scope is unclear, users may sit under modified rules long-term and miss other important events, so explicit scope and visible state are preconditions. If a class is deemed non-degradable, the override should not allow turning it off entirely. If overrides are rarely used, either the defaults already fit well or the entry point is not reachable enough.

Applying it

• Provide a reachable temporary override and state its scope and how to restore.
• Keep the active override visible so users do not forget it.
• Limit the override range for non-degradable classes, allowing adjustment rather than disabling.
• Verification: track critical-event miss and restore rates after overrides; rising misses or widespread non-restoring means the scope design needs revision.

Related

• Within the group: D5.06.3 Priority follows consequence level, not channel capability · D5.06.6 Cross-application arbitration usually belongs to the system layer
• Adjacent: D2.11.1 Users need to control sound by category rather than all-or-nothing · D5.09.4 After an explicit switch, the system should not silently revert
• Search terms: user override · temporary rule · context exception