Flow, process and networks
Service blueprint
Links customer actions to visible service, backstage work and supporting processes.
- Diagram
- Responsibility
- Service design
What it answers
How do visible service and backstage work support the customer?
- Shape
- Customer, frontstage and backstage layers
- What it shows
- Dependencies and potential service failure points.
Example
The question
What happens behind the scenes when a customer collects in store?
Click and collect service blueprint
Illustrative data. It belongs to no company.
When to use it
Use it when
Service design and operational coordination.
Avoid it when
Missing support systems or unclear visibility boundaries.
How to read it
Read each customer action vertically through service layers, then follow hand-offs.
Note
Define visibility, interaction and hand-off boundaries.
The data you need
- Layout
- Wide service-stage table
- Fields
- StageOrder: integer; Stage,CustomerAction,Frontstage,Backstage,Support: text
- One row is
- One service stage with activities across service layers. What is the grain?
- Rules
- Align activities by stage and identify responsibility and hand-offs.
- Optional
- Visibility boundaries,FailurePoint,Owner,EvidenceSource.
- Preparation
- Validate the input grain and missing values. Align activities by stage and identify responsibility and hand-offs.
- Units
- Relationships and positions have no numeric unit by default. Label any counts, durations, probabilities or weights separately.
Worked example
Customer submits order; frontstage confirms; backstage validatesstock; inventory system supports it. Stock validation links a visible promise tohidden work.
| StageOrder | Stage | CustomerAction | Frontstage | Backstage | Support |
|---|---|---|---|---|---|
| 1 | Order | Submit order | Confirm order | Validate stock | Inventory system |
| 2 | Delivery | Receive parcel | Send tracking | Dispatch parcel | Carrier |
