Marcus Andrey Study
Ler em português Library

Framework · Measurement · 3 min read

SUS

The System Usability Scale: a standard 10-item questionnaire scored 0–100, where about 68 is average, so you can compare an app's perceived usability with its own past and with published data.

10Ten items

Five-point agreement scale, 1 Strongly disagree to 5 Strongly agree.

Use the standard wording
1Odd items

Positive statements. Contribution is the answer minus 1.

Items 1, 3, 5, 7, 9
2Even items

Negative statements. Contribution is 5 minus the answer.

Items 2, 4, 6, 8, 10
%Score

Sum of contributions (0–40) times 2.5 gives 0–100.

About 68 is average

SUS = (sum of odd items − 5 + 25 − sum of even items) × 2.5

SUS turns ten 5-point answers into one 0–100 score; it is not a percentage, and about 68 is average.

Use it when

  • You want one standard usability score per app, measured once or twice a year.
  • You need to show whether a redesign changed how usable people find an app.
  • You are building a Happiness metric for a HEART framework table.

How to use it

  1. Use the ten standard items. Ask all ten statements in the original order, on a 5-point scale from 1 = Strongly disagree to 5 = Strongly agree. You may replace "system" with the app name. Ask after people have used the app, not before. Output: a survey with the ten items.
  2. Score the odd items. Items 1, 3, 5, 7 and 9 are positive. For each, the contribution is the answer minus 1. Output: five numbers from 0 to 4.
  3. Score the even items. Items 2, 4, 6, 8 and 10 are negative. For each, the contribution is 5 minus the answer. Output: five numbers from 0 to 4.
  4. Add and multiply by 2.5. Add the ten contributions (0–40) and multiply by 2.5 to get a score from 0 to 100 per person. Then average across people. Output: one SUS score per app.
  5. Compare. Compare with your own last round first. For outside reference, Jeff Sauro's analysis of about 500 studies puts the average at about 68. Output: score, change from baseline, and position against 68.
  6. Follow up with qual. SUS tells you how usable people find the app, not why. Add an open question or a few interviews. Output: reasons behind the score.

Worked example

One operator's answers on an internal booking tool:

Item 1 2 3 4 5 6 7 8 9 10
Answer 4 2 4 1 3 2 5 2 4 3
Contribution 3 3 3 4 2 3 4 3 3 2

Odd items: (4+4+3+5+4) − 5 = 15. Even items: 25 − (2+1+2+2+3) = 15. Total 30 × 2.5 = 75. The team averages the scores of 18 respondents to get the app's score and compares it with last year's.

The same operator's answers as in the table above. Change any answer and watch the score update. The scoring runs in your browser; nothing is sent anywhere.

Watch out for

  • Reading it as a percentage. 75 doesn't mean "75% usable". Compare with 68 and with your own baseline.
  • Changing the items. Dropping items, rewording them or using a different scale breaks comparison with published data.
  • Forgetting to reverse the even items. Summing raw answers gives a wrong score. Use the scoring rule or a checked spreadsheet.
  • Scoring single items. SUS is valid as a total score. Don't report item 3 alone as "ease of use".

Template

Copy these standard items into your survey tool. Keep the order and the 1–5 scale.

1 = Strongly disagree ... 5 = Strongly agree

 1. I think that I would like to use this system frequently.
 2. I found the system unnecessarily complex.
 3. I thought the system was easy to use.
 4. I think that I would need the support of a technical person to be able to use this system.
 5. I found the various functions in this system were well integrated.
 6. I thought there was too much inconsistency in this system.
 7. I would imagine that most people would learn to use this system very quickly.
 8. I found the system very cumbersome to use.
 9. I felt very confident using the system.
10. I needed to learn a lot of things before I could get going with this system.

Score per person = ((sum of odd answers - 5) + (25 - sum of even answers)) x 2.5
Source
John Brooke (1986; published 1996)
Where to find it
UX Lead Course: Module 9: UX Maturity & Measurement › Standard UX measures
UX Design Foundations: Defining success
UX Research: Measuring usability

"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close