Switching should be user-initiated, not forced
Aliases: user control · forced switching · automatic switch
What it is
Modality switching should be initiated by the user. When the system changes modality on its own, users are often still in the previous mode and must reorganize, raising cost and error. A user-initiated switch happens when it matches the user's current state.
Why it happens
The advantage is timing: users know their hand position, attention, and environment, so they switch when the cost is lowest. A forced switch commonly lands when the user is unprepared—demanding speech just as they are focused on touch. It also undercuts predictability, preventing stable habits from forming. When the system must switch for availability reasons—the current modality is unusable—the right move is to announce the switch and wait for confirmation rather than changing the input mode outright.
Studying it
Compare user-initiated and forced switching: measure post-switch completion time, error rate, and accuracy in identifying the active modality. Variables include the switch trigger, whether a notice is shown, and user readiness. Include the rate of misidentifying the active modality, since that is the main risk of forced switching.
Where it stops holding
When the original modality is entirely unavailable—microphone in use, camera occluded—the system must switch, and notice plus confirmation is the next-best but necessary approach. When switching cost is very low and transparent to the user, forced switching interferes less. If users have explicitly asked the system to choose automatically, system-led switching meets their expectation.
Applying it
- Default to user-initiated switching and have the system only suggest when necessary.
- When the system must switch, show a notice and wait for confirmation rather than changing input mode outright.
- Display the active modality after a switch so users do not continue in the old mode.
- Verification: compare completion time and modality misidentification under user-initiated and forced switching; clear misidentification argues for notice-and-confirm.
Related
- Within the group: D5.03.1 Switching modalities costs attention and limb reconfiguration · D5.03.2 Frequent switching cancels the benefit of multimodality
- Adjacent: D5.09.4 After an explicit switch, the system should not silently revert · D5.10.2 Failed detection should suggest an alternative modality rather than fail silently
- Search terms:
user-initiated switching·forced switch·mode transparency