What a blueprint shows that a journey map does not
The customer journey mapping framework draws on Nielsen Norman Group's introduction to journey mapping, which describes a journey map as a visualisation of the process a person goes through to accomplish a goal. The map's lanes describe the customer's actions, thoughts, emotions and touchpointsAny interaction between a person and a brand, paid, owned or earned, before, during or after a purchase., then the pain points, opportunities and owners. It is drawn from the customer's side, which is its strength: it records what people actually experience rather than the process the business believes it runs.
That strength leaves a gap. A journey map can show that customers wait days for a quote, or arrive at an appointment to find the staff member knows nothing about their request. It cannot show why, because the cause sits inside the business: a form that lands in a shared inbox nobody checks on Fridays, a note typed into one system and never copied to another, a manager whose approval is needed before anyone can reply. Service blueprinting, a general practice in service design, adds those layers underneath the customer's steps.
The blueprint is the internal companion to the journey map, not a replacement. The map comes first, because the blueprint borrows its customer steps; the blueprint then follows each step down into the business. Where the retention version of journey mapping gives service and billing lanes equal to marketing's and names an owner for each moment, the blueprint goes one level deeper and shows which piece of work, system or handoff each owner would have to change. For retention work this matters because the moments that send customers away, set out in the customer retention strategy guide, are usually produced backstage. The customer experience foundations hub sets the journey, onboarding, retention and loyalty side by side; the blueprint is a tool that serves all four. It pairs naturally with three tutorials and guides in this section: onboarding new customers beyond software, whose path to first value often stalls backstage; reducing customer effort, whose repeated questions usually start at a handoff; and checking marketing promises against the experience, where the step that breaks a promise is often found below the line of visibility.
Before you start
- Have a journey map, or walk the journey first. The blueprint's top row is the customer's steps. Take them from an existing map built with the journey mapping tutorial, or from notes made while walking the customer journey. A blueprint whose customer row is invented in a meeting inherits the business's assumptions.
- Pick the people who do the work. Invite someone from each team that touches the scenario: front desk or sales, the people who deliver the service, support, and whoever runs the systems. A blueprint drawn only by marketing describes the process on paper.
- Collect the evidence. Bring recent complaints and support contacts about the scenario, the forms and messages customers receive, and screenshots of the systems staff use, including the CRMThe system that stores an organisation's contacts, companies, deals and interactions, and the processes built around it. and any booking or order system.
- Book a wall or a large shared canvas. The blueprint is a grid of rows and columns that grows during the session. Sticky notes or a shared whiteboard both work; a spreadsheet makes it hard to see the handoffs.
- Agree a sponsor. The last step names a fix and an owner. Someone with authority over the teams involved should be ready to back it.
The steps
Choose one service and one scenario
Blueprint a single service and a single situation with a clear start and end, such as a first order delivered, an appointment booked and attended, or a repair reported and completed. Pick the scenario where complaints, repeat contacts or lost customers already point to trouble. Write the scenario at the top in the customer's terms and note what counts as done. A blueprint of "the whole customer relationship" becomes too large to read and too vague to act on.
Lay out the customer's steps from the journey map
Copy the customer's actions for the scenario across the top row, left to right in the order they happen. Keep them in the customer's words and at the level a customer would recognise: "books online", "gets a confirmation", "arrives", "waits", "pays". Include the steps where nothing seems to happen, such as waiting for a reply, because the business is often busiest out of sight at exactly those moments. Under each step, note the evidence the customer sees or holds: the confirmation message, the invoice, the sign on the door.
Add what staff do in front of the customer
In the next row, for each customer step, write what a member of staff does that the customer sees or hears: the receptionist greets them, the agent answers the chat, the engineer explains the fault. Name the role, not the person. Draw a line under this row and label it the line of visibility. Everything above it is what the customer experiences; everything below it is what they do not see but depend on.
Add what staff do out of sight
Below the line of visibility, write what staff do behind the scenes to make each visible action possible: checking stock before confirming, reading the customer's notes before a visit, preparing a quote, chasing a supplier. Ask the people who do the work what they actually do, including the workarounds. The unofficial steps, such as a printed list kept by one person or a message sent from a personal phone, are often where the service really runs and where it breaks when that person is away.
Add the systems and support processes
In the bottom row, write the systems, tools and processes that support each backstage action: the booking system, the CRM, the payment system, stock records, the rota, approval rules and suppliers. Note where the same information is held in more than one place and where staff copy it by hand from one system to another. Those copies are a common source of the "nobody told me" failures customers report.
Draw the handoffs between teams
Draw an arrow every time work or information passes from one role, team or system to another. For each arrow, note what passes across, how (a system update, an email, a conversation, a note on paper) and what triggers it. Handoffs are where blueprints earn their keep: a customer step that looks simple on the journey map can rest on several handoffs, each of which can lose information or add a wait. The RACI matrix can later record who is responsible for each handoff; the blueprint only needs to show that it exists.
Mark failure points and waits
Go through the grid with the evidence. Mark every point where the service fails or could fail: information lost, a step done twice, a decision waiting for approval, a system nobody checks. Mark every wait the customer experiences and trace it down the columns to the backstage cause. Link each mark to the complaints or contacts that show it happens, so the conversation stays on what customers experienced rather than on opinions. Then ask which single step limits the whole service, as the theory of constraints does: improving any other step adds little while that one holds everything up.
Check it with the people who do the work
Walk the blueprint with staff who were not in the drawing session, one column at a time. Ask whether this is what really happens, what is missing and what happens on a busy day or when someone is off. Correct the grid where it describes the official process instead of the real one. Expect disagreements between teams about what the other team does; they usually mark the handoffs that fail.
Choose the first fix and name its owner
List the failure points with what each costs the customer and what fixing it would take, then choose one to fix first, usually the constraint or the failure behind the most complaints. Name one owner, the change, the date and how you will know it worked, such as fewer contacts about that step in the support records, tracked as a KPIA metric tied directly to an objective. the owner reports. Keep the blueprint with the journey map, date it and redraw the affected columns after the change, so the next fix starts from the service as it now runs.
The blueprint's rows: a table
| Row | What it holds | Where it comes from | What to look for |
|---|---|---|---|
| Customer actions | The customer's steps for one scenario, in order, in their words | The journey map or a journey walk | Steps with no visible business response; long waits |
| Evidence | What the customer sees or holds at each step: messages, documents, signs | Copies of real messages and documents | Evidence that contradicts what staff say happened |
| Frontstage actions | What staff do that the customer sees or hears | Staff interviews and observation | Staff asking for information the customer already gave |
| Line of visibility | The boundary between what the customer sees and what they do not | Drawn by the team | Backstage problems that leak above the line |
| Backstage actions | What staff do out of sight to make the visible actions possible | Staff interviews, including workarounds | Unofficial steps that depend on one person |
| Support processes and systems | The systems, tools, rules and suppliers behind the backstage work | System owners and screenshots | The same data in several places; manual copying |
| Handoffs | Arrows where work or information passes between roles, teams or systems | Drawn during the session | Handoffs with no trigger, no owner or no record |
| Failure points and waits | Marks where the service fails, could fail or makes the customer wait | Complaints, support contacts, staff accounts | The constraint that limits the whole service |
The first five rows describe; the last two diagnose. As with the journey map's lanes, keep the description honest before anyone starts proposing fixes, or the blueprint becomes a drawing of the process the business would like to run. Not every blueprint needs every row: a small service may merge the frontstage and backstage rows for a role that does both, provided the line of visibility still shows what the customer sees.
A dog grooming salon blueprints its booking-to-collection service (illustrative)
Yuzzibel Dog Grooming blueprints one appointment
Yuzzibel Dog Grooming, an invented salon with 4 groomers and 1 front-desk assistant, receives 11 complaints in a quarter about groomers ignoring owners' instructions, such as a dog's sensitive skin or a request to leave the ears long. The owner and the team blueprint one appointment from online booking to collection.
The customer row has 7 steps, from booking online to collecting the dog. The frontstage row shows the front desk greeting the owner and the groomer handing the dog back. Below the line of visibility, the team finds that owners type their notes into the online booking form, which saves them in the booking system the front desk uses. The groomers work from a printed day sheet that lists only the dog's name, breed and service, so they never see the notes. On busy mornings the front desk passes on notes verbally, and on 8 of the 11 complaint days it did not.
The second failure point is collection. The front desk phones owners when a groom finishes, but the groomers tell the front desk by calling across the salon, and owners wait while calls queue. The owner makes two changes: the notes field now prints on the day sheet, and the booking system sends the owner a text when the groomer marks the groom finished. In the next quarter the salon records 2 complaints about instructions and no complaints about collection waits, and the front desk makes no collection calls.
Common mistakes
- Blueprinting everything at once. One service, one scenario. A blueprint of the whole business cannot be read or acted on.
- Inventing the customer row. Take the customer's steps from a journey map or a journey walk, not from the process diagram the business already has.
- Drawing the official process. The blueprint is only useful if it shows what staff really do, including workarounds. Check it with the people who do the work.
- Leaving out the waits. Steps where the customer waits look empty on the customer row and are often the busiest backstage.
- Ignoring handoffs. Most failures happen where work or information passes between people or systems. Draw every arrow.
- Stopping at the diagram. A blueprint with no chosen fix and no owner is a workshop output, not a change.
- Letting it go stale. Date the blueprint and redraw the affected columns after each change, or the next team will fix a service that no longer exists.
