Service blueprints in the same canvas.
Frontstage and backstage lanes, a line of visibility, systems underneath. A blueprint is a journey map with more honesty about what happens behind the counter.
Start from the blueprint template.
The service blueprint starter comes with customer actions, frontstage, backstage and systems lanes already in place, plus a divider for the line of visibility. Rename, reorder, add.
- Frontstage and backstage lane types. Purpose-built lanes, not text cards with a naming convention.
- Divider lanes. Draw the line of visibility, the line of interaction, or both.
Link the blueprint to the journey.
Put a linked-map lane on the customer journey and nest the blueprint under the stage it explains. Readers click through; editors keep one source of truth.
- Linked maps. Nest detail without duplicating it.
- Shared personas and metrics. The same libraries serve every map in the workspace.
Find the failure points.
Backstage pain points get keys too. When a handoff between systems is what hurts the customer, add it to the portfolio from the blueprint. It sits next to the frontstage problems and gets scored the same way.
Questions teams ask
What is the difference between a journey map and a service blueprint?
Keep exploring
See your journeys take shape.
Start your free 14-day trial. No card needed.