Start customer experience work with one journey

Customer experience programs often begin with a big kickoff. A steering group, a vision statement, a long list of touchpoints, a dashboard with forty measures. Six months later the dashboard is still being built and customers notice nothing different.

The programs that work usually start much smaller. They pick one journey, fix it from the customer's first moment to the last, and measure the difference. Then they pick the next one.

Why one journey beats a program

A journey is something a customer actually lives through: reporting a fault, onboarding to a new account, changing a plan, getting a refund. It has a start, an end and a result the customer cares about. That makes it easy to measure and hard to argue with.

A touchpoint, by contrast, is a slice of a journey owned by one team. Improving the call center script, the email template or the app screen in isolation often moves the problem somewhere else. The customer still waits three days. They just wait more politely.

Fixing one journey end to end forces the teams involved to work on the handoffs between them, which is where most bad experiences actually come from.

How to pick the first journey

Look for the journey where three things overlap.

• Volume: plenty of customers go through it every month, so improvements show up quickly in the numbers.
• Money: it touches revenue or cost directly, through renewals, refunds, repeat contacts or failed orders.
• Pain you can already see: complaints, repeat calls, drop-offs in a form, or a support queue that spikes at the same step.

Support tickets and call reasons are the fastest source here. Group a month of them by the journey they belong to and the candidates usually stand out within an afternoon.

Measure it before you touch it

Agree the baseline first. For most journeys, three or four numbers are enough: how many customers complete it, how long it takes, how often they have to contact you again, and what it costs you to serve each one. If you can add a short satisfaction question at the end of the journey, do it before the changes, not after.

Without a baseline, every change looks like a success, and nobody can tell which ones were.

Fix the whole thing, including the parts customers never see

The visible fixes are the satisfying ones: a clearer email, a status page, a shorter form. They matter. But the root cause is often behind the scenes. A system that does not pass the order number to the field team. An approval that sits in one person's inbox. A policy that made sense five years ago.

That is why we map the journey from the customer's side and then draw the service blueprint behind it: who does what, in which system, at each step. The fix usually needs both.

Then do the next one

Once the first journey is measurably better, share the result widely, with the numbers. It buys the credibility to take on the next journey, and it gives other teams a working example of what "better" looks like.

Four or five journeys fixed properly in a year will change how customers see you. A program that touches everything a little rarely does.

A place to start

Pull last month's support contacts, group them by journey, and count. The biggest group with a clear cost attached is probably your first journey. If you want help running that exercise, it is how our customer experience work begins.