process & strategy
Service blueprint
What is a service blueprint?
A service blueprint is a diagram that maps a service across stacked layers: customer actions, frontstage elements (what they see and interact with), backstage activities (staff and systems hidden from view), and support systems beneath. Each layer aligns with journey steps and is divided by the line of visibility. It extends a journey map downward, revealing the full stack of people, processes, and infrastructure needed for each moment.
Also known as: service blueprint, service blueprinting
Prefer to watch?
Watch the recap 0:28
The demo
Here's the journey for ordering a coffee - browse, order, collect. We'll build the blueprint beneath it, one layer at a time, down past the line of visibility. Watch where the hidden break point appears.
What this demo shows (text version)
A service blueprint is built up beneath a three-step coffee-ordering journey (browse, order, collect). Each reveal adds a layer down the stack: customer actions (what the user does at each step), frontstage (the app screens and staff they interact with), the line of visibility, backstage (the kitchen staff and order systems the customer doesn't see), and support processes (payment, inventory and other infrastructure). A break point is highlighted backstage - where the order system fails to hand off to the kitchen - showing how a hidden failure undermines a visible step.
That's a service blueprint: a journey map extended downward through frontstage, the line of visibility, backstage and support processes, lined up against the journey's steps. Reading down a column shows everything needed for one moment to work; reading across shows the journey over time. Its power is exposing where the invisible machinery breaks - the main tool of service design for fixing whole services, not just their surfaces.
A service blueprint takes a journey map and goes deeper, showing the whole system beneath each customer step. From top to bottom: customer actions, frontstage (what they see), the line of visibility, backstage (staff and systems they don’t see), and support processes (the underlying infrastructure). Reading down a column shows everything required for one moment to work; reading across shows the journey over time. Its power lies in revealing where invisible parts fail or disconnect - the dropped handoff, the system that doesn’t talk to the next - which is where most service problems actually live. Use it to design and fix services as whole systems, not just their visible touchpoints. You can see and try this concept in action on this page.
A journey map shows the customer's steps; the blueprint adds everything underneath each one - the frontstage, the line of visibility, the backstage staff and the support systems. Suddenly you can see exactly where the machine breaks: the handoff between two backstage systems that drops the order. That vertical view, beneath the line of visibility, is what makes a service blueprint a tool for fixing the invisible failures, not just the visible ones.
A service blueprint stacks layers against the timeline of a journey: customer actions (the steps the user takes), frontstage actions (the touchpoints and people the customer directly interacts with), the line of visibility (the crucial divider), backstage actions (employee actions and activities the customer doesn't see), and support processes (internal systems, tools and third parties that enable everything above). Lines connect the dependencies between layers.
Where a customer journey map captures the user's experience and emotions across touchpoints, a blueprint extends it downward to expose the operational reality that produces each step - it's the service-design tool for seeing both the experience and the machinery together. Reading vertically reveals everything required for a single moment to succeed; reading horizontally shows how the service unfolds over time and across channels.
Its main value is diagnostic and coordinating: blueprints make visible where backstage processes and support systems break down, disconnect or fail to hand off - the hidden causes of "bad service" that a surface view misses - and they align teams (design, operations, IT, frontline) around a shared picture of how the whole service works. Use one to analyse and redesign an existing service or plan a new one, focusing attention below the line of visibility where many problems originate.
A service blueprint shows the full stack of a service - from customer actions to backstage systems - so you can fix what’s invisible. Try the demo to see it in action. It’s not just a journey map; it’s a system map. Each column reveals what must happen behind the scenes for one moment to work - exactly where service failures hide.
Try the interactive service blueprinting examples on this page to see how layers stack across the customer journey. Use service blueprinting examples to reveal hidden failures - like dropped handoffs or misaligned systems - that break the customer experience.