Originated by G. Lynn Shostack (How to Design a Service, 1982) and carried into service design by Marc Stickdorn and Jakob Schneider (This Is Service Design Thinking, 2010).
Maps a service in layers, from what the customer does and sees through frontstage and backstage staff actions to support systems, showing how hidden work produces the experience.
A hotel check-in in four layers, and where the afternoon wait really starts
Three stages of a stay across, four layers of the service down, the guest on top. The first observation is placed as an example; select each other one, then the layer and stage where it happens, and follow the desk wait down to the system under it. Illustrative.
- Not placedPlacedGuestFrontstageBackstageSupport systems
- Not placedPlacedGuestFrontstageBackstageSupport systems
- Not placedPlacedGuestFrontstageBackstageSupport systems
- Not placedPlacedGuestFrontstageBackstageSupport systems
- Not placedPlacedGuestFrontstageBackstageSupport systems
- Not placedPlacedGuestFrontstageBackstageSupport systems
- Not placedPlacedGuestFrontstageBackstageSupport systems
- Not placedPlacedGuestFrontstageBackstageSupport systems
Layer of the service
Stage of the stay
Your sort matched 0 of 8.Your sort matched 1 of 8.Your sort matched 2 of 8.Your sort matched 3 of 8.Your sort matched 4 of 8.Your sort matched 5 of 8.Your sort matched 6 of 8.Your sort matched 7 of 8.Your sort matched 8 of 8.
- Guest
- What the guest does and sees. Complaints surface here, and few of them start here.
- Frontstage
- What the staff the guest meets do. The line of visibility runs under this row.
- Backstage
- Staff work the guest never sees. A delay here reaches the guest as a wait at the row above.
- Support systems
- The software, equipment, and suppliers the staff depend on. A fix here clears the symptom at every stage that uses it.
The sort
- Waits 15 min at the desk: Guest. The complaint in the reviews. It is where the guest meets the problem; the column under it shows where the problem starts.
- Clerk: room not ready: Frontstage. The clerk sees the room as dirty on the screen and cannot assign it. Training the clerk changes nothing below this row.
- Rooms keyed clean hourly: Backstage. A supervisor collects the housekeepers' paper sheets and keys the clean rooms in once an hour, so a room cleaned at 1:05 shows clean at 2:00.
- Desk-only status entry: Support systems. The root of the wait: the property system takes room status only at the desk terminal. Give housekeepers a phone screen and the three rows above clear.
- Circles block to park: Guest. A guest action at arrival. Its cause sits three rows down, in the garage equipment.
- Garage sign stuck: Full: Support systems. Equipment: the garage counter misses exits after six, so the sign reads Full with forty spaces free.
- Key card fails at door: Guest. The guest meets it in the room; the cause is in the encoder, in the support row.
- Encoder misses moves: Support systems. When a clerk moves a guest to another room, the card encoder keeps the old room until it is reset by hand.
An example
A 210-room business hotel kept getting the same review: a long wait at the front desk in the middle of the afternoon. The general manager added a clerk on Fridays and sent the desk team to service training, and the reviews stayed the same.
The operations lead then drew check-in as a blueprint, with the guest's actions across the top and three layers of work under them. Guests waited because clerks could not assign rooms. The rooms were clean by two o'clock, but housekeepers marked them on paper sheets that a supervisor collected and keyed in once an hour, because the property system accepted status changes only at the desk terminal. The fix was a phone screen on which each housekeeper marks a room clean on leaving it. Afternoon waits fell from fifteen minutes to four, and nothing at the desk changed.
Why it works
Customers report a service where they meet it, at the counter or on the phone, so complaints point at the front line and the fixes land there. A blueprint keeps the customer's steps on top and draws under each one the staff actions the customer sees, the work done out of sight, and the systems that work depends on. The line of visibility between the frontstage and the backstage makes the hidden share of the service plain, and the links down each column show what every touchpoint waits on.
A complaint can then be followed down its column to the layer where it starts. A fix made there clears the symptom at every stage that leans on the same system, which no amount of training at the counter can do.
The thinking behind it
G. Lynn Shostack G. Lynn Shostack, a senior vice president at Bankers Trust who wrote on services marketing, introduced the service blueprint in How to Design a Service (European Journal of Marketing, 1982) and set it before a wider business audience in Designing Services That Deliver (Harvard Business Review, 1984). Her chart lays out each step in delivering a service and marks the points where it can fail, so the weak points are on paper before a customer finds them.
Marc Stickdorn Marc Stickdorn, a service design practitioner and educator, and the designer Jakob Schneider edited This Is Service Design Thinking: Basics, Tools, Cases (BIS Publishers, 2010), a multi-author introduction to service design that presents its working tools, the customer journey map and the service blueprint among them. It is a practitioner's collection, and through it the blueprint passed from services marketing into the everyday practice of service design.
How to run it
- Scope one journey. Pick one service and one kind of customer, from first contact to last, so the map stays readable on one sheet.
- Write the customer's steps across the top. Record what the customer does at each stage and what they see or touch there.
- Draw the frontstage under them. List what the staff the customer meets do at each stage, then draw the line of visibility below it.
- Add the backstage and the support systems. Ask the people out of sight what they actually do, and list the software, equipment, and suppliers each step relies on.
- Link each touchpoint to what it waits on. Draw an arrow from every customer step down to the work and the systems it depends on.
- Trace a real complaint down its column. Follow the arrows from the complaint until you reach the lowest layer whose change would remove it.
- Fix it there, and measure at the top. Change that layer, then judge the result by the complaint where the customer meets it.
Where it goes wrong
The map is drawn from the manual. The process as written leaves out the workarounds that keep the place running. Walk the floor and ask each role what it does on a busy day before drawing a box.
It stops at the line of visibility. A blueprint with a thin backstage and an empty support row is a journey map with extra lines, and it sends every fix back to the front line. An empty bottom row means the map is unfinished.
It tries to cover everything. A map of every journey for every customer becomes a wall chart nobody reads. Draw one journey well, fix what it shows, and add the next.
When to use something else
- Customer Journey Mapping. When the question is how the experience feels to the customer, stage by stage, and the work behind it can wait.
- Value Stream Mapping. When the thing moving through the process is an order or a product, and the loss is time spent waiting between steps.
- Fishbone Diagram. When one recurring failure has many candidate causes and the team needs to sort them before testing any.
Where it sits in SOLVE eX
Go to the source
- How to Design a Service, European Journal of Marketing, 1982
- This Is Service Design Thinking, BIS Publishers, 2010