Home › Glossary › UX· 429 ·

Usability Testing

yoo-zuh-bil-i-tee tes-tingnoun

Filed underUXAnalytics

In brief · quick answer

Usability testing is the practice of observing real users as they attempt to complete tasks with a product, identifyin g where they struggle, and using those insights to improve the design.

§ 1 Definition

Usability testing is a research method where real users attempt to complete predefined tasks on a product while researchers observe and record their behavior, errors, confusion, and feedback. Unlike asking users what they want (which often produces unreliable data), usability testing shows what users actually do. The goal is to identify usability problems, measure task completion rates and time, and gather qualitative insights that inform design improvements. Usability testing can be conducted in person or remotely, moderated or unmoderated, and at any stage of the design process from early prototypes to live products.

§ 2 Moderated vs Unmoderated Testing

Moderated testing involves a researcher guiding the participant through tasks, asking follow-up questions, and observing reactions in real time. It produces rich qualitative data and allows the researcher to probe when users show confusion. Unmoderated testing uses a tool (UserTesting, Maze, Lookback) to present tasks and record the session without a live moderator. It scales better (more participants, less researcher time) but yields less depth. Both are valuable. Use moderated testing early to discover why users struggle, and unmoderated testing later to validate fixes with a larger sample.

§ 3 How Many Participants Do You Need?

The famous Nielsen Norman Group finding: testing with 5 participants per user group uncovers approximately 85% of usability problems. Additional participants tend to reveal the same issues already found. The key is to run multiple small rounds of testing (test with 5, fix issues, test again) rather than one large test. One round of 5 participants per tested segment is the minimum. For quantitative metrics (task time, completion rate), you need larger sample sizes (20+ per segment).

§ 4 What Usability Testing Measures

Task success rate (did the user complete the task?), time on task (how long did it take?), error rate (how many mistakes did the user make?), satisfaction (how did the user feel about the experience?), and findability (could the user locate the information or feature?). These metrics form the baseline for measuring improvement. A framework like SUS (System Usability Scale) provides a standardized satisfaction score that can be compared across products and versions.

§ 5 Note

Always pilot-test your usability test script with one internal participant to catch confusing wording or technical issues before testing with real users.

§ 6 Common questions

Q. Can usability testing replace analytics?: A. No. They provide different information. Analytics tell you what users did (where they clicked, where they dropped off). Usability testing tells you why they did it (they were confused, could not find the button, did not understand the label). You need both for a complete picture.
Q. How early can you start usability testing?: A. As soon as you have something interactive, even if it is paper prototypes or a low-fidelity Figma prototype. Testing early with rough prototypes catches structural problems before they are embedded in visual design and code. The cost of fixing an issue found in a paper prototype is minutes. The cost of fixing the same issue in production code is days or weeks.

Key takeaways

Usability testing observes real users completing real tasks to identify problems.
Moderated testing gives rich qualitative insights. Unmoderated testing scales better.
5 participants per user segment finds approximately 85% of usability issues.
Run multiple small rounds (test, fix, test again) rather than one large test.
Test early with prototypes, not just with finished products.

How Atomic Glue helps

We run usability tests at every stage: from 5-user guerrilla tests to full moderated studies. Data drives every design decision. See our Creative Services or get in touch.

Get in touch

# Usability Testing

Usability testing is the practice of observing real users as they attempt to complete tasks with a product, identifyin g where they struggle, and using those insights to improve the design.

Category: UX (also: Analytics)

Author: Atomic Glue Editorial Team

## Definition

## Moderated vs Unmoderated Testing

## How Many Participants Do You Need?

## What Usability Testing Measures

## Note

Always pilot-test your usability test script with one internal participant to catch confusing wording or technical issues before testing with real users.

## Common questions

Q: Can usability testing replace analytics?

A: No. They provide different information. Analytics tell you what users did (where they clicked, where they dropped off). Usability testing tells you why they did it (they were confused, could not find the button, did not understand the label). You need both for a complete picture.

Q: How early can you start usability testing?

A: As soon as you have something interactive, even if it is paper prototypes or a low-fidelity Figma prototype. Testing early with rough prototypes catches structural problems before they are embedded in visual design and code. The cost of fixing an issue found in a paper prototype is minutes. The cost of fixing the same issue in production code is days or weeks.

## Key takeaways

Usability testing observes real users completing real tasks to identify problems.
Moderated testing gives rich qualitative insights. Unmoderated testing scales better.
5 participants per user segment finds approximately 85% of usability issues.
Run multiple small rounds (test, fix, test again) rather than one large test.
Test early with prototypes, not just with finished products.

## Related entries

Last updated July 2026. Permalink: atomicglue.co/glossary/usability-testing