User Experience Considerations
This domain tests whether you separate usability from the wider user experience and whether you can pick measures that reflect users' perceptions, not only task success. Items often contrast ISO definitions or ask what a given metric tells you.
Definitions to keep apart
ISO 9241-11 defines usability as the extent to which a system can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use. ISO 9241-210 defines user experience as a person's perceptions and responses resulting from use or anticipated use: it includes emotions, beliefs, preferences and comfort, and covers interaction before, during and after use.
What UX adds
- Utility (does it do what users need), desirability, trust and perceived value.
- Context of use: users, tasks, equipment, and the physical and social environment.
- Journey-level qualities: first impression, learnability, memorability, error recovery, feedback and perceived performance.
- Human-centred design principles: explicit understanding of users and context, active user involvement, iteration, user-centred evaluation and a multidisciplinary team.
Measuring it
Behavioural metrics (completion, time, errors, usage logs) show what happened; attitudinal metrics (SUS, UEQ, NPS) show how it felt. NPS measures loyalty and is weak as a stand-alone usability measure; SUS gives one 0-100 usability score.
Worked example
A banking app shows 96% transfer completion but low SUS scores and complaints of anxiety during transfers. Task success alone would hide the problem. The issue is trust and feedback: add clear progress and confirmation states, then retest with SUS plus a post-task confidence question. Reasoning: UX problems can coexist with high effectiveness.
Traps
Treating UX as visual design; assuming one attitude score proves usability; ignoring context such as one-handed outdoor use; measuring satisfaction before users attempt real tasks.