Usability Testing Add/remove
Purpose:
Usability testing of a design, product or service can be used in two cases: Either to explore the problems of an existing product, or to test one or more developed solutions. Even though developers have a large insight in users’ needs, the only way to create truly human-centered design is to test with real end-users. This way, the developer becomes aware of problems with a design, can find ways to improve it, and lastly learn about users’ preferences.
Tips to include participants who are not able to:
Hold
Ask the test person if recording the session is okay to be able to remember insights better.
Touch
Ask the test person if recording the session is okay to be able to remember insights better.
Move
Ask the test person if recording the session is okay to be able to remember insights better.
Speak
Hear
See
Focus
Think
Overview
Input
A solution
Output
Information on solution problems, user preferences and behaviors
Complexity
Moderate
Time
1-2 hours
Participants
min. 2
Activity
Core abilities:
- Communicating
- Observing
- Writing
Step by step:
Determine the goals for the design, product or service. This could be done through a product development specification (PDS) or like. Use the template above to plan the test.
Recruit participants! Always keep in mind that participants must be fitting the target group of your solution. Using people that are just available, like friends and family, can skew the results and cause your solution to move in the wrong direction, away from your real end-users.
Now, decide which of the following types of usability tests you want to use:
- A usability test can be performed as a think-aloud test, where the participant is given a task, and tries to solves it while saying out loud, what they are doing. The test responsibles note down the participants comments as well as their behavior. In this type of test, the participant gets room to interact and investigate your design in their own speed.
- The usability test can also be conducted as a type of interview, with a combination of instructions and questions. One test responsible should note down the participants answers and another should look at their behavior. In this type of test, the test responsible is more visible and has more room to guide and get insights on participants’ thoughts, frustrations, etc.
Make the instructions and/or questions for the test participants. It is important that the instructions/questions reflect the goal of your test. Remember to plan breaks if the test is exhaustive.
Make an introduction for the participants. This could be used during participant recruitment, or in the beginning of the test, to make sure participants know what they agree to. Ideas for the introduction could be to:
- address the aim of the test
- explain about the steps and length of the test
- inform that they can stop the test of withdraw their contribution at any time
Use the template for writing down answers and insights when performing the usability test.
When doing this method you should consider:
- It is possible, with permission of the participant, to record the session, to be able to watch the test several times. This way, you might be able to uncover more and more insights from the test.
- It is important not to let the participant feel stupid or inadequate. This can cause the participant to give up on the provided task. Make sure to encourage the participant, but do not force them to complete the task, if they have tried their best.
- It is always a great idea to perform a pilot test! Find the method for ‘Pilot testing’ before conducting the usability test on real users.
Materials needed:
- Usability test plan (template)
- Pens
- The solution you want to test (prototype or final product)
- Optional: Microphone/camera
