Customer journey managers: what they do and when you need one

Peel back the layers of any digital transformation, the research, design and development, and you find maps. Customer journey maps, sitemaps, logic maps, empathy maps. It is one of the most-used cognitive tools we have, and for good reason: when you are building something with no physical form, a map helps you make sense of it.

That raises a question many organisations fail to answer. You have maps of every individual product. Who is holding the map of the whole thing?

Complex worlds need maps

The customer experience moved beyond a single website years ago. A client may encounter a service firm through a referral, article, event, search result, relationship partner, proposal, onboarding form, email, client portal and invoice. Some interactions are digital. Some depend on a person making a good judgement. The client experiences one firm even when each step has a different system, budget and owner.

Every additional platform creates another seam. The more surfaces you operate, the greater the chance that the experience thins out somewhere and stops meeting the standard set elsewhere.

Look at IKEA. It has to hold an experience together across stores, ecommerce, apps, social channels, delivery and, yes, the meatballs. Making that feel like one organisation is a serious undertaking.

Large organisations respond by creating specialist teams. Product and service ownership is essential for scale, focus and delivery. It also encourages each team to optimise the part it can control. The website team improves enquiry conversion. The CRM team improves data completion. Operations reduces handling time. Each measure can move in the right direction while the customer still repeats information, waits through a handoff or receives conflicting messages.

Your teams are each optimising their part of the journey. Nobody is optimising the journey.

What a journey manager owns

This is the case for a journey manager.

The title is less important than the accountability. A journey manager owns the performance and coherence of a defined end-to-end journey across products, channels and teams. They find the chasms that open at handoffs, the moments where the customer falls between two owners, and make sure somebody fixes them.

They do four kinds of work that individual product owners struggle to do alone.

Maintain the end-to-end view. The journey is kept current using customer research, operational evidence and performance data. It includes human interactions, waiting periods, policies and workarounds alongside screens.

Define shared outcomes. Product teams need local measures, but those measures sit beneath journey outcomes such as time to complete onboarding, repeated requests for information, avoidable contacts, abandonment, complaints and successful resolution. The journey manager makes trade-offs visible when one team's efficiency creates work for another team or for the client.

Prioritise the seams. Many journey failures have no natural backlog. The portal team sees a support problem; operations sees missing data; the relationship team sees anxious clients. The journey manager turns the combined evidence into a cross-team improvement and secures an owner for delivery.

Protect coherence as things change. A new form, policy, supplier or AI feature can improve one step while damaging the wider service. Journey-level review gives the organisation a way to assess those changes before the customer discovers the conflict.

The role is therefore different from a researcher who creates a journey map, a programme manager who coordinates delivery or a product owner responsible for one product. One person might wear more than one of those hats in a smaller firm. The end-to-end accountability still needs to be explicit.

Give the role a journey with boundaries

"Own the customer experience" is too broad to be useful. Define a journey around a recognisable customer goal and business outcome.

For a legal firm, that could be instructing the firm and completing client acceptance. For a wealth manager, it could be preparing for and acting after an annual review. For a consultancy, it might run from first serious interest through proposal and mobilisation.

State where the journey begins and ends, which customer groups it covers and which outcomes matter. List the principal product, operational and policy owners involved. A journey can cross organisational boundaries without becoming limitless.

It also helps to distinguish journeys from lifecycle stages. "Client" is a segment or status. "Resolve a claim" or "move from accepted proposal to productive project" describes progress a person is trying to make. The second gives the manager something concrete to improve.

Authority matters more than the map

A journey manager with excellent maps and no influence is an expensive way of documenting problems.

The role rarely needs direct control of every delivery team. It does need a route to decisions. That might include a cross-functional journey forum, agreed access to product planning, an executive sponsor and a small improvement budget. When teams disagree, somebody must be able to decide whether the journey outcome warrants changing a local priority.

Set expectations with product owners from the beginning. The journey manager should not become a shadow product director issuing work into every backlog. Product owners retain responsibility for their services and technical choices. The journey manager brings evidence from across the experience, exposes conflicts and holds the organisation to the shared outcome.

That tension is useful. If everybody agrees instantly, the journey view may be too superficial. The role earns trust by showing where an intervention helps customers and the business, rather than arriving with a map and a claim to moral authority.

Start with evidence, not a mapping exercise

Journey maps are attractive artefacts, which makes it easy to confuse producing one with changing a service.

Begin with a problem that crosses boundaries. Look at complaints, support demand, abandonment, manual chasing, delays, rework and client feedback. Interview clients and frontline colleagues. Follow a small number of real cases through the systems, taking appropriate care with personal and confidential information.

The map should show what is known, what is assumed and where evidence is missing. Add the backstage operation and ownership to the customer-facing experience. Then choose one or two seams where improvement is valuable and achievable.

For example, a firm may discover that prospects complete a detailed enquiry form and then repeat the same information during qualification because the website data never reaches the relationship team in a usable form. The form can have an excellent completion rate while the journey performs badly. Fixing the data handoff, confirmation message and colleague workflow is a journey intervention, rather than a website redesign.

Measure the result at both levels. Did the handoff work technically? Did clients repeat less information? Did colleagues spend less time reconstructing context? Did qualification quality change? That combination keeps the role grounded in delivery.

The parallel with outside-in change

There is a real similarity between journey management and outside-in transformation. A person who sits beyond one product team's settled way of working is more likely to see the constraints and compromises the team has learned to live with.

That position is the value of the role. It is also the part most at risk of being organised away. Once a journey manager is absorbed into one product team and judged mainly on that team's delivery targets, they become another person with a backlog.

Independence does not require isolation. The manager needs close working relationships with the teams and enough practical understanding to make feasible recommendations. Their perspective stays end to end, and their performance measures should reinforce it.

Do you need a new role?

Perhaps. A new title should be the last conclusion, rather than the first.

You may need dedicated journey managers when several high-value journeys cross many product and operational teams, change frequently and suffer from persistent ownership gaps. The work can justify a full-time role when resolving those seams has material commercial, regulatory or customer consequences.

A smaller firm might assign journey accountability to an existing leader, supported by research and product expertise. That can work if the person has time, authority and journey-level measures. Adding the responsibility to an already overloaded operations or marketing role in name only will produce another static map.

There are also cases where stronger product management and a shared service review solve the problem. If one product contains almost the entire journey, creating another layer of ownership may add confusion. Use the lightest structure that makes cross-boundary decisions happen.

The leadership test

Product owners do think about customers. They are also incentivised to think about customers within their surface area. Nobody in that structure is naturally rewarded for improving an experience that happens in somebody else's product. That is an ownership problem, rather than a failure of people.

Ask your leadership team a practical question. If a client had a rotten experience last week and that experience spanned three teams, who would be accountable for understanding and fixing it?

If the answer is "nobody" or "all of them", you have found the gap. Decide which journey matters, name an accountable owner, give them access to evidence and decisions, and judge the role by whether the experience improves.

Try the question on one important journey this month. If ownership is diffuse, assign a time-limited accountable lead with access to the evidence and decisions. Review whether the role removed a boundary problem before creating a permanent title.