What is user testing in UX?
User testing in UX is the practice of watching real people try to use a product or prototype, to find out what works and what confuses them.
also calledusability testing · user testing session · product testing
You have stared at your design for weeks, so you can no longer see it. Hand it to a stranger, say nothing, and watch where their cursor goes. In about five minutes you will learn things your whole team missed, most of them humbling and all of them useful.
- Watch real people attempt realistic tasks, and stay quiet while they do.
- Five to eight participants per round will reveal most major problems.
- Write tasks as goals and avoid leading questions.
- Test early, fix the worst issues, then test again.
What happens in a session
A participant gets a realistic task, such as "Find a flight to Lisbon next month and add a bag". They try it on a prototype or live product while you observe and, usually, ask them to think aloud. You stay quiet when possible. If they get stuck, that is the finding, not a cue to help.
Afterwards you ask a few follow-up questions, then you compare notes across participants. Patterns matter more than any one comment: if four of five people miss the same button, you do not need a debate.
Moderated, unmoderated, remote and in person
In a moderated test, a researcher guides the session, either face to face or over a video call, and can ask follow-up questions. In an unmoderated test, participants complete tasks on their own time, usually recorded through a testing platform. Moderated sessions go deeper, unmoderated ones are quicker and cheaper at scale.
In-person sessions let you read body language. Remote ones let you reach people in their normal environment and on their own devices. Neither is better in general. Pick based on your question, your budget and who you need to reach.
Running a test, step by step
- Decide what you want to learn and write it as a clear question.
- Choose participants who resemble real users. Five to eight per round is often enough to spot the biggest problems.
- Write tasks as goals, not instructions. "You want to change your delivery address" beats "Click Settings".
- Run a pilot with a colleague to catch broken tasks.
- Observe, take notes and resist helping.
- Group the problems by severity and fix the worst ones first.
- Test again after changes to confirm they worked.
User testing versus usability testing
The terms overlap heavily and many teams use them interchangeably. When people draw a line, usability testing is the narrower idea: measuring how easily people complete tasks. User testing can include wider questions as well, like whether a concept is appealing or a feature is wanted.
If somebody asks for "user testing", spend a minute clarifying what they want to learn, since that determines the method.
Mistakes that spoil the results
Leading questions are the worst. "Isn't this menu easy to use?" will get you politely agreeable answers. Testing with friends is the next. They want to be kind. Others include testing too late, so that findings land after the build is done, and treating a single comment as a law. And remember that people are not always right about why they struggled, so watch what they do as well as what they say.
User testing: your questions, answered
What is user testing in UX?
It is a research method in which real people use a product, prototype or concept while you observe. The goal is to spot confusion, errors and unmet needs so that you can fix them before or after launch.
How many users do you need for user testing?
For qualitative tests, five to eight participants per round usually reveal the most serious usability problems. Running several small rounds is generally better than one large test, because you can fix issues in between and check the improvements.
When should you do user testing?
As early and as often as you can. Test rough sketches, then prototypes, then the built product. Early tests are cheap and catch big structural problems, while later ones catch details such as wording and small interaction issues.
How much does user testing cost?
It ranges from almost nothing, such as testing with a few recruited volunteers, to substantial sums for large studies with specialized recruitment. Your main costs are participant incentives, tools and the time to plan and analyze sessions.
What is the difference between user testing and A/B testing?
User testing observes a small number of people to understand why they struggle. A/B testing measures how large numbers of users behave in two versions of a live product. The first explains problems, the second measures outcomes.
More quick answers
What is the difference between user testing and usability testing?
They are often used as synonyms. Usability testing focuses specifically on ease of use, while user testing can also cover appeal and desirability.
Should you pay participants?
Usually yes. A fair incentive respects their time and improves attendance.
Can you do user testing without a finished product?
Yes. Paper sketches and clickable prototypes work well, and finding problems at that stage is cheaper.
What does think-aloud mean?
It means asking participants to say what they are thinking while they use the product, which exposes expectations and confusion.
How is user testing different from user research?
User research is the umbrella for learning about users, including interviews and surveys. User testing is one method inside it, focused on evaluating a design.
Usability testing in UX is a method where you watch real people try to complete realistic tasks with a product to find where they struggle.
User research in UX is the practice of studying people who use or might use a product, to understand their needs and behavior so design rests on evidence.
A/B testing in UX means showing two versions of a design to different groups of users and measuring which one gets the better result.
Beta testing in UX is releasing a nearly finished product to a limited group of real users to find bugs and usability problems before the full launch.
A prototype in UX is an early, interactive model of a product that lets you test how it works and feels before spending time building the real thing.
Qualitative user research is the study of people's behavior, needs and motivations through observation and conversation, to learn why they act as they do.
Found this useful? A GitHub star helps other designers find it.