methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session2-10 daysWorkshop or asyncPrototype Learnings

Session: Wizard of Oz Test

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 5-20 Nutzer. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Prototype Learnings. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Define experience and script

    Setup, 1-2 days

    Describe the experience as end-to-end flow. Define typical requests and answers per step. Set SLA, tone, and escalation path. Hint: If the script does not cover 70% of requests on day one, the experience is too broad. Narrow scope.

    FacilitatorPrototype Learnings
  2. 2

    Phase 2: Frontend and wizard setup

    Setup, 1-3 days

    Build frontend (chat, form, app stub). Wizard dashboard with incoming request queue. Shift plan for wizards. Test with 2-3 internal participants. Hint: Wizards need script training. Live improvisation creates inconsistent experience.

    FacilitatorManual Effort Notes
  3. 3

    Phase 3: Live with real test users

    Runtime, 5-7 days

    Invite test users. Wizards work shifts and keep SLA. UX researcher observes patterns. Daily wizard sync for consistency. Hint: If SLA breaks, learning is distorted. Fewer users with stable experience beat many users with chaos.

    FacilitatorRisk List
  4. 4

    Phase 4: Disclosure and analysis

    Synthesis, 1-2 days

    After test end, disclose manual involvement. Interview or survey users. Analyze logs: frequent requests, wizard effort per request, escalated cases. Hint: Disclosure is an ethical duty, not optional.

    OwnerPrototype Learnings
  5. 5

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerPrototype Learnings
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Wizard of Oz Test

Goal

Artifact: Prototype Learnings

Working Question

Does the simulated automatic experience deliver recognizable value to users, and which tasks are realistically automatable?

Context

Experience to test in one sentence; SLA expectation; script for typical requests; escalation rule for unclear cases; disclosure about manual involvement after the test.

Setup

  • Format: Method session
  • Duration: 2-10 days
  • Mode: Workshop or async
  • Participants: One test owner defining experience and coordinating wizards; two to five wizards manually responding; UX researcher for observation; test users.
  • Owner: One test owner defining experience and coordinating wizards
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Prototype Learnings. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Working frontend prototype (click dummy or simple web frontend); backend scripts or manual operators (wizards); logging setup; SLA plan for response times; ethical briefing for test participants.

Preparation

Build frontend so requests go to a wizard channel. Wizards work in shifts with clear response rules. Log all requests and responses. Inform users after the test about manual involvement.

Agenda

  1. Phase 1: Define experience and script (Setup, 1-2 days) Owner: Facilitator Action: Describe the experience as end-to-end flow. Define typical requests and answers per step. Set SLA, tone, and escalation path. Hint: If the script does not cover 70% of requests on day one, the experience is too broad. Narrow scope. Output: Prototype Learnings

  2. Phase 2: Frontend and wizard setup (Setup, 1-3 days) Owner: Facilitator Action: Build frontend (chat, form, app stub). Wizard dashboard with incoming request queue. Shift plan for wizards. Test with 2-3 internal participants. Hint: Wizards need script training. Live improvisation creates inconsistent experience. Output: Manual Effort Notes

  3. Phase 3: Live with real test users (Runtime, 5-7 days) Owner: Facilitator Action: Invite test users. Wizards work shifts and keep SLA. UX researcher observes patterns. Daily wizard sync for consistency. Hint: If SLA breaks, learning is distorted. Fewer users with stable experience beat many users with chaos. Output: Risk List

  4. Phase 4: Disclosure and analysis (Synthesis, 1-2 days) Owner: Owner Action: After test end, disclose manual involvement. Interview or survey users. Analyze logs: frequent requests, wizard effort per request, escalated cases. Hint: Disclosure is an ethical duty, not optional. Output: Prototype Learnings

  5. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Prototype Learnings

Closeout

  • Update result artifact: Prototype Learnings
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Prototype Learnings: Wizard of Oz Test

Working Question

Does the simulated automatic experience deliver recognizable value to users, and which tasks are realistically automatable?

Context

Experience to test in one sentence; SLA expectation; script for typical requests; escalation rule for unclear cases; disclosure about manual involvement after the test.

Participants

  • Owner: One test owner defining experience and coordinating wizards
  • Participants: One test owner defining experience and coordinating wizards; two to five wizards manually responding; UX researcher for observation; test users.

Input

Working frontend prototype (click dummy or simple web frontend); backend scripts or manual operators (wizards); logging setup; SLA plan for response times; ethical briefing for test participants.

Template

Wizard of Oz Test Working Template

Goal

Manually simulates automated product behavior behind the scenes.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Prototype Learnings:
  • Manual Effort Notes:
  • Risk List:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Completion Check

  • Prototype Learnings is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Wizard of Oz Test Working Template

View templateCompact working template for Wizard of Oz Test with context, input, output artifacts, and next step.
markdown

wizard-of-oz-test-working-template.md

Compact working template for Wizard of Oz Test with context, input, output artifacts, and next step.

Wizard of Oz Test Working Template

Goal

Manually simulates automated product behavior behind the scenes.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Prototype Learnings:
  • Manual Effort Notes:
  • Risk List:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Prototype Learnings.
  • Own report per iteration with date, scope, and wizard setup. Document script updates as delta.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet