Share article
A few years ago, I sat through a workshop where we spent three hours sticking coloured notes onto a roll of paper stretched across the entire meeting room. By the end of the day, we had a beautiful customer journey map. Emotions marked at every stage, pain points highlighted in red, moments of truth underlined. I was thrilled, so thrilled that I photographed the thing from several angles.
Three months later, I found that map rolled up behind a cupboard in the very same room. Nobody had gone back to it. Nothing had changed.
This isn’t a one-off experience. It’s practically a ritual. Companies invest weeks in gathering data and dozens of hours of management time in workshops, and the result is an artefact that looks great on the intranet and does nothing to make life better for customers. Forrester’s analysis of journey mapping practice describes exactly this pattern: once finished, maps lose momentum and gradually become just another piece of archived research, filed away alongside everything else (Forrester, Mapping The Customer Journey). According to the same analysis, companies that actually got something out of the exercise did two things differently: they genuinely shared the map across the whole organisation, not just within the team that built it, and they systematically turned its insights into concrete action, rather than waiting for things to somehow implement themselves.
That second part is the harder task. And it’s exactly where you find out whether the map was an investment or just a nice picture.
Why it so often falls flat
Before getting into what to do differently, it’s worth asking why so many companies miss this step. The answer shows up in one of the most-cited pieces of research in the customer experience field. In 2005, Bain & Company surveyed 362 companies and found that 80% of them believed they were delivering a superior customer experience. When customers of those same companies were asked the same question, only 8% agreed (Bain & Company, Closing the Delivery Gap, 2005). That gap has since become known as the “delivery gap”: the space between what a company thinks it’s delivering and what the customer actually experiences.
In the same study, Bain went a step further and asked why that gap exists in the first place. One of the main reasons: only 30% of the companies surveyed had a working feedback loop, a systematic process that actually fed customer information back into decision-making (Bain & Company, 2005). In other words, companies were collecting data but couldn’t get it to circulate back into the organisation in a way that changed anything. A journey map, in this respect, is just another form of data collection. Without a mechanism that turns it into decisions, it ends up exactly where mine did: behind the cupboard.
Turning a map into priorities, not just observations
A good journey map typically surfaces ten, fifteen, even twenty pain points. That’s a problem in itself. A company with limited capacity can’t tackle twenty things at once, and trying to usually means nothing gets done properly.
A practical filter that works well combines two dimensions: impact on the customer, and difficulty of fixing it. Impact can be estimated from data you already have on the map: how often customers go through that stage of the journey, how strongly it affects their emotional state, and how many customers drop off or complain at that particular point. Difficulty is best judged realistically: does fixing it mean changing one process, or touching a system that affects five different departments?
In the same study, Bain set out three principles that separate companies which genuinely close the gap between perception and reality from those that just talk about it. These companies identify their most important customers and understand their needs, design offerings tailored precisely to those needs, and treat every customer interaction as a valuable resource rather than routine admin (Bain & Company, 2005). Translated into journey-mapping terms: don’t start where the problem is most visible, start where it overlaps with your most valuable customer segment. A pain point that occasionally annoys a marginal group can wait. One that repeatedly hits high-value customers can’t.
This choice should be explicit and written down, not just something everyone quietly assumes. Draw up a short list of three to five priorities with a clear rationale for each, and share that list with the same energy you shared the map itself. A priority nobody outside the CX team knows about only gets implemented by accident.
Who’s actually accountable for turning a priority into action
This is the point where journey mapping splits companies into two camps. In the first, the team that built the map writes up recommendations and then waits for someone else to act on them. In the second, every stage of the journey has a clearly named owner accountable for the outcome at that stage, regardless of how many departments touch it.
The customer journey almost never lines up neatly with a company’s org chart. A customer applying for a mortgage moves through a marketing campaign, digital onboarding, document verification, a contact centre, a branch, and finally an approval process — six different departments, each optimising only its own piece. The result is paradoxical: every team does its own job well, and the customer still hits friction, because nobody feels responsible for the handoffs between steps.
The practical fix more and more companies are adopting is the “journey owner” role. This is a person or team who doesn’t need direct control over every department the journey passes through, but does have the mandate to track metrics across the whole journey, pull people from different teams together to fix specific friction points, and escalate when something gets stuck at a departmental boundary. Alongside the overall journey owner, it also makes sense to have owners for individual stages people accountable for a specific section who report back to the journey owner.
Without this structure, you get exactly what I’ve seen happen many times over: recommendations from the map end up in a slide deck, everyone nods and agrees they’re important, and then nothing happens, because on paper it wasn’t formally anyone’s job.
Keeping the map alive
This is the part companies underestimate the most. A journey map built as a one-off project starts going stale the moment it’s printed. Customers change their behaviour, new channels appear, competitors launch new products, and what was accurate a year ago may no longer hold true.
The answer isn’t to schedule an annual “map review” and call it done. A yearly cycle is better than nothing, but a genuinely living map responds to signals in the data, not just a date in the calendar. If complaints suddenly spike at one stage of the journey, if you launch a new product or channel, if a key process behind the scenes changes that’s a trigger to update, whatever the scheduled review date says.
In practice, this means connecting the map to ongoing data sources: stage-by-stage satisfaction scores, contact-centre call analysis, drop-off data from digital channels. The map stops being a static picture and becomes more of a living document, one the team returns to at every quarterly review, adding new findings and crossing off points that have since been fixed. This kind of ongoing upkeep is, according to Forrester’s research, exactly what separates companies where the map stays alive from those where it ends up behind the cupboard, like mine did.
How to tell whether a fix actually worked
The last step, and I think the most important one, is closing the loop. Not just making a change to the journey, but checking whether it actually shifted customer behaviour or how customers feel.
The basic rule: before you change anything on the journey, record the baseline for the relevant metric at that stage. It doesn’t need to be complicated. Track CSAT (Customer Satisfaction Score, a measure of how satisfied a customer was with a specific interaction) or NPS (Net Promoter Score, a measure of how willing a customer is to recommend the company) right at the affected stage, not just as a single company-wide number. After making the change, track that same metric again, ideally after enough time has passed for the real effect to show, rather than just a short-term reaction to something new.
Granularity is what matters here. Company-wide NPS moves slowly and is affected by dozens of factors at once, so it’s hard to tell whether your specific fix at a specific stage actually made a difference. A metric tied to one point in the journey gives you a much cleaner signal. Driver analysis is useful here too identifying which specific aspects of the experience correlate most strongly with overall ratings because it tells you whether the point you fixed is actually one of the ones driving customer perception up or down.
The link between improving loyalty and business growth isn’t just a hunch, either. In his landmark Harvard Business Review article, Frederick Reichheld described cross-industry analysis showing that companies with the highest NPS grew roughly two to two-and-a-half times faster than competitors in the same sector (Reichheld, “The One Number You Need to Grow”, Harvard Business Review, 2003). Working on specific points along the journey is a real way to contribute to that growth, rather than just hoping it happens on its own.
And it’s just as important to tell customers about the fix. Go back to the people who complained about the issue and let them know something’s changed. That’s not just a courtesy gesture. It’s a way to check, first-hand, whether the fix actually addresses what customers saw as the problem, and it’s a fast way to build a reputation as a company that genuinely acts on feedback, not just collects it.
The map as a tool, not a goal
When I picture that rolled-up map behind the cupboard now, I don’t see a failed workshop. That day’s work was good, the data was solid, the insights were valuable. What was missing was everything that should have come after: a clear priority list, a named owner, a mechanism to keep the map alive, and a way to tell whether anything had genuinely improved.
A journey map on its own saves nobody. It’s a diagnosis, not a cure. Its value comes entirely from what the company does with it next, and that final stretch is what decides whether the investment in mapping was worthwhile, or whether, three months later, it ends up exactly where mine did.
