Live prototyping tests a new service, product concept, or interaction design in the actual environment with real users during a brief, deliberately limited live deployment. Rather than simulating an experience in a lab or with role play, the design team stages a real version of the experience — usually running for hours or days rather than weeks — to observe how people actually behave when the consequences are real. The directness of live prototyping produces feedback of a quality that no simulation can match.
What It Is
A live prototype is a temporary, limited-scope implementation of a service concept that operates in the real world. It might be a staffed pop-up service touchpoint, a beta feature released to a small user cohort, a physical environment intervention in a public space, or a temporarily deployed mobile service. The 'live' element means real users making real decisions with real consequences — not participants in a test session performing prescribed tasks.
How to Run It
- Define the core service proposition to be tested and the specific questions you need the live prototype to answer.
- Design the minimum viable live experience — the smallest implementation that can generate valid evidence.
- Identify and prepare the environment, staff, materials, and systems required.
- Deploy with observers present who can record what happens without intervening.
- Capture both behavioural data (what people do) and conversational data (how they respond when asked).
- Debrief the team within twenty-four hours and decide: scale up, pivot, or stop?
When to Use It
Live prototyping is most valuable for service design projects where the quality of the experience depends on factors that simulations cannot adequately reproduce: social dynamics, environmental context, time pressure, real stakes, and genuinely voluntary participation. It is also effective for validating the operational model of a new service — testing whether the back-stage processes that support the front-stage experience can actually deliver what has been promised.
Tips for Success
- Over-prepare the operational side of the live prototype: the service experience is what you are testing, not your team's ability to improvise under pressure.
- Be transparent with participants about the experimental nature of what they are experiencing — most people are remarkably willing to participate in genuine design experiments.
- Assign dedicated observers who are not delivering the service: the people running it are too busy to observe carefully.
- Debrief immediately after each day of operation — fresh observations are your primary research data.
