Design Thinking Methods Catalogue

# Test

# User tests

Purpose
Testing the prototype with users
Time required
Design Thinking team, users
Participants
Depending on prototype
Level of experience
Expert

# What is it about?

The aim of the classic user test is to let selected users test a previously created prototype and use the findings for further development.

# The goal

In the course of user tests, the development team is able to identify weaknesses and potentials of the prototype from the user's point of view.

# How to do it?

  1. Show the user the prototype without explaining it.
  2. Only explain the context he needs in order to understand what he is doing.
  3. Let the user tell what he is doing while testing the prototype (thinking out loud).
  4. Watch the user's actions carefully but don't interfere.
  5. Ask the user important questions such as "How do you feel about it?" or "Would you use this feature and if so why or why not?

# When do you need it?

User tests should be carried out several times with prototypes of different maturity levels.

# Resources

  • Prototype
  • Pen and paper

# Advantages

The knowledge gained during a user test is very high. The problems found in a user test correspond with a high probability to difficulties in use in a real context.

# Disadvantages

The effort involved in a user test is very high, both during preparation and evaluation. In addition, the results can be influenced by the experiment leader or the observer and the participants show a desired rather than an actual behaviour. Often results obtained in a laboratory setting are only applicable to the real environment to a limited extent. Furthermore, only a part of the interactive system or individual use cases can be evaluated in a user test.

# Keep in mind

User tests are more useful in a natural test situation.

# See also

Previous methods Alternative methods
    		Following methods

    # Sources

    ← Test Capture Grid →