Preferences should change with context rather than apply to every situation
Aliases: situated preference · scope boundary · profile switching
What it is
A modality preference must bind to context, task, and device rather than turn one situation's choice into a global default. Silent text in a meeting, speech in a kitchen, brief cues while driving, and vibration-only at night are reasonable answers by the same person under different constraints.
Why it happens
Context changes availability, social consequence, and task demand. Voice suits occupied hands but leaks a meeting; a screen suits private display but is hazardous while driving; haptics are quiet and noninterruptive but carry few fields. Globalizing one preference discards those differences. Scope should follow context keys: place, time, device form, peripherals, network, task type, privacy mode, or system state. Conflicting keys need explicit precedence, with safety mode above place preference, for example.
Studying it
Collect one user's choice matrix across contexts and compare global preference, context-scoped preference, and ask-every-time. Variables include granularity, context-change frequency, task type, and privacy. Outcomes include modifications per task, wrong-channel use, switching time, and disturbances. Examine boundary transfers especially: company to home, phone to car, day to night, personal to shared. Too-fine grains yield sparse evidence; too-coarse grains mix conflicting choices.
Where it stops holding
More context keys are not inherently better. Over-segmentation leaves little evidence per preference and makes system changes hard to explain; sensitive features add profiling risk. Some contexts are ambiguous—a sensitive meeting at home or working in a parked car—so the active scope should be visible and overridable. Preference also cannot conflict with runtime detection: the same context with a broken device yields a suggestion, not a fact.
Applying it
- Define a small set of stable context keys and precedence, and show the active scope in the interface.
- Never automatically promote a restricted-context choice to global; promotion requires explicit confirmation.
- When context changes, say which preference will apply and allow immediate reselection.
- Verification: audit modification frequency and wrong-channel use across real contexts; merge or resegment any scope that users constantly override.
Related
- Within the group: D5.11.1 The system may remember modality preferences in specific contexts · D5.11.4 Overreliance on historical preference delays response to current environmental change
- Adjacent: D5.04.1 Noise, light, and social setting determine modality availability · D5.10.1 The system must detect at runtime whether the environment supports the default modality
- Search terms:
context scope·profile switching·situated preference