Prototyping Services and Experiences

Many innovations are not physical products. They are experiences.

Customers do not simply purchase airline tickets. They experience check-in processes, security procedures, boarding systems and customer service interactions. Students do not simply receive educational content. They experience assessments, learning activities, feedback systems and support services. Patients do not simply receive healthcare. They experience appointments, waiting rooms, consultations and follow-up care.

Services are often more difficult to design than products because they are largely invisible until they occur.

Unlike a physical product that can be examined and tested directly, services unfold over time through interactions between people, systems, environments and processes.

Prototyping helps overcome this challenge by making service experiences visible before implementation.

Rather than debating how a future experience might work, teams can simulate interactions, test assumptions and gather evidence from participants. Problems can be identified early, opportunities can be explored and confidence can be built before significant resources are committed.

Within the Expand stage of the 5E Design Thinking Framework, service prototyping transforms abstract experiences into practical learning opportunities.

Service prototyping is the process of creating representations of future experiences so they can be explored, tested and improved.

Unlike product prototypes, service prototypes focus primarily on:

• People
• Interactions
• Processes
• Touchpoints
• Environments
• Systems
• Emotions

The objective is not to create a finished service.

The objective is to learn how people experience it.

Services often fail because assumptions remain hidden until implementation.

Organizations may assume:

• Customers understand instructions
• Processes are efficient
• Staff have sufficient information
• Systems work together seamlessly
• Experiences feel intuitive

Unfortunately, assumptions are not evidence.

Service prototyping allows teams to test ideas before launch by observing how people interact with a proposed experience.

This approach helps identify:

• Friction points
• Communication gaps
• Operational challenges
• Unmet needs
• New opportunities

The cost of learning before implementation is often significantly lower than correcting problems afterwards.

A service is more than a transaction.

It is the complete experience surrounding a person's interaction with an organisation, process or system.

Examples include:

Education

Enrolling, studying, receiving feedback and graduating.

Healthcare

Booking appointments, attending consultations and receiving treatment.

Hospitality

Making reservations, checking in and accessing support.

Government Services

Submitting applications, seeking information and receiving outcomes.

Every experience consists of multiple interactions.

Understanding these interactions is essential for effective service design.

A customer journey describes the sequence of experiences people encounter while interacting with a service.

Journey prototyping helps teams understand:

• What people do
• What people think
• What people feel
• What challenges occur
• Where opportunities exist

Journeys provide a powerful way to visualise experiences from the user's perspective.

Many organizations optimise individual interactions while overlooking the overall experience.

Journey prototyping encourages a broader perspective.

Instead of focusing on isolated moments, teams explore how different interactions connect and influence perceptions over time.

This often reveals issues that remain invisible when touchpoints are considered separately.

Touchpoints are specific moments where people interact with a service.

Examples include:

• Websites
• Emails
• Applications
• Customer support
• Physical spaces
• Staff interactions
• Digital platforms

Every touchpoint shapes the overall experience.

Service prototypes help evaluate how these touchpoints contribute to customer outcomes.

Not all interactions have equal significance.

Some moments have disproportionate influence on how people remember an experience.

Examples include:

• First impressions
• Waiting periods
• Difficult transitions
• Moments of support
• Final interactions

Effective service prototypes identify and improve these critical moments.

Small improvements at key moments can significantly enhance overall satisfaction.

A service blueprint helps visualise the structure supporting a service experience.

While customer journeys describe what users experience, service blueprints reveal:

• Staff activities
• Supporting systems
• Internal processes
• Resources
• Dependencies

Blueprints help teams understand how frontstage and backstage elements interact.

Services involve visible and invisible activities.

Frontstage Activities

These are visible to users.

Examples include:

• Conversations
• Websites
• Support interactions
• Workshops
• Teaching activities

Backstage Activities

These occur behind the scenes.

Examples include:

• Data processing
• Scheduling systems
• Administrative workflows
• Internal communications

Service prototypes help ensure these elements work together effectively.

Role play is one of the most accessible service prototyping methods.

Participants assume different stakeholder roles and act out future experiences.

Examples include:

• Student and educator interactions
• Customer support scenarios
• Healthcare consultations
• Service onboarding experiences

Role play allows teams to explore:

• Emotions
• Communication
• Decision-making
• Expectations

Insights often emerge that would never arise through discussion alone.

Experience simulations create structured environments that replicate future services.

Participants engage with realistic scenarios while observers gather evidence.

Examples include:

• Simulated learning environments
• Customer service experiences
• Retail service interactions
• Community engagement activities

Simulations provide opportunities to explore behaviour in context rather than relying solely on participant predictions.

Bodystorming encourages participants to physically experience a situation.

Rather than discussing an experience from a distance, they move through it.

Examples include:

• Walking through a customer journey
• Acting out service interactions
• Exploring physical spaces
• Simulating operational activities

This approach often reveals practical challenges, behavioural patterns and emotional responses that remain hidden in workshop discussions.

Educational experiences can be prototyped in the same way as services.

Examples include:

• Assessment activities
• Interactive workshops
• Online learning environments
• Learning support systems
• Student onboarding experiences

Instead of launching a complete course or platform immediately, educators can test individual components and gather feedback.

This approach aligns strongly with learning through making and evidence-informed teaching practice.

Healthcare experiences involve significant emotional, operational and ethical considerations.

Common areas for service prototyping include:

• Appointment systems
• Waiting room experiences
• Patient communication
• Care pathways
• Telehealth interactions

Because healthcare services affect people during vulnerable situations, understanding experiences before implementation is particularly important.

Government services often involve complex processes and diverse user groups.

Prototyping helps governments explore:

• Application procedures
• Public information systems
• Community engagement
• Access to services
• Digital transformation initiatives

This helps create more accessible and user-centred public services.

Organizations increasingly prototype employee experiences as well as customer experiences.

Examples include:

• Staff onboarding
• Professional development
• Internal communication systems
• Workplace technologies
• Hybrid work environments

Improving employee experiences often produces benefits that extend directly to customers and stakeholders.

Popular methods include:

Journey Mapping

Visualising end-to-end experiences.

Service Blueprinting

Mapping systems and processes.

Role Play

Exploring interactions through participation.

Experience Simulation

Testing services in realistic conditions.

Bodystorming

Experiencing services physically.

Storyboarding

Visualising future experiences.

Customer Walkthroughs

Exploring processes step-by-step.

Pilot Programs

Testing services on a limited scale.

Each method serves different learning objectives.

Focusing Only on Processes

Services involve emotions and experiences, not simply procedures.

Designing for Internal Efficiency Alone

Operational efficiency is important but should not come at the expense of user experience.

Ignoring Frontline Perspectives

Staff frequently possess valuable insights that influence success.

Testing Too Late

The earlier service experiences are explored, the more opportunities exist for improvement.

Assuming Rather Than Observing

User behaviour often differs from expectations.

Observation provides more reliable evidence.

OpenStudios provides opportunities to prototype experiences as well as products.

Potential applications include:

• Learning pathways
• Innovation workshops
• Entrepreneurial journeys
• AI-supported learning experiences
• Collaborative studio environments

By treating learning as a service experience, educators can continuously improve how people engage, collaborate and develop ideas.

• What experience are you trying to improve?
• Which stakeholders participate in the service?
• What touchpoints shape the experience?
• Which moments matter most?
• What could be tested before implementation?

Services are experienced rather than owned.

As a result, they are often difficult to evaluate before implementation.

Prototyping helps make experiences visible.

By creating opportunities for observation, feedback and experimentation, teams can improve services before significant resources are committed.

The most effective service innovators:

• Focus on people
• Explore experiences holistically
• Test assumptions early
• Observe behaviour directly
• Refine continuously through evidence

The goal is not simply to design better services.

The goal is to design better experiences.