metricData, experimentation & growth

System Usability Scale (SUS)

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

Download Markdown (.md)

01What 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.[1][2][3]

02Why 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.

03When 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.

04How 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.

05A practical example

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.

06Where 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.

07Sources

  1. SUS: A Quick and Dirty Usability ScaleCRC Press · Original book chapterSUS: A Quick and Dirty Usability Scale
  2. SUS: A quick and dirty usability scaleAgency for Healthcare Research and Quality · Government-hosted original paperSUS: A quick and dirty usability scale
  3. Measuring Usability with the System Usability ScaleMeasuringU · Research practice guideMeasuring Usability with the System Usability Scale
View saved topics

Start typing to search titles, definitions, categories, and frameworks.