# Usability

Usability is the extent to which specified users can achieve specified goals effectively, efficiently, and satisfactorily in a defined context of use.

- Type: principle
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/usability/>)

## What it means

Usability is an outcome of interaction between particular users, goals, a system, and a context—not a universal property or a synonym for visual simplicity. It is commonly considered through effectiveness, efficiency, and satisfaction, with measures and observations chosen for the task and context.

## Why it matters

A product can contain the required functionality yet remain unusable in practice. Framing usability contextually helps teams define whose success matters, observe real task barriers, compare alternatives, and avoid declaring an interface intuitive without evidence.

## When to use it

Use usability as a quality objective throughout discovery, design, delivery, and monitoring. Define it for representative users and tasks before evaluation. Pair it with accessibility, utility, desirability, safety, and business considerations rather than treating it as the whole user experience.

## How it works

1. Specify the target users, goals, tasks, environments, devices, constraints, and consequences that form the context of use.
2. Define observable effectiveness, efficiency, and satisfaction criteria that match important tasks.
3. Study representative users performing those tasks through formative research and iterative usability testing.
4. Combine behavioral measures with observation and participant perspective to diagnose barriers.
5. Prioritize changes by severity and consequence, then retest in the relevant context.

## A practical example

A hospital evaluates medication ordering with clinicians during realistic interruptions. Completion alone is insufficient: the team measures critical errors, time, recovery, and confidence, then redesigns ambiguous dosage controls and retests under the same conditions.

## Where it breaks

Usability results are context-specific and do not prove usefulness, accessibility, desirability, safety, or market value. Lab studies may miss environmental pressures, satisfaction can diverge from performance, and aggregate metrics can conceal excluded user groups.

## Common mistakes

- Calling a product usable without naming users, goals, or context.
- Equating usability with visual cleanliness or personal preference.
- Measuring satisfaction alone while ignoring task success and errors.
- Treating usability testing as final validation instead of iterative learning.

## Sources

1. [ISO 9241-11:2018 — Usability: Definitions and concepts](<https://www.iso.org/standard/63500.html>) — International Organization for Standardization · Standard
2. [Usability 101: Introduction to Usability](<https://www.nngroup.com/articles/usability-101-introduction-to-usability/>) — Nielsen Norman Group · Professional guidance

## Related topics

- [Usability Testing](<https://wiki.soroush.uk/topic/usability-testing/>)
- [Usability Benchmarking](<https://wiki.soroush.uk/topic/usability-benchmarking/>)
- [Accessibility](<https://wiki.soroush.uk/topic/accessibility/>)
