# UX Metrics and SUS

> 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:** [UX Design and Research](https://learn.benibix.com/learn/design-user-experience)  
**Time:** 11 min

**After this lesson you can:**

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

## 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.

![Three panels. A ruler from 0 to 100 with a marker for one System Usability Scale score. Ten small figures, eight with a tick and two with a cross, for task success rate. A stopwatch next to two bars, a short one for the new design and a long one for the old, for time on task.](https://learn.benibix.com/diagrams/des3-ux-metrics.svg)

## Four ways to measure ease

| Metric | How it is measured | Example |
| --- | --- | --- |
| System Usability Scale | 10-line survey, score 0 to 100 | A score of 72 |
| Task success rate | Share who finish a task | 8 of 10 people |
| Time on task | Seconds to finish | 95 seconds, down from 140 |
| Single Ease Question | One rating from 1 to 7 | An average of 5.8 |

### 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.

**Words in this lesson:** [System Usability Scale (SUS)](https://learn.benibix.com/term/design/system-usability-scale), [Task Success Rate](https://learn.benibix.com/term/design/task-success-rate), [Time on Task](https://learn.benibix.com/term/design/time-on-task), [Single Ease Question (SEQ)](https://learn.benibix.com/term/design/single-ease-question)

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

**Answer:** It is about average. A SUS score is not a percentage. Across many products the average is about 68, so this product sits right in the middle.

---

Source: https://learn.benibix.com/learn/design-user-experience/ux-metrics-and-sus
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
