How to use UXScore

This page covers what SUS is, how UXScore scores it, and practical guidance so you get usable results.

What is SUS?

System Usability Scale (SUS) is a standard 10-question survey that produces a single usability score from 0 to 100.

It’s popular because it’s:

Participants answer 10 questions on a 1–5 scale.

SUS scoring converts those answers into a 0–100 score:

UXScore computes and stores a per-response SUS score, and reports the average for the run.

It depends what you’re using SUS for:

Directional signal (fast feedback): ~8–12 responses can be enough to spot big issues.
More stable comparison between runs: ~20+ responses is a solid baseline.
Benchmarking / finer-grained confidence: 50+ is better, especially if your audience is diverse.

Practical advice: start small to validate the flow, then keep collecting until the score stops swinging wildly with each new response.

SUS is most meaningful when participants resemble real users of the product you’re testing.

If you change the product (new UI, new flow), create a new run so you can compare runs cleanly.

Depending on the scale of your application and audience, you might create a new run with each sprint or minor release.

The average score is useful, but pay attention to:

Big variance (some love it, some hate it)
Consistent dips on specific questions (per-question averages will be added in a future build)

Mixing different audiences in one run (e.g., beginners + power users)
Changing the product mid-run without creating a new run
Treating SUS as a “final verdict” instead of a signal
Over-optimising the number (“gamifying” the score) instead of fixing usability issues