How to run a usability test with five people

Many teams never test their website with real people because it sounds expensive and complicated. It doesn’t have to be. With five people, a video call and an afternoon, you can see exactly where visitors get stuck, and that is worth more than weeks of debate in a meeting room.

Why five people is enough to start#

A well-known rule of thumb from usability research is that a small group finds most of the serious problems. The first person shows you a lot. The second confirms some of it and adds a little more. By the fourth and fifth, you mostly see the same problems again.

That repetition is the point. When three out of five people stumble in the same place, you do not need a statistic to know it matters. Testing with five, fixing, and testing again with five more teaches you far more than one large test.

Decide what you want to learn#

Start with the two or three things your website most needs people to do. Imagine a local bakery that takes cake orders online. Its most important tasks might be:

• Order a birthday cake for this Saturday.
• Find out whether they sell gluten-free bread.
• Check what time the shop closes today.

Keep it to three or four tasks. A session that runs too long tires people out, and tired people stop behaving naturally.

Write goals, not instructions#

The most common mistake is telling people how to do the task. The moment you name the button, you have tested whether they can follow directions, not whether your website makes sense.

Give people a realistic reason and a goal, then let them find their own way. Their route is the finding.

Find five people#

Look for people who resemble your real visitors. They do not need to be experts; they need to be the kind of person who would actually use your site.

• Existing customers are ideal, and often happy to help.
• Friends of friends work well, as long as they don’t know your business.
• Avoid colleagues. They know too much to struggle in the right places.

A small thank-you, such as a voucher or a free product, is polite and makes people more willing. Sessions work perfectly well on a video call with screen sharing.

Run the session#

Each session takes about twenty to thirty minutes. Keep the same structure every time so you can compare what you see.

1. Put them at ease. Explain that you are testing the website, not them, and that nothing they do can be wrong.
2. Ask them to think aloud. “Tell me what you’re looking at and what you expect to happen.”
3. Give one task at a time. Read it out, then stay quiet.
4. Don’t help. If they ask where something is, turn it back gently: “Where would you expect it to be?”
5. Finish with two questions. “What was the hardest part?” and “What would you change?”

Staying quiet while someone struggles is the hardest part of the job. Resist the urge to rescue them. The struggle is exactly what you came to see.

Spot the patterns#

Straight after each session, write down what you saw while it is fresh: where people hesitated, what they clicked first, what they said. Then, once all five are done, put the notes side by side.

• Seen by three or more people: fix these first.
• Seen by one or two: note them, and watch for them next time.
• Stopped someone completely: fix these immediately, however many people hit them.

Use people’s own words when you share the findings. “I thought ‘Order’ meant order history” is more persuasive than any summary you could write.

Fix, then test again#

Make the changes, then run five new sessions. Sometimes a fix works perfectly. Sometimes it reveals the next problem that was hiding behind the first. Either way, you will know, instead of guessing.

A quick checklist#

• Three or four tasks, written as goals rather than instructions.
• Five people who resemble your real visitors.
• Twenty to thirty minutes each, thinking aloud, with no help.
• Notes straight after each session, patterns after all five.
• Fix what several people hit, then test again.