A view of the whole system, not just the screens. What the customer touches above the glass, and the people, handoffs, and systems that hold it together below.
A service blueprint is the tool for the second question.
A customer journey map centres the user. It traces one person's experience across touchpoints, emotions, and decisions. It's a powerful tool, but it stops at the glass.
A service blueprint keeps going. It exposes what's below the glass: the people, interfaces, handoffs, and systems that actually produce the experience. The screens you design are the top layer of a much deeper stack, and most service failures don't happen on the screen. They happen in the handoffs the customer never sees.
Traces one person's experience across touchpoints, emotions, and decisions in time. Deep on the felt experience. Stops at the glass.
Does everything the journey map does, and keeps going. Exposes the people, systems, and handoffs that actually produce the experience. Goes below the glass.
A blueprint is not always the right tool. It pays for itself when you need to reason about the system, not just the screen.
To force specificity about operations before anything ships. You find the gaps while they're still cheap.
The customer symptom is rarely where the problem is. A blueprint lets you trace the failure back to its source below the line of visibility.
One shared artifact where research, ops, tech, and design can argue from the same picture instead of their own.
New policy, new vendor, new automation. A blueprint shows what ripples to everything the change touches.
Most breakages live at handoffs between people, teams, or systems. A blueprint puts every handoff on one canvas.
Turn 'customers are frustrated at pickup' into specific backstage actions and support processes that need changing.
Read top to bottom. The further down, the further from the customer.
What the customer encounters. Signage, app screens, receipts, the yellow bag.
What they do, in sequence, across time.
What employees or interfaces do, visibly, in response to the customer.
What employees do that the customer doesn't see. The hidden work.
Systems, vendors, internal teams, databases: everything that enables the whole thing to work.
Every crossing here is a touchpoint. This is the line the journey map already draws.
Below this line, the customer sees nothing. Most service failures hide here. This is the line that makes a blueprint a blueprint.
Handoffs between people and the systems they depend on. Where an employee hands work to a database, a vendor, or another team.
There is no single right order, but this one teaches well. Work outside-in: start where the customer is, move inward.
One service, one user, one moment. "Returning an online purchase to a store," not "Amazon." Scope is the whole game; it's better to do one slice well than the whole service poorly.
These become your columns. Chronological. If you find yourself wanting eight or nine, that's a signal your scenario is too big, not your blueprint too small.
What the customer sees, touches, receives at each step. What they actually do. This is what your journey map would already show you.
This is the line your journey map already implies. Everything you write below it, the customer never directly does.
Frontstage: the visible response from staff or interface. Backstage: the hidden work that makes the frontstage possible. Be specific. "Staff inspects item, scans barcode, confirms against order" is more useful than "Staff helps."
This is the blueprint's defining move. Below this line, the customer can't see what's happening. This is where most failure lives. If you drew this line wrong, the whole blueprint is wrong.
The systems, vendors, databases, and teams your backstage depends on. The line of internal interaction marks where an employee hands work off to a system or another team.
Scan below the line of visibility. Which of those cells, if they broke, would collapse the customer experience? Those are your fragile handoffs. That list is the point of the whole exercise.
The constraint forces you to think about scope, not exhaustiveness. If you need more steps, your scenario is too wide.
If the only thing you've added is more rows, you're not using the tool. The strategic value is in the lines.
When your group disagrees about where a cell belongs, that's the interesting moment. Don't paper over it; surface it.
The point is to see fragility, not to frame a poster. The day you print and frame a blueprint is the day it stops being useful.
The strategic value sits in where you draw the three lines. The rows are scaffolding for the lines.
Most breakdowns are not on the screen. They are in the handoff the customer never sees. The blueprint is how you find them.
This is the move Year 5 designers haven't made yet. The blueprint is the tool that makes it unavoidable.