# Simulate the interaction without pretending the system exists

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Simulate the interaction without pretending the system exists

ID: MHC-D-RESEARCH-1094 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/simulate-the-interaction-without-pretending-the-system-exists

A human behind the prototype is not a production benchmark.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- You need to test a proposed interaction before building its automation.

### Avoid when

- Disclosure may change behavior; concealment introduces ethical issues. Follow an approved research protocol, and never use the prototype for consequential live decisions.

### Explanation

Use a human operator to supply responses while a participant tries a bounded prototype. Explain that parts are simulated and agree what will be recorded. This transparent variant can expose interaction needs without presenting human judgement as an implemented model.

### Steps

1. Specify the task, allowed responses and operator assistance.
2. Run the interaction and log what the operator supplied or repaired.
3. Separate interface findings from capability, reliability and cost questions still untested.

### Example

A speech-practice prototype receives manually prepared feedback. The team records which feedback users understand, not an invented AI accuracy score.

### Check

Can every apparent system capability be traced to implemented behavior or declared human assistance?

### Limits

- Disclosure may change behavior; concealment introduces ethical issues. Follow an approved research protocol, and never use the prototype for consequential live decisions.

### Evidence and sources

- supports: Wizard of Oz prototyping can use a human operator to simulate responses of a proposed system. — RS-DCAC328873CBBBF2. Simulated capability does not establish production performance, capacity or cost. (Method definition and operator role.)
- supports: The government research guidance calls for participants to understand the activity and how their data will be used before agreeing voluntarily. — RS-B809229D425E94B5. This scoped guidance does not settle every legal basis or organisational approval requirement. (Informed consent and explaining the research.)
- RS-DCAC328873CBBBF2: The Wizard of Oz Method in UX — https://www.nngroup.com/articles/wizard-of-oz/
- RS-B809229D425E94B5: Getting informed consent for user research — https://www.gov.uk/service-manual/user-research/getting-users-consent-for-research

### Vedokrok editorial review

Prototype the conversation, not the capability

A human-operated prototype can answer whether an interaction is useful before the automation exists. The trap is treating smooth human performance as evidence that the eventual system will be equally fast, reliable or cheap.

#### Borrow human capability to test the part that is still uncertain

Wizard-of-Oz prototyping is useful when the interaction question arrives before the engineering is ready. A 2026 systematic review of 194 SIGCHI papers found the method used across many domains for reasons including technical limitations, adaptive flexibility, experimental control and cost. That supports a narrow claim: a person can stand in for missing system behaviour so a team can learn about the interaction. It does not show that the missing automation is feasible. A good session therefore starts by naming the question the prototype is meant to answer — for example, whether users understand a feedback format — and leaves accuracy, latency, scale and operating cost for later tests.

#### Transparency changes the research question

Classic Wizard-of-Oz studies usually hide the operator so participants experience the system as autonomous. The current card deliberately uses a transparent variant. That can be the safer and more honest choice for ordinary product discovery, but it changes what the result means. Once people know a human is involved, the session cannot tell you how they would react to apparent machine autonomy in the same way. It can still reveal whether the workflow makes sense, whether a response is useful, what users ask next and where the interaction breaks. In other words, disclosure does not make the prototype useless; it moves the claim from “this is how users respond to an autonomous system” toward “this is how they respond to this interaction with declared human assistance.”

#### The wizard is part of the measuring instrument

Human flexibility is the advantage and the main source of noise. Riek’s systematic review of 54 human–robot interaction experiments found that most studies constrained what the wizard produced, but very few reported measuring wizard error or pre-experiment wizard training. The broader 2026 review again identified wizard variability and bias, timing and performance constraints, ecological validity, deception and ethics, and transparency and reproducibility as recurring concerns. For practical prototyping, constrain everything that is not under study: define allowed responses, record what the operator supplied or repaired, log delays and deviations, and make operator freedom explicit. If the wizard quietly rescues every awkward case, the prototype can become a test of the wizard’s skill rather than the design.

#### Does telling participants about the operator ruin the test?

No, but it rules out some conclusions. A disclosed operator is compatible with testing flow, comprehension, desired response shape and whether an interaction is worth pursuing. It is weaker evidence for questions that depend on believing the system is autonomous, such as perceived agency or some forms of trust. If that distinction matters, write it into the study question before the session rather than explaining it away afterwards.

#### How tightly should the wizard be scripted?

Tightly enough that irrelevant operator differences do not become the result, but not so tightly that you remove the behaviour you are trying to explore. If wording is the variable, standardize timing and available actions. If you are discovering what users may ask, allow bounded flexibility but log every novel response. There is no universal script length; the useful rule is to control what should stay constant and expose what is intentionally allowed to vary.

#### When should the wizard leave the loop?

When the main uncertainty moves from interaction value to implementation performance. Once you need to know real recognition accuracy, model failure modes, latency, throughput, unit cost or behaviour at scale, human simulation becomes the wrong instrument. Houde and Hill’s prototyping framework is useful here: a prototype should be judged by the design question it was built to answer, not by how complete it looks. A convincing Wizard-of-Oz session can justify building the next technical experiment; it cannot stand in for that experiment.

**Editorial takeaway:** Use human simulation to learn cheaply about an interaction before automation exists, and label the boundary precisely. A transparent wizard can test usefulness and flow, but smooth human performance is not evidence of production capability. Script and log the operator, then switch to real implementation tests when feasibility, reliability, latency, cost or scale become the question.

#### Editorial evidence

- supports: A 2026 systematic review coded 194 Wizard-of-Oz papers from SIGCHI venues and found the method used for multiple motivations, including overcoming technical limitations, adaptive flexibility, experimental control and cost-efficiency. — yang-du-du-huang-2026-woz-review. This supports using Wizard-of-Oz as a prototyping and research method. It does not establish that a simulated capability is technically feasible or that one Wizard-of-Oz setup generalizes to every product context. (Abstract; Sections 4.3 and 5.2)
- limits: The 2026 review identifies recurring methodological concerns including temporal and performance constraints, wizard variability and bias, ecological validity, deception and ethics, and transparency and reproducibility. — yang-du-du-huang-2026-woz-review. These concerns are directly relevant to interpreting a human-operated prototype as evidence. The review synthesizes reported concerns across studies rather than estimating one pooled effect size. (Section 4.4)
- challenges: A systematic review of 54 HRI Wizard-of-Oz experiments found that 90.7% constrained wizard production, while 3.7% reported measuring wizard error and 5.4% reported pre-experiment wizard training. — riek-2012-woz-hri-review. The sample is limited to HRI publications from 2001–2011, so the exact percentages should not be generalized to all modern HCI work. They illustrate how underreported operator control can weaken reproducibility. (Abstract)
- contextualizes: Early Wizard-of-Oz methodology work treated human simulation as a way to study proposed interactive behaviour before the final system existed, while emphasizing practical control of the simulated interaction. — dahlback-jonsson-ahrenberg-1993. This is foundational method work focused on natural-language interfaces, not evidence that every transparent human-operated prototype produces valid behavioural estimates. (Article abstract and methodological discussion)
- contextualizes: Houde and Hill argue that prototypes should be designed and interpreted around the specific design question they represent, distinguishing role, look-and-feel and implementation concerns. — houde-hill-1997-prototypes. This prototyping framework supports the editorial distinction between testing interaction value and testing implementation capability; it is not a Wizard-of-Oz efficacy study. (Publisher summary and prototype model)
- yang-du-du-huang-2026-woz-review: Mapping the Wizards' Path: A Systematic Review of Wizard-of-Oz in HCI — https://doi.org/10.1145/3772318.3791174 — Ruoxuan Yang, Yuwei Du, Hongyang Du, Kaibin Huang
- riek-2012-woz-hri-review: Wizard of Oz studies in HRI: a systematic review and new reporting guidelines — https://doi.org/10.5898/JHRI.1.1.Riek — Laurel D. Riek
- dahlback-jonsson-ahrenberg-1993: Wizard of Oz studies — why and how — https://doi.org/10.1016/0950-7051(93)90017-N — Nils Dahlbäck, Arne Jönsson, Lars Ahrenberg
- houde-hill-1997-prototypes: What do Prototypes Prototype? — https://doi.org/10.1016/B978-044481862-1/50082-0 — Stephanie Houde, Charles Hill

Editorial version: 1.0.0 · evidence checked 2026-09-24 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/give-the-user-a-goal-and-keep-your-instructions-out-of-the-result
Related (compare_with): https://vedokrok.com/knowledge/deliver-the-small-service-before-automating-its-machinery
