A Land and Expand Strategy for Customer Journey Management
A pragmatic plan-on-a-page for CX teams who are just getting started and don't want to blow it.
Most of the customer journey management content out there is frustratingly high-level. You get the big vision (the enterprise atlas, the cross-functional operating model, the org-wide transformation) but very little that actually tells you what to do on Monday morning when you’re trying to get a nascent practice off the ground.
That’s the gap I wanted to address with this plan on a page.
When you’re first implementing customer journey management, you’re probably also at the point where you have the least information you’ve ever had about the practice, and the least experience within it. Getting the foundations right at this stage matters enormously.
A lot of CX design teams are genuinely struggling in their organisations right now. They don’t quite know where they sit. They’re not sure how they’re proving value. Customer journey management has come along and a lot of people are thinking: this is the practice we can organise around. The thing that moves us from floating internal consultants, parachuted in to provide the customer’s perspective, to an embedded, operational function with indisputable value.
That’s a worthy ambition. But the way most people go about it sets them up to fail.
The Problem with Going Big Too Early
If you treat customer journey management as a flashy new practice that’s going to revolutionise how your organisation works, it gets sticky very quickly. To pull that off, you’d need to have already built extraordinary trust across the business, come off the back of an incredibly successful run as a CX team, and have stakeholders who genuinely believe in you before you’ve shown them anything.
That’s not most organisations. In most organisations, you have to earn the right to scale.
So I borrowed a concept from SaaS sales: the land and expand strategy. You land the client, prove your value in a focused context, and then expand from there. The same logic applies here. Start simply and practically. Build trust and demonstrate wins. Then, and only then, grow the scope of the practice.
The Five Activities (Not Phases)
The framework uses five core activities: Define, Measure, Analyse, Improve, and Govern. I want to be clear that these aren’t phases. They might happen in parallel at various points. But when you’re starting out, working roughly top-to-bottom gives you the best footing.
-
Define: Start with a single valuable journey. Resist the urge to start with an overarching framework or a full journey atlas. It looks impressive, but in a low-trust environment it can read as territorial, like you’re trying to map and claim the whole organisation. That triggers exactly the kind of corporate political reflexes you don’t want at this stage. Pick one journey that your organisation already knows is broken, or already knows it really values. Then build a tight group of high-performing stakeholders around it. I mean people who would get the job done even without journey management. They’re just that good. These early participants will become the role models for the practice. Others in the organisation will see their success and want in.
-
Measure: Use what’s already there. In the early days, don’t even think about introducing new KPIs. Don’t introduce new language if you can avoid it. Assimilate to the organisation. Use the metrics people already care about, speak in terms they’re already using. Your job right now is to show that journey management makes their existing priorities easier to achieve, not to teach them a new vocabulary.
-
Analyse: Keep the research simple and solid. Qualitative research techniques have a way of unsettling people who aren’t researchers. Walk into a room of sceptical stakeholders and start talking about thinking, feeling, saying, doing frameworks and you’ll lose them fast. In low-trust environments, complexity is the enemy. Focus on the kinds of data that are hard to dispute: direct feedback from surveys, reasons for leaving captured at cancellation, web analytics. These are simple, solid, and credible. Save the deeper insight work for when you’ve earned the right to take people there.
-
Improve: Think Moneyball. You’ve picked a journey that almost certainly has a few obvious wins sitting inside it. Go find them. Think scrappy. Small bets with big payoffs. If you can tackle a known retention pain point early, do it. Retention moves the needle on customer lifetime value in ways that are hard to ignore. Even if you’re just reducing support calls through small journey tweaks, that counts. That’s the kind of concrete win that builds the mandate to do more.
-
Govern: Stay lightweight. In the early stages, governance should be as lightweight as possible. A single CX point of contact. Monthly reviews with the cross-functional team. Informing key stakeholders as things emerge, rather than implementing a heavy governance structure from day one. The honest reason for this is that you have to be open to the possibility that journey management might not be the right fit for every organisation. Some organisations have already found a strong set of customer-centric principles embedded in product or service design, and a formal journey management practice won’t add much that’s distinctive. If you’ve built up a complex governance structure only to discover that, unwinding it becomes a whole problem in itself. Keep it light until you know it’s working.
When to Expand
Once you’ve had some runs on the board (real wins, demonstrated value, growing internal credibility) that’s your signal to start thinking about expansion. That’s when you can go out and make a case for a broader portfolio of journeys. That’s when you can justify deeper research methods, more sophisticated KPIs, larger bets.
Your early wins are your business case. Don’t skip to the atlas before you’ve built it.
One thing I’d caution against even at the expansion stage: going straight to an enterprise-wide journey atlas as a way of asserting organisational oversight. The C-suite you’d be presenting that to likely already has ten perspectives on every problem you’re mapping, because that’s their job. The atlas has value, but its value is better realised gradually, as a portfolio that grows organically from the journeys you’re actually managing.
When you think of it that way (not as a map you draw first and then try to make real, but as a living portfolio that you build journey by journey) the whole practice feels less like a revolution and more like a discipline. And that, frankly, is what makes it sustainable.
A Note on Who This Is For
This plan on a page is aimed at CX practitioners who are building a journey management practice from scratch, or trying to get one properly off the ground for the first time. Those early days are critically important, and they deserve more concrete, pragmatic guidance than most of what’s currently out there.
I’m also working on versions of this framework tailored to specific sectors. If you’re in financial services, media, government, or anywhere else and you’re navigating the particular challenges of your industry, I’d genuinely love to hear about what you’re facing.