Purpose
When a new experience would still be too expensive to automate for real, it simulates the outcome behind the scenes. It checks user reaction and value before the technology disappears.
Product Discovery Research method
Wizard of Oz Test
Shows how people use an interaction when missing technology is simulated under controlled conditions.
In a Wizard of Oz Test a person behind the scenes operates functions that appear automated to participants. This tests interaction and value assumptions before building the technology.
How do people use this interaction when the missing technology is simulated under controlled conditions?
- Participants
- 5-20 Nutzer participants
- Time
- 60–90 minutes preparation; 20–40 minutes per session plus debriefing.
Simulation
Simulation
Define hypothesis, visible function and manually simulated scope.
Protocol
Protocol
Prepare operator rules, boundaries, consent and debriefing.
Rehearsal
Rehearsal
Rehearse the facade and operator workflow with normal, failure and boundary cases.
Observation
Observation
Give neutral tasks; log user action, operator action and delay separately.
Debriefing
Debriefing
Explain the manual simulation, collect reactions and bound the findings.
Stabilise operator rules, add new failure cases and assess technical feasibility separately.
A good fit when
For intelligent or adaptive interactions that are difficult to prototype and can be simulated responsibly.
Ideal for
- AI Features
- Service Prototypes
- Automation Ideas
Not good for
- Scalable production
- Tests without ethical transparency
Outputs
Simulation findings
Interaction findings with operator actions, latency, boundaries and debriefing.
Test findings
The test findings record the agreed handling of research data and separate assessments of value, usability, and unresolved automation.
Wizard of Oz Test· worksheet
Fictional example
In a Wizard of Oz Test a person behind the scenes operates functions that appear automated to participants. This tests interaction and value assumptions before building the technology.
Hypothesis and facade
Which interaction and assumption are tested? What is manually simulated?
Fictional: a course assistant suggests classes matching three stated time windows. Hypothesis: people can then choose a suitable option independently. A concealed operator selects from a fixed course list; no real AI exists.
Operator rules and limits
Define response rules, latency, failure cases and manual interventions.
Lea returns at most three matching offers within 20–40 seconds. No match triggers a request for another time window. Unplanned responses are logged as deviations.
Participation and debriefing
What information is needed upfront, which simulation is temporarily concealed, and how is debriefing handled?
Voluntary participation in a research prototype; only fictional scheduling data, human access to inputs disclosed. The exact operator workflow is explained immediately afterwards; withdrawal and agreed deletion are available.
Observation and operator log
Record task, user action, operator action, timing, help and outcome separately.
P02 enters three times; Lea responds after 32 seconds. P02 overlooks location and chooses a time-compatible class at the wrong venue. The moderator explains only after task completion.
Debriefing and learning decision
What was disclosed, how did the person respond and what limits remain?
P02 learns that Lea selected the options. The team adds location comparison and retests. Automated quality, scaling and operating costs are not established by this manual trial.
All example details are fictional and illustrate the application.
First step
Define an interaction hypothesis, simulated scope and acceptable boundaries.
Deep dive
How it works
It presents what looks like finished behavior, while the actual execution happens manually or in a simplified way. This lets product impact be tested without carrying the full technical effort.
In detail
Wizard of Oz Tests hold up because they realistically simulate the user experience while the actual performance is still delivered manually. Good application keeps the manual support invisible without making the behavior artificial or distorting the data. This shows whether a solution principle holds up in everyday use before effort flows into automation or elaborate product engineering.
Facilitation
Define in advance exactly which parts are simulated and which user reactions actually matter for the decision. The format shows its value where manual execution reveals early patterns that make later automation plausible or questionable. Close with a clear separation between observed user value and the internal operating effort of the test setup.
The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Topics
Artifact templates
Wizard of Oz Test: WorksheetDefine an interaction hypothesis, simulated scope and acceptable boundaries.markdown
Wizard of Oz Test: WorksheetDefine an interaction hypothesis, simulated scope and acceptable boundaries.
markdownwizard-of-oz-test-working-template.md
Define an interaction hypothesis, simulated scope and acceptable boundaries.
Wizard of Oz Test: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Complete cycle Time: 60–90 minutes preparation; 20–40 minutes per session plus debriefing.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Facade, operator console, response rules, log.
- Roles: Participants, moderator, concealed operator.
- Advance information: Define an interaction hypothesis, simulated scope and acceptable boundaries.
- Overall time needed: 60–90 minutes preparation; 20–40 minutes per session plus debriefing.
- Setup: Prepare the user interface and operator console separately; display response rules and use shared timestamps in both logs.
Prepare for the work steps
Simulation: Simulation
- Interaction concept
Protocol: Protocol
- Simulation contract and tasks
Rehearsal: Rehearsal
- Protocol and facade
Observation: Observation
- Rehearsed setup
Debriefing: Debriefing
- Logs and conversation
Wizard of Oz Test· worksheet
Hypothesis and facade
Which interaction and assumption are tested? What is manually simulated?
...
Operator rules and limits
Define response rules, latency, failure cases and manual interventions.
...
Participation and debriefing
What information is needed upfront, which simulation is temporarily concealed, and how is debriefing handled?
...
Observation and operator log
Record task, user action, operator action, timing, help and outcome separately.
...
Debriefing and learning decision
What was disclosed, how did the person respond and what limits remain?
...
Answer the prompts with your own information. Explicitly mark unknowns and assumptions.
NN/g: The Wizard of Oz Method in UX
Simulation: Simulation
Expected artifact: Simulation contract
Is it clear which assumption the test can answer?
Entry:
...
- Is it clear which assumption the test can answer?
Protocol: Protocol
Expected artifact: Execution protocol
Are data access, withdrawal and debriefing clear?
Entry:
...
- Are data access, withdrawal and debriefing clear?
Rehearsal: Rehearsal
Expected artifact: Rehearsed setup
Is operation reproducible rather than improvised?
Entry:
...
- Is operation reproducible rather than improvised?
Observation: Observation
Expected artifact: Behaviour log
Is assistance visible as an intervention in the log?
Entry:
...
- Is assistance visible as an intervention in the log?
Debriefing: Debriefing
Expected artifact: Test findings
Have the simulation and its limits been disclosed?
Entry:
...
- Have the simulation and its limits been disclosed?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/wizard-of-oz-test/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Product Discovery
Concierge MVP
Instead of Wizard of Oz Test, choose Concierge MVP when you want to deliver the value manually and get learning signals before automating.
Product Discovery
Pretotyping
Tests a market claim with the smallest fitting precursor and makes real interest measurable.
Product Discovery
MVP Test Matrix
Moves customer problem, solution idea, and evidence toward a concrete result through "list assumptions", "map assumptions to dimensions", and "derive the test plan".
Product Discovery
Problem Interview
Clarifies customer problems, solution ideas, and evidence by framing problem hypotheses, recruiting the target group, and assessing problem risk.
Innovation
Design Sprint
Brings problem space, prototype, and test findings together in a few days, enabling a well-founded decision.
Product Discovery
Assumption Mapping
Sorts assumptions by uncertainty and leverage so the riskiest hypotheses get tested first.
Constraints and origin
HighWorkshop + async2-10 Tage
Profile
- Method form
- Research method
- Participants
- 5-20 Nutzer
- Time
- 2-10 Tage
- Maturity
- Established
- Origin
- Human-Computer Interaction Community
Next up: Usability Testing