The customer journey, in five layers, and how new ideas earn investment
A journey map is only useful when it reaches the product strategy, the KPIs and the departments that have to move together. Here is the five-layer approach I use, and the discover-incubate-validate-exploit loop that decides which new ideas get money.
Adapted from an approach I wrote for a payments company in 2022. Company specifics removed.
Most customer journey work stops at a pretty diagram of awareness-to-loyalty and never touches the product strategy, the operating model or the budget. The version that changes anything goes five layers deep, in order, and each layer answers a different question.
1. The stages: how we want the customer to move
Start with the stages of the journey: awareness, consideration, acquire or purchase, service, advocate or loyalty. This is the high-level decision-making flow we want a customer to move through, from first hearing of us to recommending us. The point of this layer is shared language. Every later layer, every KPI and every department hangs off these five words, so agree on them first.
2. The touchpoints: the right message at the right time
Map every communication touchpoint to the stage it belongs to, digital and physical, managed and unmanaged: search, landing pages, partner sites, direct mail, sales calls, onboarding emails, the call center, the invoice, the newsletter. Two things come out of this map.
First, you know every touchpoint a customer passes as they progress, which lets you drive them through the journey rather than hope they find their way. The right message at the right time gives the customer the right call to action.
Second, you stop desensitizing them. When touchpoints are listed by stage, the overlapping and redundant communications are obvious, and every message becomes purposeful.
3. The journey map: where the journey meets the product strategy
This is the layer most teams skip, and it is the one that pays. The journey map links what the customer needs and wants at each stage to the business goal, the KPI, the operational activity, the responsible group and the technology systems underneath.
| Stage | Customer goal | Business goal | KPI | Operations | Owner | Systems |
|---|---|---|---|---|---|---|
| Awareness | Learn that a better option exists | Reach the right segment | People reached, qualified visits | Campaigns, content, partner marketing | Marketing | CRM, analytics, marketing automation |
| Consideration | Compare and decide quickly | Convert interest to intent | Demo requests, application starts | Sales enablement, pricing, proof | Sales, Product | CRM, website, pricing engine |
| Acquire | Get set up without friction | Lower cost to acquire, faster time to first value | Conversion, time to activation, abandonment | Onboarding, underwriting, provisioning | Operations, Risk, Engineering | Onboarding platform, KYC/KYB, core |
| Service | Get help when something goes wrong | Resolve fast, retain | First-contact resolution, wait time, churn | Support, incident handling | Customer care, Engineering | Ticketing, telephony, observability |
| Loyalty | Buy more, tell others | Expand and refer | Retention, attach rate, referrals, NPS | Account management, lifecycle marketing | Account management, Marketing | CRM, billing, marketing automation |
Built this way, the map becomes a tool for lowering the cost of customer acquisition: it shows where the friction is, how many systems a customer touches, and which operational activities can be automated.
4. The layers: which departments move when the journey changes
The fourth layer maps the stages and touchpoints to the departments that provide the inputs and outputs behind them: marketing, sales, product, technology, compliance and legal, customer care, account management, operations, executives.
Think of it as a dependency map. If we change this step in the journey, we have to work with these groups to keep the journey cohesive and purposeful. It is the difference between a product change that quietly breaks a support script, and one where support, compliance and marketing moved together because the map said they would have to.
5. The drill-down: specific customers, specific problems
Drill-down journeys are reserved for a specific customer segment we want to understand better, usually with a persona attached. They start with a question, not a template:
- Why are these customers not completing their journey?
- Why do customers of this type consistently drop out at this stage?
A drill-down follows one representative customer through each step, records the touchpoint, the satisfaction swing and the moments of truth, and captures what the customer is thinking in their own words. It ends with the two or three interactions where a change would move the KPI.
How new ideas earn investment
Journey work generates ideas. Most of them should not get money. The loop I use to decide:
- Discover the problem. Name the customer problem the journey exposed, for whom, and what it costs them and us. No solution yet.
- Incubate. Smallest possible investment: a sketch, a prototype, a concierge version, a conversation with five customers who have the problem.
- Iterate to validate the problem. Keep iterating until the evidence says the problem is real, frequent and worth paying to solve, or says it is not. Either answer is a success at this stage.
- Invest? The decision point. Validated problem, credible solution, business case that survives the journey map's KPIs: yes. Otherwise it goes back to incubation or out.
- Exploit and expand. Build, measure against the KPI in the journey map, and expand along the same direction while the numbers hold.
- New problem evaluation. Every exploited idea surfaces the next problem. The loop starts again, with more evidence than last time.
The two disciplines reinforce each other. The journey map tells you which stage and KPI an idea has to move; the evaluation loop makes sure you only pay for ideas that can.
Where it leads
This is the product side of the agentic operating model I run now. Today the journey map and the business case are drafted by agents that know the product, the regulations and the systems; the product lead still decides what moves forward, and the KPIs in the map are still what tell us whether it worked.