process & strategy
Service blueprint
What is a service blueprint?
A service blueprint is a diagram that maps a service across stacked layers - what the customer does, what they see and interact with (frontstage), what happens behind the scenes (backstage), and the support systems underneath - all lined up against the steps of the journey and divided by the line of visibility. It extends a journey map downward, exposing the staff, systems and processes that deliver each moment.
Also known as: service blueprint, service blueprinting
Prefer to watch?
Watch the recap 1:15
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 is a journey map that doesn't stop at the surface - it shows the whole stack beneath each customer step. The layers, top to bottom: customer actions (what the user does), frontstage (what they see - staff, screens, touchpoints), the line of visibility, backstage (staff actions and systems the customer doesn't see), and support processes (the underlying infrastructure). Reading down a column shows everything that has to happen for one moment to work; reading across shows the journey over time. Its power is revealing where the 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.
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.