The Customer Journey & Service Blueprinting
Innovation & New Business Proposal - TUHH Institute of Entrepreneurship & Institute of Innovation Marketing, Hamburg · part of my Technology Management MBA · study notes for revision.
The previous chapter was about validating a value proposition: does the customer actually want the thing we intend to build. This chapter changes the unit of analysis. Instead of asking is the product good, we ask how does the whole episode feel, from the moment the need appears to long after the purchase. That episode is the customer journey, and drawing it is the first market research tool in the customer-oriented design toolbox.
The reason for the switch is simple. Nobody buys a product in a vacuum. Somebody becomes aware of a problem, asks friends, searches online, walks into a shop, waits, signs something, waits again, uses the thing, and then either recommends it or complains about it. Satisfaction is built up and destroyed all along that chain, and very often the moment that ruins the experience has nothing to do with the core product at all. A perfectly good kitchen can be spoiled by two weeks of dust and strangers in the flat; a perfectly good holiday can be spoiled by carrying groceries down a steep embankment before it even begins.
So the chapter has two halves. First the customer journey map: a picture of the sequence from the customer’s point of view, with tasks, touchpoints, thoughts and feelings written along it. Then the service blueprint: the same sequence continued downwards into the organisation, so that the invisible machinery behind each visible moment becomes designable too.
1 · Why the journey, not the product, is the unit of analysis
Section titled “1 · Why the journey, not the product, is the unit of analysis”A customer journey map is a graphical depiction of a product use or a service workflow. It shows how processes, technology, people and contact points are orchestrated over time, and it records both what the customer does and what the provider does, together with the tangible evidence of delivery. The defining rule is that the whole picture is drawn from the customer’s point of view, with the focus on their needs, thoughts and feelings rather than on the org chart.
That rule already does most of the work. Once you are forced to write down the sequence as the customer lives it, you discover steps that nobody in the company owns, gaps between departments, and long stretches of waiting that never appear in any internal process document.
A journey also has to be drawn wider than the transaction. The core service or the core usage is only the middle. There is a phase before it and a phase after it, and both can dominate the overall impression:
Journey maps are used in two directions, and it is worth being explicit about which one you are doing:
- Current state. Map how customers get the job done today, with whatever solution exists, then look for the breakdowns and pain points in that existing experience.
- Future state. Use the same structure to define a new or improved service, so the design can be discussed, prototyped and implemented before anything is built.
The link between the two is the part that matters for a business proposal: the pain points found in the current-state map get translated into concrete features, functionalities, performance levels and quality dimensions of the innovation. That is how a journey map stops being a nice poster and becomes an input to a specification.
2 · Stages, touchpoints and the anatomy of a journey map
Section titled “2 · Stages, touchpoints and the anatomy of a journey map”A touchpoint is any moment of contact between the customer and the offering: an advertisement seen from the motorway, a website, a parking barrier, a sales conversation, an invoice, a support call, a social media post after the purchase. Journey maps place touchpoints horizontally along a timeline, grouped into the three phases above.
Under each stage the map records six things, which are easiest to remember as questions:
| Row | Question | What goes in it |
|---|---|---|
| Task | What is the customer doing? | The activities and tasks, forming the customer swim lane that is the backbone of the map |
| Stage | When is it happening? | Which phase of the sequence the task belongs to |
| Need | Why are they doing it? | The underlying need being served, not the surface request |
| Touchpoint | Which channel? | Shop, phone, app, e-mail, another person, plus the systems and software behind that channel |
| Thinking | What is in their head? | The thought at that exact moment, in their own words |
| Feeling | How do they feel? | Excited, confused, suspicious, relieved, irritated |
Put those rows side by side across the timeline and a seventh writes itself: opportunities. Wherever the state of mind turns negative there is a candidate for redesign, and wherever it is already positive there is something worth protecting.
The kitchen example from the lecture shows how little is needed to make this useful. Somebody buys their first house and is excited. They talk to friends and look at catalogues, and the dream starts to feel possible. They browse for kitchen studios nearby and think it looks impossibly complicated. They visit a showroom and are delighted by how good everything looks. They talk to a sales representative and are shocked by the price. They go home, look again, come back, get an offer that fits their budget, and buy. Then the construction work starts, and the dominant feeling is not joy but all these strangers in my flat, and the dirt. Only at the very end, over the first dinner cooked in the new kitchen, does the feeling turn positive again.
That single observation is the whole argument for journey mapping. If you think about the kitchen as a product, installation is logistics. If you think about the kitchen as a journey, installation is where the experience is won or lost.
3 · Making the map realistic - evidence instead of opinion
Section titled “3 · Making the map realistic - evidence instead of opinion”The horizontal axis of a journey map is easy to draw and easy to draw badly. The paper on realistic journey maps argues that most maps in circulation are critically flawed, for two related reasons:
- they assume that every customer passes through every touchpoint, and
- they assume that all touchpoints are equally important.
Both assumptions come from the same place. The map was built in a meeting room out of what managers believe happens, and it was never checked against customers.
The study behind that claim worked with the management team of one of the world’s largest indoor shopping malls. Together they listed every touchpoint a shopper might meet, grouped into before, during and after the visit. The list came to 60 touchpoints - 37 before the visit, 14 during it and 9 after it. Then, instead of stopping there, they ran a short questionnaire with 100 shoppers inside the mall, asking for each touchpoint simply whether it had happened that day.
The results dismantled the map. Of the 60 touchpoints management had invented, 50 were experienced by fewer than half the shoppers. Even inside the surviving top ten, the spread was enormous: 95 percent intended to recommend a shop to somebody else, while only 46 percent had received any comment from the people shopping with them. A map that treats those two as equally important is steering management attention to the wrong places.
- Every touchpoint management can think of is included, so the map is enormous
- Everything looks equally critical, so nothing gets prioritised and managers quietly stop using it
- It shows what the company imagines customers do
- Customers are asked directly which touchpoints they actually experienced
- The share of customers per touchpoint separates the critical ones from the marginal ones
- It shows what customers really do - shorter, truer, and therefore actually used
The second half of the argument concerns the vertical axis, which is where most maps quietly fail. If the vertical axis is only a row of emoji faces, the map has become an empathy exercise - useful, but unable to tell anyone what to change. If the vertical axis is an unstructured heap of design ideas, branding wishes and employee tasks, the map grows until it is unreadable. The recommendation is to treat the vertical axis as the key components of the service system at each touchpoint, with each row owned by a function, so that marketing, human resources, operations and IT can each see what they have to deliver:
Built that way, the journey map stops being a picture and becomes a cross-functional planning tool, and it hands over naturally to the blueprint in the second half of this chapter.
4 · Pains, gains, emotions and moments of truth
Section titled “4 · Pains, gains, emotions and moments of truth”Once the stages, touchpoints and feelings are on the map, four annotations turn it into an innovation instrument:
| Annotation | What you are marking | Why it matters |
|---|---|---|
| Pain point | A step where the customer is frustrated, confused, delayed or made to do work | Each pain point becomes a candidate feature, quality dimension or performance target for the new offering |
| Gain | A step the customer genuinely enjoys or values | Tells you what must survive a redesign, and what is worth advertising |
| Emotion curve | The rise and fall of feeling across the whole sequence | Shows where the experience collapses, which is rarely where the company assumes |
| Moment of truth | A step where customer and provider actually meet | These are the points where quality is judged, so they deserve the most design attention |
A moment of truth is not a metaphor here. It has a precise definition once we reach the blueprint: it is any point where the customer crosses over and interacts with a contact employee or with the company’s self-service technology. Those crossings are where perceived quality is created, and there are usually far fewer of them than people expect. One of the findings in the freight-transport case later in this chapter was exactly that: only a small number of contact points really mattered to customers.
The practical move is always the same. Take the pain points from the current-state map and rewrite them as requirements. We waited eleven days for a spare part becomes a performance level. Nobody told us what would happen next becomes a communication feature. The technician did not have the part on the van becomes a support-process redesign. That translation is the bridge to the next chapters, where those candidate features get sorted by how much they actually matter.
5 · Service blueprinting - the operational companion
Section titled “5 · Service blueprinting - the operational companion”A journey map tells you what the customer experiences. It does not tell you what has to happen inside the firm for that experience to occur. That is the job of the service blueprint.
The motivation is the intangibility problem. Services are fluid, dynamic and produced in real time together with the customer, and they usually have very few static physical properties. Because there is nothing to hold up and point at, people fall back on describing services in words alone, which produces oversimplified, incomplete and biased specifications, and everyone in the room walks away with a different mental picture. Blueprinting fixes that by making the service visible on one page, precisely enough to be argued about and flexible enough to leave room for creativity.
Blueprinting began as a process-control technique whose selling points were that it was more precise than a verbal definition, that it could solve problems before they happened, and that it could identify failure points in an operation. It then evolved into a customer-focused tool by plotting the customer process against the organisation’s structure and by separating onstage from backstage work. Compared with formal process-modelling languages it is deliberately simple, so that customers, front-line staff and managers can all read it, use it and modify it. In one move it converts something that only existed as words and habits into an object a cross-functional group can inspect and redesign together.
6 · The layers and the three lines
Section titled “6 · The layers and the three lines”A blueprint has five components stacked from the customer downwards, and three horizontal lines separating them. Both the components and the lines are examinable, so learn them as a stack:
Each line reveals something different, which is why there are three of them rather than one:
| Line | Separates | What it reveals |
|---|---|---|
| Line of interaction | Customer actions from onstage staff actions | Where the customer is integrated into the process and co-produces the service. Every crossing is a moment of truth where quality is judged |
| Line of visibility | Onstage from backstage actions | How much of the service the customer can actually observe. Moving work across this line is a design decision, not an accident |
| Line of internal interaction | Contact staff from support processes | The cross-functional dependencies: which internal units and systems must fire for a front-line moment to succeed |
The line of visibility deserves a second look, because deciding what to put above it is a genuine strategic choice. In a hotel, turning down the bed in front of the guest is fine, while running the laundry in front of them is not. But in a restaurant, seating diners at a chef’s table inside the kitchen - traditionally the most backstage place in the building - has become a premium product. Blueprinting makes that trade-off explicit instead of leaving it to habit.
7 · Reading a blueprint - fail points, waits, redundancies and hand-offs
Section titled “7 · Reading a blueprint - fail points, waits, redundancies and hand-offs”A finished blueprint is a diagnostic instrument. You read it by scanning downwards and sideways and asking four questions:
- Steps where the wrong outcome is plausible and the customer feels it immediately
- Usually a support process consulted too late, or a step with no clear owner. Mark them with their own symbol - this is what blueprinting was invented for
- Gaps in the customer row while backstage or support work happens
- Add time estimates per step and the queues appear. Waiting is invisible internally and enormous from the customer side
- The same information collected twice by different functions; approvals that no longer change any outcome
- Also ask: how hard is the customer being made to work for what they paid for
- Every vertical link crossing the internal line of interaction is a hand-off, and departmental boundaries are where customer-visible failures cluster
- Disagreements about how a step really works signal a genuine problem area
The redundancy question produced one of the most quoted findings in the blueprinting literature. A parks-and-resorts operator was losing repeat business at a lakeside houseboat resort and could not work out why. Blueprinting the guest experience visually, with photographs and video, made it painfully clear that customers were being asked to work extremely hard for their holiday: write long shopping lists, fight through crowded local shops, carry everything down a steep slope to the boat, then anchor a large vessel every night and navigate it without training. None of that appeared in any internal process document, because none of it was work the company performed. Once it was visible, the answer was a ladder of new services - carts to the dock, grocery shopping, on-board chefs, hired captains - plus renovations and new service standards. The outcome was 50 percent fewer complaints and 12 percent more repeat business.
8 · What blueprinting does for the organisation
Section titled “8 · What blueprinting does for the organisation”Beyond finding faults in one process, blueprinting delivers organisational benefits that explain why firms keep using it:
- A common platform for innovation. Customers, employees and managers all read the same picture, so a new service or an improvement has one shared point of discussion instead of five verbal versions of it.
- Roles and interdependencies become visible. Employees see how their own work fits the integrated whole. One large freight company discovered through blueprinting that its thousands of drivers were the real face of the brand, which redirected investment into driver technology, training and equipment.
- It works strategically and tactically, and it stores knowledge. The same technique maps a whole multi-year service system or refines one single step, and the finished blueprints can be posted, edited collaboratively, worked on remotely and handed to the next team as a roadmap.
- Moments of truth get designed rather than inherited. What is visible, who is present, and even what is said at each contact point becomes a conscious decision.
- Competitive positioning gets clearer. Map your own service, an ideal service and a competitor’s service in the same notation and the quality gaps jump off the page. That comparison is exactly how one company designed its guaranteed express delivery product, which became its most profitable service.
9 · How to build one
Section titled “9 · How to build one”The build order is not arbitrary. Doing it in this sequence keeps the customer at the centre; doing it in any other order produces an internal process chart with a customer bolted on afterwards.
A few practical rules that go with that sequence:
- Name the customer segment. The same firm often serves segments through different processes - a frequent flyer and an economy passenger do not share a check-in - so different segments need different blueprints.
- Argue about where the service starts and stops. Settling that from the customer’s point of view generates more discussion than anything else in the exercise, and the discussion itself is valuable.
- Map what happens most of the time. Ignore the exotic exceptions on the first pass, then compare the typical process against an ideal or a competitor afterwards.
- Use a cross-functional team, and include customers where you can. Anyone involved in designing, delivering or supporting the service should be in the room.
- Match the detail to the purpose, then validate and maintain. A concept blueprint of a handful of boxes is right early on; a role-responsibility blueprint that stretches around a room is right at implementation, and any single box can be exploded into its own sub-blueprint later. Show the finished version to the people who actually do the work, correct it, and update it as the service changes - an out-of-date blueprint is worse than none, because it gets believed.
Worked example
Section titled “Worked example”(a) The journey: a broken fridge
Section titled “(a) The journey: a broken fridge”An appliance company sells refrigerators and also runs the repair service. The customer segment is a private household with an out-of-warranty appliance. Here is the current-state journey, annotated as in section 4:
| Stage | Touchpoint | What the customer does | What they feel | Pain | Opportunity |
|---|---|---|---|---|---|
| Pre-service | Web search, review sites | Notices the fridge is warm, searches for who repairs it | Alarmed, the food is spoiling | No idea whether the brand even services older models | Model-based eligibility check on the first search result |
| Pre-service | Booking page or hotline | Describes the fault, asks what it will cost | Suspicious about price | No price indication at all until a technician has been | Published diagnosis fee and a typical repair price range |
| Pre-service | Confirmation e-mail | Accepts a four-hour arrival window nine days away | Resigned | Long wait, wide window, half a working day lost | Two-hour window, next-day slots, live technician tracking |
| Service | The doorstep | Waits at home, lets the technician in | Relieved, slightly anxious | No warning if the route runs late | Automatic message when the previous job over-runs |
| Service | Technician and appliance | Watches the diagnosis, answers questions | Interested, then deflated | The needed part is not on the van, so a second visit is booked | Predict the likely part from the fault code at booking and load it |
| Service | Invoice and card terminal | Approves the price and pays | Grudging | Pays a call-out fee for a visit that fixed nothing | Waive the second call-out fee, or quote one all-in repair price |
| Post-service | Follow-up e-mail, review request | Rates the visit, or does not | Indifferent sliding to negative | Asked to rate the service before the fridge actually works | Delay the request until the repair is complete and confirmed |
The emotion curve peaks when the technician arrives and collapses at the diagnosis, and both the pain and the collapse are caused by something the customer never sees: how spare parts get onto the van.
(b) The blueprint: turning one stage into layers
Section titled “(b) The blueprint: turning one stage into layers”Take the service stage - the repair visit - and continue it downwards. Each layer runs through the same four steps, so read the diagram row by row across the columns:
Fail point Step 3, backstage. The van stock is only checked after the diagnosis, standing in the customer’s kitchen. The spare-parts support process is linked into the blueprint far too late, so when the part is missing the whole visit fails in front of the customer. The redesign is obvious once it is drawn: connect the parts warehouse to step 1, predict the likely part from the coded fault, and load the van the night before.
Waiting point Step 2, customer actions. The customer sits at home through a four-hour window doing nothing, while the only activity in that row of the blueprint is a dispatcher’s routing run they cannot see. The wait is invisible internally, because nobody inside the company is idle during it. Narrowing the window, or simply exposing the technician’s live position, turns dead waiting time into something tolerable.
Apply it to your project
Section titled “Apply it to your project”-
Pick the journey and the segment. Name one specific customer type and one specific job to be done. If two segments experience your service differently, you need two maps, not one blended average.
-
Sketch the stages from memory first. Lay out the pre-service, service and post-service phases and the tasks in each. Treat this draft as a hypothesis, not a finding - it is exactly the internally invented map the research warns about.
-
Go and check it with real customers. Ask a decent number of people, for each touchpoint on your draft, whether they actually experienced it. Anything only a minority meets drops off the map, and the survivors get ranked by how many people hit them.
-
Add the state of mind, then mark it up. Under each surviving stage write what the customer is thinking and feeling, in their own words from the interviews. Then circle every pain, every gain, and every moment of truth where they meet a person or an interface of yours.
-
Translate the pains into requirements. Rewrite each one as a feature, a functionality, a performance level or a quality dimension. This list is the input for the feature-prioritisation chapters that follow.
-
Blueprint the worst stage. Take the step with the biggest pain and build the five layers under it: customer actions, then onstage, then backstage, then support processes, with physical evidence added last across the top. Draw the vertical links from each visible step down to the systems that make it possible.
-
Hunt for fail points, waits, redundancies and hand-offs, then validate. Mark each with its own symbol and add rough times per step if waiting is part of the complaint. Show the result to whoever would actually deliver the service and let them correct it - where they disagree with each other, you have probably found the real problem.
Key terms
Section titled “Key terms”| Term | What it means in plain words |
|---|---|
| Customer journey | The whole sequence a customer lives through before, during and after using an offering, not just the purchase |
| Touchpoint | Any single point of contact between customer and offering: an advert, a website, a counter, a phone call, an invoice |
| Customer journey map | A visual timeline of touchpoints from the customer’s point of view, carrying tasks, stages, needs, channels, thinking and feeling, with the rows underneath saying what each function must deliver |
| Moment of truth | A point where the customer crosses over and interacts with a contact employee or a self-service technology, and judges quality |
| Pain point | A step where the customer is frustrated, delayed, confused or made to do work, and therefore a candidate for redesign |
| Service blueprint | A layered picture of a service showing the customer process plotted against the organisation that produces it |
| Customer actions | The chronological steps the customer takes; the foundation row of a blueprint, always drawn first |
| Onstage contact-employee actions | What the customer can see staff, or an interface, doing during the encounter |
| Backstage contact-employee actions | Preparation, calls and admin done by the same contact staff where the customer cannot see it |
| Support processes | The internal units, systems and colleagues who never meet the customer but make delivery possible |
| Physical evidence | Every tangible the customer is exposed to that shapes their quality perception: premises, vehicles, websites, documents |
| Line of interaction | The boundary between customer actions and onstage actions; every crossing of it is a moment of truth |
| Line of visibility | The boundary between what the customer can see and what stays hidden; where work sits relative to it is a design choice |
| Line of internal interaction | The boundary between contact staff and the supporting rest of the firm; it exposes cross-functional dependencies |
Test yourself
Section titled “Test yourself”- Why is a customer journey drawn across a pre-service, service and post-service phase rather than only around the transaction? Give one example of a journey whose emotional low point sits outside the core service.
- Name the six things a journey map records under each stage, and say what the seventh column, the one you derive from them, is for.
- Which two assumptions make most journey maps unrealistic, and how did the shopping-mall study show that both are wrong?
- List the five components of a service blueprint in order from the top, plus the three lines that separate them. What does each line reveal?
- In the fridge-repair blueprint, van stock is only checked after the technician has diagnosed the fault in the customer’s kitchen. Why is that a fail point rather than just an inconvenience, and what does the blueprint suggest as the fix?
- Give three reasons why a firm would blueprint a service it already runs perfectly well, other than to find faults in it.
Revision summary
Section titled “Revision summary”Next: The Kano Model → - which features are expected, which sell, and which delight.