# User tests
|Motive||Testing the solution with users|
|Participants||Design Thinking team, Users|
|Duration||depending on prototype|
# 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?
- Show the user the prototype without explaining it.
- Only explain the context he needs in order to understand what he is doing.
- Let the user tell what he is doing while testing the prototype (thinking out loud).
- Watch the user's actions carefully but don't interfere.
- 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.
- Pen and paper
# Keep in mind
User tests are more useful in a natural test situation.
# See also
Design Thinking Bootleg. Hasso Plattner Institute of Design at Stanford University.