Skip to content
BENIBIX Learn

UX Metrics and SUS

Level 3 · Making sense of research

How to put numbers on how easy a product is. The share who finish, the time it takes, a score after each task, and a survey of ten lines.

Course contentsLesson 12 of 21

After this lesson you can

  • Work out a task success rate
  • Score the System Usability Scale
  • Ask the Single Ease Question

11 mincovers 4 glossary entries

Worth reading first: User Personas and Scenarios

How to put numbers on ease of use

UX measures put numbers on how easy a product is. The best known is the System Usability Scale, or SUS. It is a survey of 10 lines, each answered on a five point scale. The answers add up to one score from 0 to 100. The average across many products is about 68.

A SUS score is not a percentage. A 68 does not mean 68 in 100 people are happy. It means the product is about average. Scores above 80 are rare and good. Scores under 50 mean people struggle. Its strength is that you can compare two versions, or two products.

Task success rate is the share of test users who finish a task. If 8 of 10 people book a table, the rate is 80 in 100. Decide what counts as success before the test. Did they book the right time, or any time? Without that rule, people argue later.

Time on task is how long a person takes to finish one task. Shorter is usually better, but not always. A shop may want people to linger over products. Compare the same task across two designs, and only count people who finished.

The Single Ease Question is asked right after each task. How easy or hard was that? People answer from 1, very hard, to 7, very easy. It takes five seconds. A task that scores low while others score high tells you exactly where to look.

Numbers need more people than finding problems does. Five users can show you the big problems. A success rate from five users swings wildly: one person changes it by 20 points. For numbers you can quote, plan on 20 or more people per design.

The common mistake is to measure without a baseline. A SUS of 72 sounds good. But was the old version 80? Measure before you change anything, then again after. The change is the result, not the single number.

One score out of 100, eight of ten people done, and a shorter bar for the new design. Three ways to count ease.

Four ways to measure ease

MetricHow it is measuredExample
System Usability Scale10-line survey, score 0 to 100A score of 72
Task success rateShare who finish a task8 of 10 people
Time on taskSeconds to finish95 seconds, down from 140
Single Ease QuestionOne rating from 1 to 7An average of 5.8

Worked example

A council form before and after

A council's parking permit form scored 54 on SUS with 25 residents. Only 15 of 25 finished it.

After a redesign, a new group of 25 scored it 76, and 22 finished. Average time fell from 6 minutes to 3.

The words for this lesson4

Check yourself

A product scores 68 on the System Usability Scale. What does that mean?

Finished this lesson?

Marking it complete also marks its 4 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.