Experience Prototype

Purpose

An Experience Prototype goes beyond testing a product or interface — it simulates the entire experience a person would have, including the physical environment, social interactions, timing, and emotional arc. By staging a realistic scenario, the team can evaluate whether the experience feels right, not just whether it works.

At a glance

• Group size: 4–10
• Duration: 45 minutes
• Difficulty: Moderate to high
• Facilitation style: Scenario staging and directed testing
• Setting: A space that can be reconfigured to simulate the target environment

How to run

1. Define the experience (10 min): Map the full experience arc: before, during, and after. Identify the emotional beats, physical movements, and sensory elements.
2. Stage the environment (10 min): Set up the space to approximate the target context. Use furniture, signage, props, lighting, and sounds. It doesn’t need to be perfect — suggestive is enough.
3. Brief the actors (5 min): Assign roles: user, service provider, bystanders. Give each a brief character card.
4. Run the experience (10 min): The user walks through the entire experience in real time. Others play their roles. An observer takes notes.
5. Debrief (10 min): Ask the user: "How did that feel?" "Where were you confused/delighted/frustrated?" Ask actors: "What was difficult to deliver?"

Materials needed

• Props, furniture, signage for environment staging
• Character/role cards
• Audio (phone, speaker) for ambient sounds
• Observation template
• Camera for documentation

Pitfalls & common mistakes

• Testing only the product, not the experience: The value is in the full context — the wait, the ambiance, the handoff.
• Over-producing: The staging should be quick and suggestive. This is not a film set.
• No real user: Testing with team members only gives you insider reactions.
• Ignoring the before and after: How the user arrives and leaves is part of the experience.

Inclusion & accessibility

• Stage the experience in an accessible space.
• Consider sensory elements (lighting, sound) that may be overwhelming for some participants.
• Offer alternative ways to participate (observe rather than act, provide written feedback).

Variations

• Guerrilla experience prototype: Stage the experience in the actual target environment (a coffee shop, clinic, etc.).
• Time-shifted experience prototype: Compress a multi-day experience into a single session using time jumps.
• A/B experience prototype: Run two versions and compare user reactions.

When NOT to use this

• When testing a specific interface element — use a paper or digital prototype.
• When the environment cannot be reasonably simulated (e.g., an aeroplane cabin).
• When the team does not have time for staging — use storyboarding instead.

Source & further reading

• Buchenau & Suri — "Experience Prototyping" (DIS 2000, ACM)
• Stickdorn, Hormess, Lawrence & Schneider — *This Is Service Design Doing* (O’Reilly, 2018)
• IDEO — *The Field Guide to Human-Centered Design* (2015)