What is usability testing?
Usability testing means watching real people try to complete real tasks with your product, to find out where it confuses or blocks them.
The critical word is watching. People are unreliable narrators of their own behaviour. Someone who struggled for four minutes will often say the flow was fine, because they got there in the end and do not want to seem slow.
Types of usability testing
- Moderated. A facilitator is present and can ask why. Richer, slower, and vulnerable to the facilitator leading the participant.
- Unmoderated. The participant works alone while their screen is recorded. Faster and cheaper, and you cannot ask follow-up questions.
- Remote or in person. Remote is now the default and loses body language.
- Comparative. Two designs, same task, measuring which performs better.
How many testers do you need?
Five is the number most often quoted, from research showing five participants surface the large majority of usability problems in a given design. It holds reasonably well for one user group and one flow.
It stops holding when you have distinct user groups. Five admins and five end users is not the same as ten people, because they hit different problems.
How to run a usability test
Write tasks, not instructions. “Find out how much your team would pay per month” is a task. “Click pricing, then select the team plan” is a script that tests nothing.
Say nothing while they work. The silence is uncomfortable and it is where the findings are.
Watch for hesitation, not just failure. A pause before clicking is a usability problem even when they click correctly.
Ask afterwards, not during. Questions mid-task change the behaviour you are measuring.
What usability testing does not tell you
It tells you whether people can use the thing. It does not tell you whether they want it. A flawlessly usable feature nobody needs still fails, and usability testing will report it as a success.
That question belongs to product discovery, and running usability tests instead of discovery is a common and expensive substitution.
How Usersnap supports usability testing
Participants report problems as they hit them, in the product, without stopping to describe what they saw. Annotated screenshots and screen recordings capture the moment, and browser, operating system and console data arrive attached. For unmoderated sessions this matters most, because there is no facilitator to reconstruct what happened. Findings land alongside acceptance testing reports and general feedback rather than in a separate document.
Usability testing FAQ
How many people do you need for usability testing?
Around five per distinct user group and per flow. Five surfaces most problems in one design for one audience, and separate groups need their own five.
What is the difference between usability testing and user acceptance testing?
Usability testing asks whether people can use it, usually before release, on a design. Acceptance testing asks whether it does the job the business needs, usually just before go-live.
What is the difference between moderated and unmoderated testing?
Moderated has a facilitator present who can ask follow-up questions. Unmoderated records the participant working alone, which is faster and cheaper but loses the ability to ask why.
Capture what testers saw, not what they remember. Start free with Usersnap, first 20 feedback items included, no card needed.
.svg)
