Definition
Your team has built a prototype for reporting overflowing bins. You know exactly how it works. But can someone who has never seen it use it without your help?
User testing means watching real people try to complete a task with a prototype, without help from its makers. The makers note where users get stuck, change the design and test the same task again. It finds problems the makers cannot see, because they already know how the prototype works.
In simple words
When you explain the way to your house, it always sounds clear to you, because you already know the way. A visitor is the one who finds the confusing turn. Letting someone else test your prototype is like asking that visitor to find the house alone.
Why it matters
Makers are the worst testers of their own designs: they know which button to press and what each word means. A short test with a fresh user shows the real problems, and fixing them before presenting makes a project far more useful. In 2000 the usability expert Jakob Nielsen wrote that testing with about five users reveals most of a design's problems, so even a few testers help.
Key terms
- Prototype
- An early, simple version of a product, made to test an idea.
- User testing
- Watching people use a prototype to do a real task, to find problems.
- Task
- One specific thing the tester tries to do, such as 'report the full bin near the park gate'.
- Think aloud
- Asking the tester to say what they are thinking while they use the prototype.
- Iteration
- Changing the design and testing again, repeating until the task is easy.
Explained in detail
Set up a fair test
Choose one clear task that a real user would want to do, such as 'Report the full bin near the park gate.' Give the tester the task in writing and nothing else: no tour and no hints. Ask them to think aloud. Your job is to watch and take notes, staying quiet even when they struggle. If you jump in to help, you lose the very information you came to collect. Note where they hesitate, what they tap or click first, any word they misunderstand and how long the task takes.
Notes that lead to changes
| What you saw | What it suggests | Possible change |
|---|---|---|
| The tester looks for a 'Report' button and misses one labelled 'Submit data' | The label uses your words, not theirs | Rename it 'Report a full bin' |
| The tester doesn't know how to mark the place | The location step is unclear | Add 'Use my location' and a small map |
| The tester asks, 'Did it work?' | No confirmation is shown | Show 'Thank you, your report was sent' |
Change, then test the same task again
After the test, choose the most serious problem and change the design. Then ask a new tester, or the same one, to do exactly the same task. Compare: did they finish? How long did it take? Did they need help? If the task is now easy, move on to the next problem. Repeating this loop a few times, called iteration, is how good designers work, and it is part of design thinking.
Respect your tester
Make it clear that you are testing the prototype, not the person: if they get stuck, the design is at fault. Thank them, and do not record their face or voice without permission. A tester's confusion is a gift, because it shows you exactly what to fix before your real users meet the same problem.
Testing early saves work. A paper sketch can be tested in five minutes, long before anything is built, and changing a drawing is far easier than changing a finished app. Many teams test after every important change, so that each small fix is checked before the next one is made, and they keep a short log of what each test showed.
How it works
- Write one clear task that a real user would do.
- Give the tester the task and ask them to think aloud.
- Watch silently and note where they hesitate, misunderstand or get stuck.
- Change the design to fix the biggest problem.
- Test the same task again and compare.
Worked example
Team Swachh's prototype lets residents report overflowing bins. Their tester, who had never seen it, was given the task 'Report the full bin near the park gate.' She looked for a 'Report' button, missed the one labelled 'Submit data' and needed help after two minutes. The team renamed the button 'Report a full bin' and added 'Use my location' and a thank-you message. A second tester did the same task alone in under a minute.
Try it yourself
Watching a user test
Follow one silent test and the change it led to.
Run a user test
Put the steps in order.
- 1Give the task to a tester who hasn't seen the prototype
- 2Change the design
- 3Test the same task again
- 4Write one clear task
- 5Note where they get stuck
- 6Watch silently while they think aloud
A new case: a library app on paper
Work with a partner.
- Draw three screens of a paper prototype for borrowing a library book.
- Ask your partner to borrow a book using only your drawings, while you stay silent and take notes.
- Write one problem you saw, change the drawing and test the same task again.
Think about it
- Was it hard to stay silent? What would you have hidden if you had helped?
Common mistakes
- Helping the tester instead of watching, which hides the problem.
- Testing with a teammate who already knows the design.
- Changing many things at once and not testing the same task again.
Check yourself
Summary
- Let someone who has never seen your prototype try a real task while you watch silently.
- Note where they hesitate or get stuck, and change the design to fix the biggest problem.
- Test the same task again to prove the change helped, and repeat: that is iteration.
Finished reading?
Sources: Jakob Nielsen · Why you only need to test with 5 users (2000)