A service blueprint is a diagram that shows, stage by stage, what the customer does, what they see (people, screens, physical evidence) and what happens backstage and in support processes to deliver the service. The line of visibility separates what shows from what stays hidden. It helps you find fail points, waits and poorly handled handovers between teams.
How to use
- Write the service and the scenario: who the customer is and in what situation. One scenario per blueprint.
- List the stages in the order the customer experiences the service, one per row.
- For each stage, fill in the customer action, physical evidence, frontstage, backstage and support.
- Mark the fail point for each stage and how long the customer waits.
- Read the grid, the list of fail points and the warnings, and export it to discuss with the teams involved.
What each field asks for
| Field | What to enter |
|---|---|
| Service | The service you are going to map, from the customer's point of view. |
| Customer and scenario | Who the customer is and in what situation. One scenario per blueprint. |
| Wait unit | Applies to the wait column for every stage. |
| Stage | E.g. Collection |
| Customer action | E.g. shows the code |
| Physical evidence | E.g. receipt |
| Frontstage | People and touchpoints the customer sees. |
| Backstage | What staff do out of the customer's sight. |
| Support | Systems and internal teams. |
| Fail point | What can go wrong. Blank if none. |
| Wait | Time the customer waits. |
Example
A retail chain maps in-store pickup of online orders in 5 stages: online purchase, picking, arrival at the store, collection and after collection. The blueprint marks 4 fail points, such as out-of-date stock selling an item the store does not have and an order sitting in the queue at peak time. The customer waits 257 minutes in total, almost all of it during picking (240 minutes). A warning points out that arrival at the store has a fail point with no backstage or support process.
When to use
- Before launching or redesigning a service that involves several teams and channels.
- When the customer journey shows a bad moment and you need to understand what happens behind it.
- To align service, operations and technology on who owns each handover.
- To prioritise improvements by fail points and the longest waits.
Frequently asked questions
What is the difference between a service blueprint and a customer journey?
The journey shows the experience from the customer's point of view, with stages and emotions. The blueprint adds what the company does at each stage, front and back, and the failures that can happen. The journey often comes first and the blueprint goes deeper into the critical moments.
What is the line of visibility?
It is the divide between what the customer sees (frontstage and evidence) and what stays hidden (backstage and support). Moving it is a design decision: showing order progress, for example, brings something from backstage into the customer's view.
What counts as a fail point?
Any place where the service can break or slow down in a way the customer feels: wrong information, a handover between teams with no owner, a system outage, a queue. Each fail point deserves an owner, a warning signal and a preventive action.
What is physical evidence?
Everything the customer sees, touches or receives at each stage: screens, emails, signs, packaging, receipts. Evidence is what stays in memory and what the customer uses to judge the service.
How many stages should a blueprint have?
Between 4 and 8 is usually enough for one scenario. Beyond that, split it into two blueprints or focus on the stretch with the most problems. The tool accepts up to 10 stages.
Who should take part in building it?
People from each team that appears in the lanes: customer service, operations, technology and whoever knows the customer. The value of the blueprint lies in everyone seeing the whole service, not just their own part.