Skip to main content

How to Run Usability Testing Surveys

You don't need a lab to measure how usable your product is. Here's how to run survey-based usability testing and read the results.

Usability testing sounds like it needs a lab, a facilitator, and a week of scheduling. It doesn't. A short survey, asked at the right moment, gives you a usability score you can track over time and across hundreds of real users.

Here's how to run survey-based usability testing — with two questions that researchers have trusted for decades.


Surveys vs. a lab test — use both, for different jobs

Survey-based usability isn't a replacement for watching real people use your product — it's the other half. Surveys measure how much; lab sessions explain why.

Surveys measure what and how much (cheap, scalable) versus lab tests that explain why (deep, small sample)



The SEQ: one question, right after a task

The Single Ease Question (SEQ) is the simplest usability metric there is. The moment someone finishes a task, ask how easy it felt, on a simple 5-point smiley scale. It's quick, it's proven, and the average score tells you which tasks are causing friction.

Ask it immediately after the task, while the experience is fresh — not at the end of a long questionnaire.


A single ease question using a smiley scale from very difficult to very easy



The SUS: a usability score in ten statements

The System Usability Scale (SUS) is the industry standard for an overall usability score. It's ten short statements, each rated from strongly disagree to strongly agree. A matrix question fits the whole thing on one screen.

System Usability Scale statements shown as a matrix from strongly disagree to strongly agree



Trigger it in the product, right after the task

Where you ask matters as much as what you ask. A short survey that pops up in the product, right after someone completes a task, gets far more (and more honest) responses than an email days later.


An in-app slide-in survey asking how easy the checkout was, right after the task



Reading the score

SUS produces a single number from 0 to 100 — but it's not a percentage. The key benchmark to remember: 68 is the average. Below that is below average; 80 and up is genuinely good.

📈 The real value comes from tracking your own score over time — run the SUS every release and watch whether your changes actually move it.


A SUS score scale from 0 to 100 with the industry average marked at 68 and a score of 78 in the good range



Where to start

  1. Add an SEQ right after your most important task.

  2. Run the SUS as a matrix once per release.

  3. Trigger both in-app, in context, not by email.

  4. Track the scores over time — the trend beats any single number.


💡 A quick start

Survio's matrix and rating questions cover SEQ and SUS out of the box, and you can compare the same survey across releases to see your score move. Pair this with "Feature Prioritization: How to Ask Users What They Actually Want" in this collection.

Did this answer your question?