Service Blueprint

Purpose

A Service Blueprint maps the complete service experience across multiple layers: customer actions, frontstage employee interactions, backstage processes, and support systems. It makes invisible organisational complexity visible, revealing failure points, redundancies, and opportunities for improvement that journey maps alone cannot show.

At a glance

• Group size: 4–12
• Duration: 90 minutes
• Difficulty: High
• Facilitation style: Guided collaborative mapping
• Setting: Large wall or whiteboard space; can be done digitally with Miro or Mural

How to run

1. Define scope (10 min): Choose one specific service scenario end to end. Agree on the start and end points.
2. Map customer actions (15 min): Walk through every step the customer takes, left to right. One sticky note per action.
3. Add the line of interaction (5 min): Draw a horizontal line. Above it: what the customer sees. Below it: what happens behind the scenes.
4. Map frontstage actions (15 min): For each customer action, note what the employee does that the customer can see.
5. Map backstage actions (15 min): What happens behind the scenes to support each frontstage action.
6. Map support processes (10 min): Systems, tools, third parties, and policies that enable backstage actions.
7. Add evidence and touchpoints (10 min): Physical or digital artefacts at each step (emails, forms, screens).
8. Identify pain points and opportunities (10 min): Mark breakdowns, waits, handoffs, and emotional peaks with red and green dots.

Materials needed

• Large wall or digital whiteboard
• Sticky notes in 4–5 colours (one per swim lane)
• Markers
• Printed customer journey map (if available) as a starting reference
• Red and green dot stickers for pain points and opportunities

Pitfalls & common mistakes

• Boiling the ocean: Trying to map every service at once. Pick one scenario.
• Skipping backstage: Teams over-index on what the customer sees and neglect internal complexity.
• No customer data: Blueprints built on assumptions are fiction. Ground them in research.
• Stopping at the map: The blueprint is a diagnostic tool, not a deliverable. Follow up with action.

Inclusion & accessibility

• Use colour-blind-friendly palette and add text labels to colour-coded lanes.
• Provide digital copies for remote participants or those with visual impairments.
• Ensure all voices contribute — backstage staff often have the richest insights but the least power in the room.

Variations

• Emotional layer: Add a customer emotion curve on top of the blueprint.
• Future-state blueprint: Map the desired service experience, then identify gaps to close.
• Failure mode blueprint: Specifically map what happens when things go wrong at each step.

When NOT to use this

• When you haven’t done any user research yet — build the journey map first.
• For purely digital products with no service layer — a user flow diagram may suffice.
• When the team lacks cross-functional representation — the blueprint will have blind spots.

Source & further reading

• Shostack, G. Lynn — "Designing Services That Deliver" (Harvard Business Review, 1984)
• Polaine, Løvlie & Reason — *Service Design: From Insight to Implementation* (Rosenfeld Media, 2013)
• NNGroup — "Service Blueprints: Definition" (nngroup.com)