Satisfaction concerns the subjective experience
Aliases: satisfaction · subjective evaluation · satisfaction scales
What it is
Satisfaction measures users' subjective evaluation of the process and its result: comfort, control, trust, willingness to return. It reflects the user's verdict, not the product's objective behavior—with identical operational performance, different expectations and preferences yield different scores.
Why it happens
The subjective evaluation arises from comparing actual experience against expectation: expectation comes from past products, category benchmarks, and brand impressions, so satisfaction has a moving baseline—as the whole category improves, the passing line rises with it. Satisfaction also carries judgments of control and trust that correlate weakly with operational data: a high-completion flow can still score low because it feels out of the user's hands.
Studying it
Standardized scales (SUS, AttrakDiff) give comparable composite scores across versions; task-level immediate ratings capture emotional reactions to specific moments; interviews and open questions explain what the score means. Timing matters: immediate post-task ratings and next-day recalled evaluations differ, both are useful, and reports must state which was collected.
Where it stops holding
Satisfaction does not predict behavior: high-scoring products can go unused, and poorly rated tools can be indispensable. Scores shift with testing context—experimenter courtesy, compensation, task order. Cross-cultural comparison needs validated translations. And it cannot replace objective performance measurement; the two frequently diverge.
Applying it
- Fix one scale across usability rounds and use scores for version-over-version comparison, not absolute pass marks.
- Collect subjective ratings at task end and study end to separate momentary experience from overall judgment.
- Follow low-scoring moments with probes that turn "didn't like it" into a modifiable design problem.
Related
- Same group: B5.02.1 Effectiveness asks whether the task gets done · B5.02.2 Efficiency asks how many resources the effort costs · B5.02.4 The three can diverge and must be measured separately
- Nearby: B5.05 Experience versus usability · P1 Emotional Design
- Search terms:
satisfaction·system usability scale·subjective evaluation