Usability is a measure of how easily and reliably people can accomplish what they came to do. It is not a synonym for good looks, and it is not a matter of taste. It asks three answerable questions: can the user complete the task, how long does it take, and how many mistakes do they make along the way.
That answerability is what makes usability useful. Where design debates stall on opinion, usability can be tested and the argument settled with evidence.
The five components of usability
Nielsen Norman Group defines usability through five components, and this model is the working industry standard: 1
- Learnability — how easily can a first-time user complete basic tasks?
- Efficiency — once learned, how quickly can tasks be completed?
- Memorability — after time away, how easily does competence return?
- Errors — how many mistakes do users make, how severe are they, and how easily can users recover?
- Satisfaction — how pleasant is the design to use?
The international standard defines usability in compatible terms: 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. 4 Note how much work "specified" is doing in that sentence — usability is never absolute. A tool that is highly usable for a trained operator can be unusable for a first-time visitor.
Usability and user experience are not the same thing
Usability is one part of user experience, and the most testable part. User experience covers everything about how it felt to encounter the product — including whether it solved a real problem, how the brand behaved, and what happened after the interaction ended.
The practical distinction: usability asks how — how do I complete this task?User experience asks what, why and how together. A checkout can be perfectly usable and still be part of a poor experience, if the product was wrong, the delivery promise was misleading or the returns process was hostile.
Why usability is an economic question
Treating usability as polish, to be applied if there is time left over, gets the causality backwards.
- Revenue. A checkout that is hard to complete produces abandoned carts. This is the most direct link between usability and money, and it is why conversion rate optimisation is largely a usability discipline in practice.
- Retention. People do not return to products that made them feel incompetent. Friction is remembered even when its cause is not.
- Cost of change. Fixing a problem in a design file is cheap. Fixing the same problem after it is built is more expensive, and fixing it after release is more expensive again — because the cost now includes the users it already affected.
- Credibility. A product that is easy to use reads as competent and trustworthy. One that is not raises doubt about everything behind it.
How to run a usability test
Usability is measured with people, not with opinions in a meeting. A workable test takes five steps:
- Set the objective. Name the task you are testing, precisely. "Testing whether a new user can book an appointment in the mobile app" is testable; "testing the app" is not.
- Recruit five to seven participants who resemble your users. Jakob Nielsen's finding is that a first study with five participants surfaces roughly 85% of an interface's usability problems. 2 The implication is not "test less" — it is that several small studies beat one large one, because you can fix problems between rounds.
- Write scenarios, not instructions. Do not say "book an appointment".Say: "Imagine you need a dentist appointment for next Tuesday. Please try to arrange that." An instruction tests obedience; a scenario tests whether the interface is findable.
- Observe, and stay quiet. Do not help. Ask participants to think aloud so you hear what they expected, not just what they clicked.
- Prioritise by severity. A problem that stops task completion outranks one that merely irritates. Send findings to the team ranked, not as an undifferentiated list.
Heuristic evaluation: the 10 principles
Before testing with users, an expert review against established principles catches a large share of problems quickly and cheaply. Nielsen's 10 usability heuristics are the standard checklist: 3
- Visibility of system status. Keep users informed about what is happening. An order that moves visibly through "received → prepared → shipped" removes the need to ask.
- Match between the system and the real world. Speak the user's language rather than internal jargon. Banking apps that label a transfer the way customers describe it, not the way the ledger does, are applying this.
- User control and freedom. Give people an exit from a state they entered by accident — the "Undo" that appears after deleting an email is the canonical example.
- Consistency and standards. The same action should look and behave the same everywhere. A save button that is green on one screen and blue in a different position on the next forces relearning.
- Error prevention. Better than a good error message is a design that makes the error impossible. Showing password rules while the field is being typed prevents the failure instead of reporting it.
- Recognition rather than recall. Do not make users remember information across screens. Showing recent orders on the home screen turns a memory task into a recognition task.
- Flexibility and efficiency of use. Serve both the novice and the expert. Keyboard shortcuts are invisible to a beginner and indispensable to a daily user.
- Aesthetic and minimalist design. Every extra element competes for attention with the ones that matter.
- Help users recognise, diagnose and recover from errors. "Error code5002-B" tells the user nothing. "The card number you entered is not valid — please check and try again" tells them what happened and what to do.
- Help and documentation. Ideally unnecessary, but when needed it must be findable and task-focused.
Heuristic evaluation does not replace testing with real users. It removes the obvious problems so that testing time is spent on the ones no expert would have predicted.
Frequently asked questions
How is usability different from accessibility?
Accessibility asks whether people with disabilities can use the product at all; usability asks how well anyone can use it. They overlap heavily — most accessibility improvements raise usability for everyone — but a product can be technically accessible and still be difficult to use.
Is five users really enough?
Five is enough to find most problems in one round, not to prove a statistic. 2 If you need quantitative confidence — a completion rate you can report as a number — you need a larger sample. For finding and fixing problems, small and repeated beats large and one-off.
Can you test usability without a finished product?
Yes, and it is cheaper to. Paper sketches and clickable prototypes reveal navigation and labelling problems long before anything is built, which is exactly when those problems are least expensive to fix.
What should we measure?
Start with task completion rate, time on task and error rate. These three map directly onto the components above and are readable by people outside the design team, which matters when you need the fix prioritised.
Who should run the test?
Someone who did not design the thing being tested. Designers unconsciously guide participants past the exact friction the test exists to find. If that is unavoidable, at minimum write the scenarios in advance and read them verbatim.
Last updated:
