In this guide
A small usability test is simple: you give a person a task, watch them try, and write down where they hesitate or fail. With around five people you will usually see the same big problems repeat. That is the point: repetition tells you a problem is not a one-off.
What it can tell you
- Where people get stuck, misread a label or miss a button.
- Which problems repeat across people (likely to affect many users).
- Which wording or flow confuses someone who has never seen your app.
What it cannot tell you
- How often a problem occurs in your whole user base. Five people give no percentages.
- Which version performs better in numbers. That needs a different method.
- Rare problems. A bug on one device model may not show up.
- What people would pay for or whether they will return later.
Treat the result as a list of likely problems, not as proof. I am not giving a formula for "the right number": it depends on how different your users are and how many separate problems your app has. If your five people come from very different groups, run a round per group.
Plan
- Pick 3-5 tasks that matter most. Example: "Create an account", "Add your first item", "Find the settings".
- Choose five people who resemble your users and have not seen the app.
- Write the task as a goal, not steps. "You want to remind yourself to drink water" rather than "Tap Add".
- Watch, do not help. Ask them to think aloud. If they ask "is this right?" reply "What would you do if I were not here?"
- Note each stumble in the sheet below.
Note sheet
| Person | Task | Did they finish? | Where they hesitated | Their words | Device |
|---|---|---|---|---|---|
| P1 | yes / no / with help |
After the sessions
Count how many people hit each problem. Fix the ones that blocked a core task first, then rerun with a new group to see whether the fix worked. Sort the remainder with how to prioritize app feedback.
Remote and written options
You do not have to sit next to someone. Compare options in moderated vs unmoderated testing. A short form with a clear structure helps for the written kind: see in-app feedback form design.
AppReviewX gives you private, structured feedback from other developers on your app; one feedback you write earns one credit. Start free.
Hub: app feedback guide.