Why usability testing matters
Even very good designers can't predict how people will read a screen. Your team knows that "Workspaces" holds billing. A new customer looking for invoices may not.
Watching one person hunt for the export button for two minutes settles arguments that a meeting can't. It also replaces opinions about the design with evidence, which makes prioritising much easier.
How a usability test works
There are three parts: a facilitator, a participant and a set of tasks. The participant should be a realistic user. The tasks should be things they'd actually do, like "You've been charged twice this month. Find out why."
Participants usually think aloud while they work, and the facilitator watches, listens and asks follow-up questions without steering. Task wording matters more than people expect, because a task that mentions the button label gives the answer away. GOV.UK's Service Manual puts a typical moderated session at 30 to 60 minutes.
How many participants a usability test needs
For a qualitative study of one user group, Nielsen Norman Group recommends five participants. Jakob Nielsen's model suggests five users reveal most of the problems, and that after the fifth you mostly see the same issues again.
The point is to test, fix and test again. Three rounds of five beat one round of fifteen. Quantitative studies that measure task success or time on task are different and need far more people.
Usability testing vs user acceptance testing
User acceptance testing checks that the software meets its agreed requirements before release. Usability testing checks whether people can actually use it to do what they came for.
A feature can pass acceptance testing and still fail usability testing. The button works, the data saves, and nobody can find the button.
How Gr8r approaches usability testing
Our UX audit is an expert review, not a usability test, and we're clear about that difference. When an audit raises a question only real users can answer, we flag it and suggest the tasks worth testing.
In product design work, we recommend testing the riskiest flows with a handful of representative users. Doing it before build is when changes are still cheap.
Example
A team building an expense app asks five finance managers to "submit last week's taxi receipt for approval" on a clickable prototype. Three of them look for an upload button on the dashboard instead of opening the expenses tab. The team adds a quick action to the dashboard before development starts.
Go deeper on Usability testing
- What Is Product Discovery, and What Should It Hand You?What is product discovery? A plain definition, what you should hold at the end, the stages it moves through, and the habits that keep it short and useful.
- Redesign, Refactor or Rebuild Your SaaS Product?Should you redesign, refactor or rebuild your SaaS product? A plain diagnostic: the symptoms behind each option, the risks, and a quick scoring test.
Reviewed by Tanjim Islam, Founder & CEO · Updated 8 November 2026
Sources
