Skip to content

User Testing

In a user test you test if your product is usable by the user. Often you test for a specific feature of your product. A good test follows a test plan, has users perform a number of tasks, and registers results to see what works and what needs to be improved. You register results by asking for feedback,and measure quantitative results.

ISO Definition of Quality

For testing user experience, the ISO definition of quality in use is often used.

β€œQuality in use is the degree to which a product or system can be used by specific users to meet their needs to achieve specific goals with effectiveness, efficiency, freedom from risk and satisfaction in specific contexts of use.” ISO/IEC 25010:2011(en)

Effectiveness

Effectiveness here refers to the degree to which the user can achieve their goal, for example, do they make mistakes, and can they complete the task?

Examples of how to measure effectiveness: * Number of people who have accomplished the goal * Number of steps completed correctly * Number of mistakes made * Number of times help/tips/suggestions were needed

Efficiency

Efficiency concerns how quickly the user can achieve their goal. This can be measured by looking at how many clicks they need or by keeping track of time.

Examples of how to measure efficiency: * Time taken to accomplish the goal * Time taken to complete steps * Number of clicks required to accomplish the goal * Number of clicks required to complete steps

Satisfaction

"Satisfaction" refers to how satisfied the user is with the product. This can be measured by having a questionnaire filled out or by conducting an interview. You can also assess it qualitatively using closed-ended questions (yes/no) and survey scales (e.g., Likert scale).

Guerrilla Test

A Guerrilla test is a super-fast way of testing. All you need is: 1. a prototype (for example, a sketch, storyboard, wireflow, wireframe, or digital prototype) or an MVP (a minimal but working coded application) 2. a test goal (which specific functionality or interaction do you want to test?) 3. at least 5 test participants

Prodcedure

  • Keep it short! About 5 minutes per tester, maximum 10 minutes.
  • Provide as little help as possible; if your testers make mistakes, this is valuable feedback!
  • Ask your users to think out loud; this way, you gain insight into their thought process.
  • Document the feedback and turn it into User Stories.
  • Tip: Bring snacks; your test participants will appreciate it!
Google over Guerilla testing

Note: This page was created with the assistance of (ChatGPT)[https://chat.openai.com].