# System Usability Scale \(SUS\)

The System Usability Scale is a standardized ten-item questionnaire that produces a perceived-usability score from 0 to 100.

- Type: metric
- Domain: Data, experimentation & growth
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/system-usability-scale/>)

## What it means

The System Usability Scale is a ten-statement questionnaire introduced by John Brooke for a quick assessment of perceived usability. Respondents use a five-position agreement scale, and item responses are transformed and combined into a score from 0 to 100.

## Why it matters

SUS is short, technology-agnostic, and widely used, making it practical for repeated studies and benchmarking. It captures a participant’s overall perception after use and can complement observed measures such as task success, errors, and completion time.

## When to use it

Use SUS after participants have had enough direct experience with a system or prototype to judge it. It is useful in benchmark studies, iterative usability tests, and comparative evaluations when administration, scoring, language, and participant populations remain consistent.

## How it works

1. Have participants use the system before answering, and administer all ten items in their established alternating positive and negative form.
2. For each odd-numbered item, subtract one from the response value; for each even-numbered item, subtract the response value from five.
3. Add the adjusted item values and multiply the sum by 2.5 to produce a score from 0 to 100.
4. Summarize the distribution and uncertainty, and compare only with relevant benchmarks or prior studies using compatible conditions.
5. Interpret SUS alongside qualitative findings and behavioral measures rather than as a diagnosis of specific interface problems.

## A practical example

A team asks participants to complete account setup and a first transfer, then administers SUS. The new flow scores higher than the previous benchmark, but task observations reveal persistent confusion about transfer timing. The team reports both findings and fixes the timing language rather than treating the aggregate score as sufficient.

## Where it breaks

A SUS score is not a percentage and does not identify the cause of usability problems. Small or unrepresentative samples create uncertainty, while translations, altered wording, incomplete product exposure, and different study contexts can weaken comparisons. Positive change does not prove business impact.

## Common mistakes

- Interpreting a score of 80 as 80 percent usable.
- Changing or dropping items without acknowledging loss of comparability.
- Using SUS alone instead of pairing it with observed behavior and qualitative evidence.

## Sources

1. [SUS: A Quick and Dirty Usability Scale](<https://doi.org/10.1201/9781498710411-35>) — CRC Press · Original book chapter
2. [SUS: A quick and dirty usability scale](<https://digital.ahrq.gov/sites/default/files/docs/survey/systemusabilityscale%2528sus%2529_comp%255B1%255D.pdf>) — Agency for Healthcare Research and Quality · Government-hosted original paper
3. [Measuring Usability with the System Usability Scale](<https://measuringu.com/sus/>) — MeasuringU · Research practice guide

## Related topics

- [Task Success Rate](<https://wiki.soroush.uk/topic/task-success-rate/>)
- [Time on Task](<https://wiki.soroush.uk/topic/time-on-task/>)
- [HEART Framework](<https://wiki.soroush.uk/topic/heart-framework/>)
