You are not your user. The faster you accept this, the better your product will be.
1Observational Research
Don't listen to what users say they like. Watch what they do. If a user says 'It's great!' but takes 10 minutes to find the checkout button, the design has failed.
2Mental Models
Users bring their past experiences to your app. If they expect a 'search bar' to be at the top right because every other app does it, and you put it at the bottom, you've broken their mental model.
3Iterative Testing
Don't wait for the final product. Test the low-fidelity wireframes. It's much cheaper to change a box in a drawing than to change a feature in a finished codebase.
4Step-by-Step Breakdown
Usability Testing is the practice of testing how easy a design is to use with a group of representative users. It's about finding 'Where' they get stuck.
The 'Think-Aloud' protocol: Ask users to verbalize their thoughts as they navigate the product. This reveals the 'Why' behind their actions.
Be a silent observer. Don't help the user. If they get stuck, ask 'What are you trying to do right now?' or 'What do you expect to happen?'.
When conducting a usability test, what should you do if a user asks 'How do I do this?'
- →Tell them exactly how to do it
- →Say 'I can't tell you' and move to the next task
- →Answer with a question like 'What would you try to do in this situation?' to understand their mental model
- →End the test immediately
According to Jakob Nielsen, how many users are usually enough to find 85% of usability problems?
- →1
- →5
- →50
- →100
Level Up 🚀
Advanced cheat sheets, SEO tricks, and interview prep for this topic.
Browser Support
Fully supported.
Fully supported.
Fully supported.
Fully supported.
Accessibility (A11y)
1Recruit Beyond the 'Easy' Users
Usability panels sourced only from tech-savvy, able-bodied volunteers miss the friction that screen-reader users, older adults, or people on slow connections actually hit. A representative panel should include participants who use assistive technology.
// Wrong
Recruiting: 5 users, all under 35, all fluent with the product category.
// Right
Recruiting: 5 users spanning age ranges and at least one who relies on a screen reader or keyboard-only navigation.SEO Implications
- 1
'How-To' Queries Convert to Practitioners
Searches like 'how many users do I need for usability testing' or 'think aloud protocol examples' are practitioner queries with strong dwell-time potential. Including a concrete moderator script snippet keeps readers on the page longer, which correlates with better rankings.
Best Practices
Write the Script Before the Session
Draft your task scenarios and neutral prompts ('What are you trying to do right now?') in advance. Improvising during a live session risks accidentally leading the participant.
Test Early Prototypes, Not Just Finished Screens
A clickable low-fidelity wireframe surfaces the same navigation and mental-model problems as a polished UI, at a fraction of the cost to fix.
Frequent Bugs
The moderator jumps in to help the moment a participant hesitates, which erases the exact friction the test was designed to find.
Set a personal rule to wait at least 10-15 seconds of silence before speaking, and when you do speak, respond with a question ('What would you try next?') instead of an answer.
Real-World Examples
Recovering a Stuck Participant Without Biasing Results
A participant can't find the settings menu and starts getting visibly frustrated during a moderated session.
Participant: 'I don't know where to go for this.'
Moderator (wrong): 'Try the gear icon in the top right.'
Moderator (right): 'What would you expect to click on to change that?'