Usability Test Guide
A Usability Test Guide is a structured document that outlines the key questions, topics, and areas of exploration for conducting usability tests on software products or features, ensuring consistency and depth in the data collection process.
Purpose
The purpose of a Usability Test Guide is to provide a standardised approach to evaluating the usability of a product or feature. It ensures consistent, objective assessment of user interaction and satisfaction, leading to actionable insights for improving the overall user experience.
Format
Evaluating Usability
To assess how easily and effectively users can use the prototype to accomplish their goals. Focus on identifying usability issues and opportunities for improvement.
| Usability Aspect | Description |
|---|---|
| Learnability | How easy it is for users to accomplish basic tasks the first time they encounter the design. |
| Efficiency | Once users have learned the design, how quickly can they perform tasks? |
| Error Rate | How many errors do users make, how severe are these errors, and how easily can they recover from the errors? |
| Satisfaction | How pleasant is it to use the design? |
| Memorability | When users return to the design after a period of not using it, how easily can they re-establish proficiency? |
| Accessibility | How easily can users with disabilities access and use the design? |
Assessing Desirability
Understanding whether the prototype appeals to users' needs, preferences, and expectations. Focus on the emotional and social dimensions of the user experience.
| Desirability Aspect | Description |
|---|---|
| Appeal | The initial attraction to the feature. Does it catch the user's interest? Is it something they are interested in? |
| Perceived Usefulness | The user's subjective anticipation of the product's ability to fulfill their needs before actual use. |
| Emotional Connection | The emotional response elicited by the prototype. Does it make users feel confident, happy, etc.? |
| Social Influence | The prototype's potential to affect the user's social image. Would users be proud to share or recommend it? |
Anti-patterns
| Leading Participants: Asking leading questions or guiding participants too much, influencing their actions and feedback. | Ignoring Silent Feedback: Focusing only on what participants say and ignoring non-verbal cues or actions that indicate usability issues. | Confirmation Bias: Interpreting user feedback in a way that confirms pre-existing beliefs about the product's usability. |
|---|