Description
Compare what users will expect to do, what sensors can detect and what functions are wanted, to find undiscoverable functions and spare inputs in sensor-based interfaces.
Sensor-based and tangible interfaces have no fixed buttons, so mismatches between user actions, sensing and functions are easy to create. ESD lists three sets: expected actions (what people will naturally do with the device), sensed actions (what the sensors can detect) and desired actions (what the designer wants to support). Placing each item in the seven regions of a Venn diagram shows where design work is needed. The centre, where all three overlap, works well. Sensed and desired but not expected means a hidden function users will not discover. Expected and sensed but not desired is spare input that could carry an unsupported desired function. Expected but not sensed means actions the system will ignore, a source of frustration.
Attributes
- Discipline
- Human Factors & Error
- Loss type
- Siloed
- Stage
- Design
- Data
- Analytical / expert
- Effort
- Hours
Steps
- List the actions users are likely to perform with the device in context.
- List everything the sensors can detect.
- List the functions the design should support.
- Place each item in the seven-region Venn diagram.
- Flag hidden functions (sensed and desired but not expected) and ignored actions (expected but not sensed).
- Reassign spare expected-and-sensed actions to unsupported desired functions, then test discoverability.
Sources
- Touch IT (Dix et al., 2022)
Also known as
- ESD framework
- Expected, sensed and desired framework
Categories
- Accessibility
- Human Factors & Error