In short
- Definition: The ease with which the intended users can learn and use a system effectively, efficiently and with satisfaction.
- Goal: Let users reach their goals quickly, with few errors and a good experience.
- Example S.M.A.R.T. requirement: A System Usability Scale score above 75, and new users completing the main task in under 3 minutes.
1. Definition
As a non-functional requirement, usability describes how easily the intended users can learn and use a system to reach their goals effectively, efficiently and with satisfaction.
If users need a manual to do the main task, the design has failed the requirement.Key takeaway
ISO/IEC 25010 treats usability as a product quality characteristic, and Nielsen Norman Group summarizes it as how easily people can complete tasks with a design [1], [2]. It always depends on who the users are, what they are trying to do and in what context.
Usability is measured, not argued: usability tests with representative users, task success rates, time on task, error counts and standard questionnaires such as the System Usability Scale (SUS) [3], [4].
2. Goal
The goal is to let users reach their goals quickly, with few errors and a good experience.
Poor usability shows up as training costs, support tickets, workarounds, abandoned tasks and lost customers.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| System Usability Scale score | 0–100 | ≥ 75 | SUS questionnaire after test |
| Task success rate | % of key tasks | ≥ 90% | Moderated usability test |
| Time on main task | Minutes (new user) | < 3 | Usability test |
| Errors per task | Count | ≤ 1 | Usability test |
Across hundreds of studies, the average SUS score is 68, so a target of 75 or more means clearly above average.
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Satisfaction: “The application shall reach a System Usability Scale score of at least 75 with representative users.”
- Efficiency: “New users shall complete the main task in under 3 minutes without help.”
- Effectiveness: “At least 90% of test participants shall complete each key task successfully on their first attempt.”
5. Questions to Ask Stakeholders
- Who are the main user groups and their context?
- Which tasks matter most?
- Which usability targets reflect success?
- When and how often will usability tests run?
- How many participants per round?
- How will findings be prioritized and fixed?
6. Common Pitfalls
- “User-friendly” as a requirement. It cannot be tested; give measurable targets.
- Testing only at the end. Test early and repeatedly, even with prototypes.
- Testing with the team. Developers are not representative users.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Accessibility — usable by people with disabilities.
- Training — easy systems need less training.
- Emotional Factors — how users feel while using the system.
- Response Time — slow screens hurt usability.
8. FAQ
A 10-item questionnaire giving a score from 0 to 100; 68 is the average across many studies.
Small rounds of about five users, repeated, find most major problems at low cost.
Usability is part of user experience, which also covers emotions, brand and the whole journey.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| ISO | International Organization for Standardization | Independent international body that publishes standards, such as ISO/IEC 25010 for software quality. Its short name comes from the Greek “isos” (equal) and is said as a word. | [5] |
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [6] |
| SUS | System Usability Scale | Ten-question survey that produces a usability score from 0 to 100. | [4] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [7] |
| IEC | International Electrotechnical Commission | International standards body for electrical and electronic technologies; it publishes joint “ISO/IEC” standards with ISO. | [8] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [9] |
| UX | User experience | Everything a person experiences when using a product: ease, emotions, and the whole journey. | [10] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [11] |
10. Sources and Further Reading
- [1] “Usability 101: Introduction to Usability.” Nielsen Norman Group. https://www.nngroup.com/articles/usability-101-introduction-to-usability/ (accessed Nov. 18, 2026).
- [2] “ISO/IEC 25010.” ISO 25000. https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 (accessed Nov. 18, 2026).
- [3] “Measuring Usability with the System Usability Scale (SUS).” MeasuringU. https://measuringu.com/sus/ (accessed Nov. 18, 2026).
- [4] “System usability scale.” Wikipedia. https://en.wikipedia.org/wiki/System_usability_scale (accessed Nov. 18, 2026).
- [5] “International Organization for Standardization.” Wikipedia. https://en.wikipedia.org/wiki/International_Organization_for_Standardization (accessed Nov. 19, 2026).
- [6] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [7] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [8] “International Electrotechnical Commission.” Wikipedia. https://en.wikipedia.org/wiki/International_Electrotechnical_Commission (accessed Nov. 19, 2026).
- [9] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 19, 2026).
- [10] “User experience.” Wikipedia. https://en.wikipedia.org/wiki/User_experience (accessed Nov. 19, 2026).
- [11] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @halacious; inline photo by @amayli, both on Unsplash.








