What usability testing actually is
You have an idea for a product.
You have not written code yet, and you are wondering whether to test it with real people first.
But it is not a magic validation ritual, and it cannot answer every question you have about your idea.
This guide explains what usability testing is and when it makes sense before building.
It also covers what testing can and cannot prove, and how to run a simple task-based session on a prototype.
Usability testing is an observational research method.
A facilitator asks a participant to perform realistic tasks, usually with a specific interface, and watches what the participant does while listening for feedback.
The core elements are simple: a facilitator, a set of tasks, and a participant, as described in NN/g’s usability testing overview.
Goals vary by study, but they usually include identifying problems in a design and uncovering opportunities to improve.
Teams also aim to learn about the target user's behavior and preferences.
NN/g is blunt about why this matters: even the best UX designers cannot design a good experience without iterative design driven by observations of real users.
The number of variables in an interface and in human behavior is enormous.
Notice what this definition does not include.
Usability testing is not an opinion survey, a focus group, or a request for people to say whether they like your idea.
It is about watching someone try to do something and seeing where they struggle.
When testing before building makes sense
Usability testing before development is most useful when you can represent the core of your idea without writing production code.
That usually means one of these situations:
- You have sketches, wireframes, or a clickable prototype of the main flow.
- You have a landing page or a mockup of a key screen, and you want to see whether people understand what it offers and what they would do next.
- You are choosing between two or three different approaches to the same task and need evidence about which one people can actually use.
The design-thinking framing NN/g describes supports this: teams prototype quickly and put the prototype in front of real users.
They then return to their understanding of the user afterward.