McKinsey's Research: Why Journeys Beat Touchpoints in CX

Every CX dashboard in the Gulf tells a reassuring story. Call centre CSAT is at 92%. The app store rating sits at 4.6. The branch exit survey says "satisfied" nine times out of ten. And yet the customer still churns, still complains on social media, still tells a friend the bank is "fine, I guess." The dashboards aren't lying. They're just measuring the wrong thing.

McKinsey & Company's research into customer journeys supplies the uncomfortable explanation: touchpoint scores and journey outcomes are not the same metric, and treating them as interchangeable is why so many CX programmes report green dashboards while losing customers. In its widely cited analysis of end-to-end experience, McKinsey & Company found that performance on complete, end-to-end customer journeys is far more strongly correlated with overall satisfaction, loyalty and revenue outcomes than performance on any individual touchpoint. A customer can rate the call, the branch visit and the app each highly in isolation, and still feel the overall journey — opening an account, resolving a dispute, switching providers — was exhausting.

What does McKinsey's research actually say about customer journeys?

The core finding is simple and should unsettle anyone running a touchpoint-survey programme: journeys predict business outcomes better than touchpoints do. McKinsey's analysis found that journey-level performance is roughly 35% more strongly correlated with overall customer satisfaction than touchpoint-level performance is. That is not a marginal statistical nuance. It means the metric most CX teams report on in board decks — average touchpoint satisfaction — is a materially weaker predictor of whether a customer stays, spends more, or recommends you than the thing almost nobody formally measures: how the whole journey felt, stitched end to end.

This matters because most CX measurement infrastructure in the region — and globally — is built the other way round. Surveys fire after a call ends, after a delivery arrives, after a branch visit closes. Each one captures a snapshot. None of them captures the lived sequence: three days of chasing a refund, two escalations, one apology email, and a resolution that technically "closed the ticket." The touchpoint scores on that case might all read 4 out of 5. The journey was a disaster. McKinsey's research gives the structural reason journeys and touchpoints diverge, and it is worth stating as a clean, standalone answer: customer journeys outperform individual touchpoints as a predictor of satisfaction and loyalty because customers experience their relationship with a company as a continuous narrative, not as a series of disconnected interactions — so measuring only the interactions misses the thing that actually drives behaviour.

Why do touchpoint scores mislead even well-run CX teams?

Touchpoint measurement fails for a structural reason, not a execution one — you can run the survey perfectly and still get the wrong signal. A few mechanisms explain why:

• Touchpoints are measured in isolation from what came before. A customer who rates a complaint-resolution call 5 out of 5 may be grading the agent's tone, not the fact that this was their third call about the same issue. The survey has no memory of the journey.
• Averaging hides the moments that matter. A journey with nine smooth touchpoints and one catastrophic one will average out to "good" — but the customer remembers the catastrophe, not the mean. This is the statistical blind spot that end-to-end journey analysis is specifically designed to correct.
• Touchpoint silos create organisational blind spots. The contact centre owns its CSAT, the branch network owns its own, digital owns app ratings. Nobody owns the seam between them — the exact point where most journeys actually break down, such as a case handed from chatbot to human agent with no context transferred.
• Touchpoint surveys reward local optimisation. If a team is measured on call-handling satisfaction, the rational response is to make calls pleasant — not to make calls unnecessary. McKinsey's journey research implies the opposite incentive: design to eliminate journeys, not to polish them.

None of this means touchpoint data is worthless. It is a diagnostic layer — useful for spotting which specific interaction needs repair. The error is treating it as the strategic layer, the one that tells leadership whether the business is winning or losing customers. That layer has to be the journey.

How does the peak-end rule explain why journeys beat touchpoints?

Behavioural science supplies the mechanism McKinsey's data describes. Daniel Kahneman's peak-end rule holds that people judge an experience not by its average quality but by its most intense moment and its final moment — the rest of the sequence is largely discarded from memory. This is why a customer can endure eight unremarkable touchpoints in a journey and still rate the entire relationship on the strength of one terrible escalation and how it was finally resolved.

That is the behavioural explanation for McKinsey's statistical finding. If memory privileges peaks and endings over averages, then a measurement system built entirely on per-touchpoint averages is measuring something customers' brains don't actually use to form judgement. The journey-level view — which captures sequence, peaks, troughs and resolution — maps far more closely onto how satisfaction is actually constructed in the customer's mind. A loan application that was frictionless for five steps and then stalled for eleven days at the final signature isn't remembered as "90% smooth." It's remembered as "the bank that nearly lost my house deal." The ending dominates.

Loss aversion compounds the effect. Kahneman and Amos Tversky's prospect theory, developed through their research in the late 1970s, established that losses are felt roughly twice as intensely as equivalent gains. A single bad moment near the end of a journey — a fee discovered at checkout, a rejection after a long application — doesn't just lower the average score. It triggers a loss response that outweighs every preceding positive touchpoint. Touchpoint surveys, fired moment by moment, can't see this asymmetry. Journey analysis, which tracks the emotional arc across the whole sequence, can.

What should CX leaders measure instead of touchpoint satisfaction?

The shift McKinsey's research demands is from touchpoint inventories to journey architecture — mapping the stages a customer actually moves through to accomplish something that matters to them, like opening an account, resolving a billing dispute, or renewing a policy, and then scoring the whole arc rather than each stop along it. In practice, this means:

• Define journeys by customer goal, not internal process. "Resolve a billing dispute" is a journey. "Call centre interaction" is a touchpoint. The first has a beginning, middle and end the customer recognises; the second is an organisational artefact.
• Track the emotional arc, not just the endpoint score. Plotting sentiment or effort across every step of a journey reveals where it peaks, where it troughs, and where it ends — the three data points that actually predict loyalty, per the peak-end logic above.
• Identify Moments of Truth deliberately. Not every step carries equal weight. A handful of moments — the first bill, the first complaint, the cancellation attempt — disproportionately shape the relationship, and deserve disproportionate design attention.
• Measure effort alongside satisfaction. The Customer Effort Score exists because friction, more than delight, predicts churn in service-recovery journeys. A journey that is merely low-effort will often outperform one that is occasionally delightful but frequently frustrating.

This is also where behavioural economics does more than explain the problem — it supplies design levers. Friction, in Richard Thaler's framing, is sometimes necessary and sometimes sludge: unnecessary resistance that serves the organisation rather than the customer. A journey audit should ask, step by step, which friction is protective (fraud checks, consent steps) and which is sludge (a mandatory call to cancel what was a two-click sign-up). McKinsey's journey lens is what surfaces the difference, because sludge rarely shows up as a bad touchpoint score — customers rate the retention agent politely even while resenting the thirty-minute call they shouldn't have had to make.

How do you build a journey-first measurement system?

Shifting an organisation from touchpoint tracking to journey measurement is a sequencing problem as much as an analytical one. A practical build order:

1. Inventory journeys by customer goal, not department. List the five to ten journeys that account for most volume and most value — onboarding, complaint resolution, renewal, upgrade, cancellation — before touching any survey tooling.
2. Map each journey stage by stage. For every stage, capture the channel, the customer's job-to-be-done, and the known pain points. This is the foundational artefact everything else attaches to.
3. Overlay existing touchpoint data onto the journey map. Most organisations already have the raw data — CSAT by call, NPS by branch visit, app ratings. The missing step is sequencing it against the journey rather than reporting it by department.
4. Score each touchpoint's contribution to the whole, not in isolation. A transparent, consistent scoring method — rather than a raw average — lets you see which specific steps are dragging the overall journey score down, and by how much.
5. Flag the Moments of Truth and the journey's ending. Given the peak-end rule, the final step of any journey deserves a design review on its own, independent of how the rest of the journey performed.
6. Route the findings to a roadmap, not a dashboard. A journey score that nobody is accountable for fixing is decoration. Convert weak stages into prioritised initiatives with named owners.

Teams building this out often find that the hardest part is not analysis but governance — who owns a journey that spans five departments none of which individually owns the outcome. That is a structural question, and it is where a formal CX governance strategy earns its keep: someone has to be accountable for the seam, not just the stop.

What happens when organisations ignore the journey, not the touchpoint?

The cost of staying touchpoint-bound is not abstract. It shows up as the gap between what the dashboard says and what the churn report says six months later. A bank can run a technically excellent contact-centre programme — short wait times, high agent CSAT, strong first-call resolution — and still lose customers at renewal, because nobody measured the cumulative friction of the three separate interactions it took to update a single piece of account information across the year. Each call scored well. The relationship didn't survive it.

There is also a resourcing distortion. Organisations that measure touchpoints invest in touchpoint fixes: better IVR scripts, faster agent training, prettier app screens. Useful, but marginal, if the actual leak is structural — a journey that requires the customer to repeat their story to three different systems because the organisation never looked at the journey as a whole. McKinsey's research is, in effect, an argument for where the CX budget should go: toward redesigning the handoffs and the endings, not just polishing the interactions that already work tolerably well.

The regional context sharpens this further. In markets across the Gulf where customer switching costs are falling — digital-only banks, aggregator-driven insurance renewal, e-commerce platforms competing on delivery experience — the journey, not the touchpoint, is what competitors are increasingly designing against. A rival that fixes the ending of the cancellation journey, or removes the sludge from the renewal journey, wins the customer even if its individual call-centre scores are unremarkable. Touchpoint excellence is becoming table stakes. Journey excellence is becoming the differentiator.

Where this leaves CX leaders now

McKinsey's finding reframes the whole measurement conversation: the question is no longer "how do we make this interaction better," but "how do we make this journey shorter, more coherent, and better at the end." That is a harder question, because it cuts across departmental ownership, requires journey-level data infrastructure most organisations haven't built, and demands that leaders resist the comfort of a green touchpoint dashboard that is quietly disconnected from the business outcomes it claims to predict.

The organisations that move first on this will not be the ones with the most survey data. They will be the ones willing to stitch that data into a single narrative per customer goal, score it as a whole, and act on the ending first. Everything else — the call scripts, the app redesigns, the agent training — is downstream of getting the journey itself right.

Building that capability — mapping journeys properly, scoring them consistently, and turning the gaps into a prioritised roadmap — is the discipline behind Renascence's customer experience consulting work, and it starts with an honest view of where your current measurement actually sits. Organisations that want a structured first look can run a CX maturity assessment against their own journeys before committing budget to the next touchpoint fix.

Journeys, not touchpoints, are where loyalty is won or lost. Measure accordingly, and the dashboard will finally start telling the truth.