What is Customer Journey Management?
Customer Journey Management is the practice of running customer journeys as a shared operating model — using them continuously to prioritize work, make decisions and align teams, rather than producing them once as research artifacts.
Most organizations already know what their customers go through. They have the research. They have the maps. What they don't have is a way to make that knowledge change what gets built next quarter. That gap is what Customer Journey Management closes.
Watch: what is Customer Journey Management?
Journey mapping vs. Customer Journey Management: what's the difference?
A journey map is a diagnosis: it shows you where the experience breaks. Journey management is the treatment plan, the owner, and the follow-up appointments.
| Journey mapping | Customer Journey Management | |
|---|---|---|
| Output | An artifact | A decision-making practice |
| Timeframe | A project | Continuous |
| Owner | The team that ran the workshop | Named journey owners |
| Lives in | A slide deck, a Miro board | The roadmap, the backlog, the operating rhythm |
| Answers | What is the experience today? | What do we do about it, and who decides? |
You need both. Mapping without management gives you beautiful diagrams nobody acts on. Management without mapping gives you decisions with no evidence behind them.
Why do journey maps stop being used?
Because nothing in the organization depends on them.
- 01
They were made for a project, and the project ended.
Ownership dies with the initiative that funded the work.
- 02
They describe, but they don't connect.
Nothing links the friction on the map to a line on the roadmap, so nothing happens.
- 03
They go stale, and everyone knows it.
The moment a map is visibly out of date, teams stop trusting it — and once trust goes, it never comes back.
- 04
Every team drew their own.
Marketing, product and service each have a version. None of them agree, so leadership uses none of them.
None of these are research problems. They're operating-model problems, which is why better maps never fix them.
When does an organization need Customer Journey Management?
You probably need it when more than one team touches the same customer.
- —Two or more teams are solving the same problem without knowing it.
- —Roadmaps contradict each other across the journey — one team's improvement creates friction downstream.
- —Someone can show you a journey map, but nobody can tell you what changed because of it.
- —You measure experience (NPS, CSAT, CES) but the numbers don't connect to what teams actually build.
- —Frontstage initiatives keep colliding with a backstage nobody designed.
What does Customer Journey Management actually involve?
Four building blocks. Tooling is the last ten percent, not the first.
One shared journey model
A single hierarchy of journeys everyone uses — not one per department. This is mostly a naming and scoping exercise, and it is harder and more political than it sounds. It is also the piece that makes everything else possible.
Real ownership
Every journey has a named owner accountable for its health, with enough authority to influence the roadmap. Ownership without authority produces reporting, not change.
A connection to delivery
Journeys have to be linked to the backlog, the OKRs, the quarterly planning — whatever your organization actually uses to decide what gets built. If insight cannot travel into that system, it stays decoration.
A cadence and a governance model
Reviews, decision forums, and a clear definition of who updates what and when. This is what turns a one-off exercise into a practice, and the part most organizations skip.
What tools are used for Customer Journey Management?
Dedicated platforms like TheyDo and Smaply are built for this, and they help — but only once the four blocks above exist. I've seen organizations buy a platform hoping it will create the practice. It doesn't. It makes an existing practice scale, and it makes the absence of one very expensive.
At LGT Bank I championed the adoption of TheyDo specifically to align two product teams that had been working in silos. The tool mattered. What made it work was agreeing on a shared journey model first.
A walkthrough of TheyDo and Smaply
What results can you expect?
-50%
Duplicated work
At LGT Bank I established the organization's first journey management framework. Two product teams that had been duplicating each other's work — across trade execution, compliance and client documentation — moved to a shared view of the client journey.
The pattern I see repeatedly: the first win is rarely a better customer experience. It's teams stopping work they shouldn't have been doing. The experience improvements come next, and they compound.
Who should own Customer Journey Management?
When journey management sits with a team that can only measure and recommend, it becomes a dashboard. When it sits close to the people who decide what gets built, it becomes a steering mechanism.
How long does it take to establish?
Expect a first working version in one to two quarters, and real maturity over a year or more.
Weeks 1–4
Align on the journey model and pick one journey to prove it on.
Quarter 1
Run the practice on that journey: owner, cadence, link to the backlog.
Quarter 2 onward
Extend to the rest of the portfolio and hand over ownership.
The goal is always internal capability. If the practice depends on the consultant, it isn't a practice.
Bring Customer Journey
Management to your organization
I help organizations move from journey maps that sit in slide decks to a practice that drives real product and service decisions.