Skip to content
Kuza Ndoto Academy

Test: Learning from Users

All levelsChapter 3 · Page 12 of 293 min readUpdated 15 Nov 2026

The test mode is where you put prototypes in front of real users, watch what happens and learn. Testing is not about proving you were right; it is about discovering what works, what confuses people and what to change next.

What to test

Every test should answer specific questions. They usually fall into three groups:

Question typeExampleHow to check
DesirabilityDo people want this? Would they use it again?Reactions, follow-up use, willingness to pay or sign up
UsabilityCan people use it without help?Task success, time taken, where they get stuck
ValueDoes it actually solve the problem?Before-and-after comparison, user stories

Running a usability test

  1. Recruit the right people: users who match your persona, not your friends from class (unless they are the target users).
  2. Give a realistic task, not instructions. Say "Record that Peter owes you KES 200 for tomatoes", not "Tap the plus button".
  3. Ask them to think aloud: "Please say what you're thinking as you go." This is called the think-aloud method.
  4. Stay quiet and observe. Resist helping. Where someone struggles is exactly what you need to see.
  5. Note what they do, not just what they say. Hesitations, wrong taps and confused faces are data.
  6. Debrief: ask what they liked, what was confusing and what they would change.

Usability expert Jakob Nielsen has argued that testing with around five users per round reveals most of the major usability problems, so several small rounds teach more than one big test. Treat this as a rule of thumb; desirability and value questions often need more people and real-world use over time.

Capturing feedback

A simple feedback capture grid helps you organise what you hear during or after each session:

LikesCriticisms
What users enjoyed or found usefulWhat frustrated or confused them
QuestionsIdeas
What users asked or wondered aboutSuggestions from users or new ideas the session gave you

From feedback to iteration

After a round of tests, look for patterns. One user's complaint might be personal taste; the same complaint from four out of five users is a signal. Decide for each finding:

  • Fix: clear usability problems with obvious solutions.
  • Explore: surprising reactions that need more empathy work.
  • Rethink: evidence that the core idea does not meet the need. This may send you back to define or ideate.

Then update the prototype and test again. Each loop should be faster and more focused than the last.

Example

Wanjiku and Ali built a clickable mock-up of a clinic queue app for a health centre in Machakos. They asked five patients to "book a slot for tomorrow morning" while thinking aloud. Four of the five could not find the booking button because it was labelled "Reserve". Three asked whether they would get an SMS reminder. Two older patients said they would prefer to book by phone call. The team renamed the button "Book a visit", added SMS confirmations and started exploring a USSD option for basic phones. In the second round, all five patients completed the booking in under a minute.

Testing etiquette and ethics

  • Explain what you are testing and that it is the prototype being tested, not the person.
  • Ask permission before taking photos or recordings, and store notes safely.
  • Respect people's time; a soda, airtime or a small thank-you is a kind gesture.
  • Never collect more personal data than you need.
Common mistake

Defending your prototype when users struggle ("No, you just have to tap here!"). Every explanation you give hides a problem real users will face alone. Another mistake is asking only "Do you like it?"; people tend to say yes to be polite. Watch behaviour and ask about specifics instead.

Key points

  • Test prototypes with real target users to learn about desirability, usability and value.
  • Give realistic tasks, ask users to think aloud and observe without helping.
  • Several small rounds (around five users each, as a rule of thumb) beat one large test for usability.
  • Look for patterns, then fix, explore or rethink, and iterate.
Up next · New chapter: Validation & Business ModelsCustomer DiscoveryInterview customers to test your assumptions.
→

Tip: use the ← and → keys to move between pages.