Design Thinking Methods Catalogue

# Prototype

# Wizard of Oz prototype

Purpose
Test functionalities before they exist
Time required
From 1 hour to 1 day
Participants
Design Thinking team, Users
Level of experience
experienced

# What is it about?

Wizard of Oz prototypes allow you to test functionalities that have not yet been implemented. The user only tests a simulation of the actual functionality. Instead of the real functionality, the "Wizard of Oz" pulls the strings in the background.

# The goal

The aim of the method is to save time and money and instead to first proof, which functionalities are necessary.

# How to do it?

  1. Determine which functionality should be tested.
  2. Consider how you can realistically simulate this functionality.
  3. You can combine different tools such as tablets, email systems and PowerPoint with human intervention.
  4. Run the tests and observe the behavior of the users carefully.

# When do you need it?

Wizard of Oz prototypes are often used for the simulation of digital systems.

# Resources

  • various (digital) tools for the creation of the prototype

# Advantages

The Wizard of Oz method enables a realistic interaction between subjects and the autonomous system. This test procedure is cost-effective and agile, and the context of the investigation can be expanded at will.

# Disadvantages

Involving and training a wizard is an additional resource cost and sometimes difficult for wizards to provide consistent responses across the sessions. That's mostly because playing the wizard can be exhausting, meaning the wizard’s reaction may change over time, mainly due to cognitive fatigue. If a research member plays the role of wizard, there is a risk that they will improvise beyond the programmed behavior.

# Keep in mind

Testing with the Wizard of Oz prototypes is more useful, when the test situation feels natural to the test user.

# See also

Previous methods Alternative methods Following methods

# Sources

← User tests →