What it is
A technique where users interact with what looks like a working system, but a hidden human (’the wizard’) generates the responses, letting you test experiences (especially AI or automation) before building the underlying technology.
When to use it
During Prototype, when the backend is expensive or unbuilt but you need real user reactions to the experience.
Why (value)
Tests demand and interaction for complex or automated systems without building them, saving major investment on unvalidated concepts.
How to run it
- Define the experience and the wizard’s rules.
- Build a convincing front-end facade.
- Have users interact while the hidden wizard responds.
- Observe reactions and behavior.
- Decide whether to build the real system.
Inputs and outputs
- Inputs: A front-end facade, a trained wizard, participants.
- Outputs: Behavioral feedback on an unbuilt system.
Time and effort
Medium. Setup plus sessions.
Evidence and limitations
Behavioral, but a proxy: responses come from a human, not the real system, so it validates desirability and interaction, not technical performance. Be careful not to overpromise capability. See Evidence and limitations.
Tips and pitfalls
- Script the wizard so behavior is consistent.
- Keep the illusion intact during sessions.
- Use it especially for AI/automation concepts.
Variations
Wizard-of-Oz for conversational UI, concierge MVPs.
Related methods
Need help planning research or facilitating this method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Paper prototyping — Test interactions with hand-drawn screens before building anything digital.
- Concept testing — Put an early idea in front of users to gauge value and comprehension before building it.
- Usability testing — Watch representative users attempt real tasks to find where the design helps or gets in their way.
