Usability testing: methods, questions, and examples
Usability Testing
✓ see where real users get stuck
On this page
Usability testing is a UX research method that evaluates how easily people can complete tasks using a product. By observing representative users as they interact with a prototype or live experience, teams can identify usability issues, improve workflows, and make evidence-based design decisions before launch.
This guide explains the main types of usability testing, when to use each method, the metrics worth tracking, how to run a usability test, and where AI-moderated sessions fit into modern UX research.
TL;DR
Usability testing helps teams understand how real users interact with a product by observing them as they complete realistic tasks. The goal is to identify usability issues, reduce friction, and improve the user experience before or after launch.
An effective usability test includes:
- Clearly defined research objectives
- Representative participants
- Realistic task scenarios
- Metrics such as task success rate, time on task, error rate, and the System Usability Scale (SUS)
- Actionable findings that guide product improvements
Usability testing can be conducted in moderated, unmoderated, remote, in-person, or AI-moderated formats depending on your research goals.
What is usability testing?
Usability testing is a UX research method that evaluates how people interact with a product by asking them to complete specific tasks while researchers observe. It helps measure how intuitive an interface is, identify areas of friction, and uncover opportunities to improve the overall user experience.
Rather than confirming that a design works as intended, usability testing reveals where users hesitate, become confused, or fail to complete important tasks. Identifying these issues early allows teams to make improvements before investing additional time and development resources.
Why usability testing matters
Usability testing helps teams identify issues before they affect customers, making it easier to improve the user experience while reducing the cost of future changes.
- A better user experience. Observing real users helps uncover usability issues that may not be obvious during design or internal reviews.
- Higher satisfaction and retention. Products that are easier to understand and navigate are more likely to meet user expectations and encourage continued engagement.
- Lower development costs. Resolving usability issues during design or prototyping is generally faster and less expensive than making changes after launch.
- Measurable business impact. Nielsen Norman Group has found that investing roughly 10% of a project's budget in usability activities can improve conversion, task completion, and user productivity.
Organizations that incorporate usability testing into their regular product development process are often able to identify issues earlier and iterate more efficiently. For example, ServiceNow reduced participant recruitment time from 118 days to six after consolidating its research tools, making research a more consistent part of product development.
Types of usability testing
Usability testing methods vary depending on the research question, product stage, and type of feedback you're looking to collect. Most studies combine multiple approaches to answer different research questions.
Type | What it is | Best for |
|---|---|---|
| Qualitative | Observing how users behave and asking why to understand the experience | Understanding user behavior and design issues |
| Quantitative | Measuring task success, completion time, error rates, and satisfaction | Benchmarking performance and measuring improvements |
| Moderated | A facilitator guides participants and asks follow-up questions in real time | Complex workflows and exploratory research |
| Unmoderated | Participants complete tasks independently while sessions are recorded | Scaling research across larger participant groups |
| AI-moderated | An AI facilitator guides sessions and asks adaptive follow-up questions | Combining moderated-style depth with greater scalability |
| Prototype testing | Testing an early version of a product before it's complete | Identifying design issues early |
| Card sorting | Participants organize content into logical categories | Improving information architecture |
| Tree testing | Participants navigate a site's structure to locate information | Validating navigation and information architecture |
Qualitative vs quantitative usability testing
Qualitative usability testing focuses on understanding why users behave the way they do. Researchers observe participants completing tasks, ask follow-up questions, and explore the reasoning behind their decisions. These insights often reveal usability issues that wouldn't be apparent from metrics alone.
Quantitative usability testing focuses on measurable outcomes such as task completion rates, time on task, error rates, and satisfaction scores. These metrics make it easier to benchmark usability over time and evaluate whether design changes have improved the experience.
The two approaches are most effective when used together. Quantitative research identifies where problems occur, while qualitative research helps explain why they happen.
Moderated vs unmoderated usability testing
Moderated usability testing is conducted with a facilitator who guides participants through tasks and asks follow-up questions in real time. This approach is particularly valuable for complex user journeys or exploratory research where unexpected behaviors often generate the most meaningful insights.
Unmoderated usability testing allows participants to complete tasks independently while their screen, audio, and interactions are recorded for later review. Because sessions don't require live facilitation, this method scales more easily across larger participant groups and geographic locations. The trade-off is that researchers cannot ask clarifying questions during the session, making well-designed tasks and instructions especially important.
Remote vs in-person usability testing
Usability testing can be conducted either remotely or in person, regardless of whether the study is moderated or unmoderated.
In-person testing allows researchers to observe body language, facial expressions, and other nonverbal cues that may provide additional context during a session. It typically requires more coordination and resources but can be valuable for complex or high-stakes studies.
Remote testing allows participants to complete sessions using their own devices in their normal environments. This approach is generally faster to schedule, supports geographically distributed participants, and reflects how people naturally interact with a product.
In-person | Remote | |
|---|---|---|
| What you can observe | Body language, facial expressions, and other nonverbal cues | How people use the product on their own devices, in their normal environments |
| Setup | Typically requires more coordination and resources | Generally faster to schedule |
| Best for | Complex or high-stakes studies | Geographically distributed participants |
AI-moderated usability sessions
AI has introduced a new approach that combines aspects of moderated and unmoderated usability testing.
An AI facilitator guides participants through tasks, asks follow-up questions, and adapts to participant responses in real time. This allows teams to collect richer qualitative feedback while maintaining the speed and scalability of unmoderated research.
AI moderation works well for asking follow-up questions, conducting large numbers of sessions, and maintaining consistency across studies. Researchers still play an essential role in designing tasks, interpreting findings, and determining which insights should influence product decisions.
Great Question's AI Moderation conducts AI-moderated sessions and automatically organizes participant feedback into themes, linking each finding to the supporting transcript or recording. This helps researchers review evidence efficiently while keeping moderated and unmoderated studies together in a single research repository.
Other methods worth knowing
Prototype testing evaluates an early version of a product before development is complete, allowing teams to identify usability issues while changes are still relatively inexpensive.
Card sorting helps researchers understand how users naturally organize information by asking participants to group content into categories. Results are commonly used to improve information architecture and navigation.
Tree testing, sometimes called reverse card sorting, evaluates whether users can successfully navigate a site's structure to locate information. It is often used alongside card sorting to validate information architecture decisions.
How to run a usability test
Usability testing doesn't require a complex setup to produce valuable insights. Following a structured process helps ensure consistent results and makes findings easier to act on.
- Set the goal and pick the method. Start by defining what you want to learn. Your research objective should determine the testing method. Can new users complete the sign-up process without assistance? Use a task-based moderated or unmoderated usability test. Do navigation labels make sense to users? Consider card sorting or tree testing. Choosing the right method begins with identifying the research question.
- Recruit the right participants. Recruit participants who closely match your target audience based on characteristics such as role, experience level, or familiarity with similar products. Participants can come from your existing customer base or external recruitment panels. Offering a small incentive can help improve both participation rates and engagement.
- Write realistic tasks. Create task scenarios that reflect real user goals without revealing how to complete them. Things like “Purchase a pair of running shoes in your size” is good. Try to avoid things like “Click the green ‘Add to Cart’ button.” Include a brief introduction, consent information, task instructions, and a few follow-up questions at the end of the session.
- Run a pilot. Test your study with one or two participants before launching the full research project. Pilot sessions help identify unclear task wording, broken prototype links, or confusing instructions, allowing you to make adjustments before collecting larger amounts of data.
- Conduct the sessions. Observe participants as they complete each task without providing assistance unless the study requires it. For moderated studies, encourage participants to think aloud while completing tasks, then ask follow-up questions after each task to avoid influencing their natural behavior. Record observations and note where participants hesitate, backtrack, or encounter errors.
- Analyze and share. Review participant observations, identify recurring patterns, and prioritize issues based on their impact on the user experience. Share findings with stakeholders in a concise, actionable format that clearly explains what should change and why. Storing sessions, notes, and research findings in a centralized repository also makes future research easier to reference and build upon.
Usability testing metrics to track
Observations explain why usability issues occur. Metrics help measure how often they occur and whether design changes improve the experience over time.
Key usability metrics include:
Metric | What it measures |
|---|---|
| Task success rate | The percentage of participants who successfully complete a task. This is one of the clearest indicators of whether a workflow is effective. |
| Time on task | The amount of time participants need to complete a task. Longer completion times can indicate friction, although results should always be interpreted alongside other metrics. |
| Error rate | The frequency of incorrect actions, such as selecting the wrong option or entering information in the wrong field. Repeated errors often highlight usability problems within an interface. |
| System Usability Scale (SUS) | A standardized 10-question survey that produces a usability score from 0 to 100. A score of approximately 68 is generally considered average, making SUS useful for benchmarking usability over time. |
| Satisfaction ratings | Simple post-task ratings, such as a 1-to-5 ease-of-use scale, help capture participants' perceptions of the overall experience. |
Select the metrics that best align with your research objectives and use them consistently across studies to track changes over time.
Usability testing questions to ask
Usability studies typically combine open-ended and closed-ended questions to collect both qualitative and quantitative feedback.
Open-ended questions
Open-ended questions encourage participants to explain their experiences in their own words.
- What was your experience using this feature?
- What did you expect to happen when you clicked that?
- How would you improve the navigation?
- Which parts of the experience were most and least satisfying?
- What would make you more likely to use this regularly?
Closed-ended questions
Closed-ended questions provide consistent responses that are easier to compare across participants.
- On a scale of 1 to 5, how satisfied are you with this feature?
- Would you describe this task as easy, moderate, or difficult?
- Would you recommend this app to a colleague? (Yes/No)
- How often do you run into issues using this product? (Rarely / Occasionally / Frequently)
- Which feature was most useful: A, B, or C?
Related reading
Rating scales, the more points the merrier? by Thomas Stokes, UXR consultant and principal at Drill Bit Labs.
Usability testing examples and use cases
Website usability testing
A retail company evaluates its e-commerce website by asking participants to browse products, add items to a cart, and complete checkout. Observing where shoppers hesitate helps identify opportunities to improve navigation, search, and the checkout experience.
Mobile app usability testing
A fitness app team tests workout tracking and meal-planning features with both new and existing users. Researchers observe participants completing common tasks, identifying navigation issues and areas where onboarding can be improved.
Software usability testing
A business software company evaluates its messaging and task management features with participants who regularly use similar tools. Observing how users complete common workflows helps identify inefficiencies and prioritize interface improvements.
The bottom line
Usability testing helps teams understand how people actually interact with a product, making it easier to identify friction, validate design decisions, and improve the user experience before and after launch.
As Nielsen Norman Group's Kate Moran puts it:
“The only way to get UX design right is to test it.”
The most effective teams treat usability testing as an ongoing part of product development rather than a one-time milestone. Testing early and regularly helps uncover issues sooner, evaluate design changes, and continuously improve the user experience. While AI-moderated sessions and automated analysis can make research faster and easier to scale, interpreting findings and making product decisions still depends on human judgment.
Great Question's UX research platform brings participant recruitment, scheduling, moderated and AI-moderated sessions, and analysis together in one place, helping teams conduct usability research from start to finish without switching between multiple tools.
Frequently asked questions
Why is usability testing important?
Usability testing shows you how real people use your product, not how you assume they will. By watching users and collecting their feedback, you can find and fix problems that make a product harder to use, which improves satisfaction, retention, and conversion.
When should you do usability testing?
Throughout development, from early design through launch and beyond. It's worth testing whenever you make a significant change or add a feature. Testing early and often means you catch problems while they're still cheap to fix.
How many participants do you need for a usability test?
For qualitative testing, about five participants per user type will surface most of the common issues, a guideline Nielsen Norman Group popularized as the “rule of five.” If you need statistically reliable numbers, aim for at least 20 users. More participants uncover more problems, but depth of observation usually beats raw sample size for design decisions.
How do you recruit participants for usability testing?
Find people who closely match your real users. You can recruit from your own customer base, use a participant panel, or work with a recruiting partner, screening on the traits that matter for your product. Recruiting from customers you already have is usually the fastest route and gets you people who genuinely use products like yours.
What tools do you need for usability testing?
At a minimum, a way to recruit and schedule participants, run or record the session, and analyze what you see. Teams often stitch these together from separate tools, which is where studies get slow and messy. For a rundown of options, see our guide to the best usability testing tools. Running the whole study on a single UX research platform removes the handoffs between recruiting, sessions, and analysis.
How do you analyze usability test results?
Review what participants did and said, group similar observations, and look for issues that show up across multiple people rather than one-off reactions. Rank the problems by severity, then turn the top ones into specific, actionable recommendations. AI theme-clustering can speed up the grouping, but a human should still decide which findings actually matter.
