Prototyping Experiences
When the team at a major ride-sharing app wanted to redesign their passenger pickup process, they did not jump straight into coding complex software updates. Instead, they used cardboard cutouts and markers to map out the physical journey of a rider meeting a driver at a busy airport terminal. This is Prototyping Experiences, a method that turns abstract service ideas into tangible models for testing before any real investment occurs. By building a low-fidelity representation of the service, the designers could see where passengers felt confused or frustrated. They saved months of development time by catching these flaws during the early paper-based testing phase.
Testing Concepts with Low-Fidelity Models
Prototyping is like building a rough sketch of a house before you pour the concrete foundation for the actual building. You would never start construction on a physical home without seeing how the rooms connect or how the light hits the floor. Similarly, service designers use paper prototypes to simulate how a customer moves through a digital or physical space. This process allows teams to observe user behavior in a controlled environment without spending money on expensive software or complex infrastructure. By using simple tools like sticky notes, sketches, and cardboard, you force yourself to focus on the core flow of the interaction rather than the visual polish of the final product.
Key term: Prototyping Experiences — the process of creating simple, low-cost models of a service to test and refine customer interactions before full-scale implementation.
When you build these models, you must ensure that every step of the journey is represented clearly for the user. You can use index cards to represent different screens or physical stations that a customer visits during their experience. If a participant gets stuck on a specific card, you know exactly which part of your service design needs more clarity or better instructions. This iterative approach helps you identify hidden gaps in the service journey that you might otherwise miss during a brainstorming session. By focusing on the user’s perspective, you can refine the sequence of events to ensure that the experience feels natural and intuitive from start to finish.
Refining Service Flows Through Iteration
Once you have your initial model, you should conduct a walkthrough to see how real people react to your proposed service feature. This stage of the design process, known as Iterative Design, requires you to observe participants as they navigate your paper-based prototype. You should avoid guiding them too much, as the goal is to see where they struggle on their own. If a user cannot figure out how to complete a task, you simply redraw that part of the flow and try again with a new participant. This cycle of building, testing, and refining creates a robust service that is far more likely to succeed in the real world.
| Prototype Type | Fidelity Level | Primary Benefit | Best Use Case |
|---|---|---|---|
| Paper Sketch | Very Low | Rapid changes | Initial ideation |
| Storyboard | Low | Visual flow | Early journey mapping |
| Roleplay | Medium | Emotional nuance | Staff interaction |
Using this table, you can choose the right tool for your specific design challenge. If you are designing a new digital checkout process, a series of paper sketches will help you map out the buttons and data entry fields. If you are designing a hotel check-in service, a roleplay session will help you understand the tone and helpfulness of the front desk staff. By matching the tool to the problem, you make your testing phase much more efficient and effective. This structured approach ensures that you are not just guessing what works, but actively learning from the people who will eventually use your service.
Creating low-fidelity models allows teams to identify and fix service flaws before investing in expensive, final production.
But this model of simple prototyping faces a major challenge when the service requires complex, real-time data integration that paper cannot easily simulate.