Customer journey mapping

Customer journey mapping is the practice of laying out the full set of stages a customer moves through and capturing their actions, goals, and emotions at each one. A typical map runs from awareness to consideration, purchase, onboarding, ongoing use, and advocacy. For each stage it records what the customer is trying to do, what stands in their way, and which team is responsible for that moment. The map gives a shared, end-to-end picture of the experience that no single team usually holds on its own.

It matters because customer experience is owned in pieces. Marketing owns awareness, sales owns purchase, success owns onboarding, support owns problems, and product owns ongoing use. Each team optimises its own slice, and the gaps between slices are where customers get dropped. A journey map exposes those handoffs and makes the whole experience visible in one place, which is the first step to connecting it to outcomes like retention rate and net revenue retention.

A map that is only descriptive ages into wall decoration. The version that earns its keep attaches a metric to each stage, so awareness has reach, consideration has conversion rate, onboarding has time to first value, and advocacy has referral rate. With numbers on every stage, the map stops being an opinion about the experience and becomes a live diagnostic for where it is failing.

Journey mapping is a framework rather than a single number, so you measure it by attaching the right metric to each stage and tracking progression between stages. The connective measure is the stage progression rate: the share of customers who entered a stage and went on to the next one. Layered on top, each stage carries its own experience metric.

1. 1

   Define the stages and owners

   Agree the ordered stages of the journey and name the team accountable for each. A stage with no owner is a stage where problems go unaddressed, which is exactly where customers are lost.

2. 2

   Attach a metric to each stage

   Give every stage a measurable signal: reach for awareness, conversion for consideration, time to first value for onboarding, support resolution for ongoing use, referral rate for advocacy. This is what makes the map measurable rather than descriptive.

3. 3

   Track stage progression

   For each transition, divide the customers who advanced by the customers who entered the stage. This shows where the journey loses momentum and which handoff between teams is leaking.

4. 4

   Capture the experience signal

   Pair the hard progression numbers with a softer read of how the stage feels, through satisfaction or effort scores. A stage people pass through but resent is a future churn risk even when progression looks fine.

A worked example: awareness reaches 50,000 people, 5,000 enter consideration, 1,000 purchase, 700 reach activation, and 400 become regular users. The progression rates expose that the awareness-to-consideration step (10%) and the consideration-to-purchase step (20%) both lose most of the people who reach them, while onboarding holds on to most of theirs (700 of 1,000, or 70%). The map plus the numbers tells you the experience is not failing everywhere, it is failing at two specific, ownable handoffs.

A journey map and a metric tree fit together naturally. The map lays out the stages horizontally; the tree decomposes the end outcome vertically into those same stages and the levers beneath each. The root is the outcome the whole journey exists to produce, retained, expanding customers. The first level is the journey stages, because the experience compounds through them in order.

Each stage then breaks into the drivers that determine whether a customer moves forward and how they feel doing it. The onboarding stage decomposes into time to first value, setup friction, and early support quality. This is where the map becomes actionable: a stage on a diagram becomes a set of specific levers a team can pull.

KPI Tree attaches RACI ownership to each stage and driver, so marketing is accountable for the awareness branch, sales for the purchase branch, and customer success for the onboarding branch. The handoffs between stages, the places journey maps are built to expose, become explicit owned edges rather than no-man-s-land. When a stage metric moves, the platform pushes it to the accountable owner, and the verified impact loop checks whether the change to that stage flowed through to retention, so the map stays tied to outcomes instead of drifting into decoration.

There is no benchmark for a journey map as a whole, because the meaningful benchmarks live at each stage. The table below gives realistic stage-level progression and experience ranges that a mapped journey can be measured against, useful as a sanity check on where a stage sits.

Read these per stage rather than as one score. The point of mapping is to find the single stage that drags the outcome down, and that only shows up when each stage is measured against its own benchmark. Your trend over time at each stage matters more than the comparison to any external average.

A journey map improves when it moves from a one-off workshop output to a living model with metrics and owners attached. The aim is a map that surfaces the weakest stage, points to a responsible team, and keeps proving whether changes worked.

KPI Tree turns a journey map into an owned, measurable model. Each stage and each handoff becomes a branch with a RACI owner, so marketing owns awareness, sales owns purchase, and success owns onboarding, with the seams between them made explicit. When a stage metric moves, the accountable owner is notified directly, and the verified impact loop checks whether the change flowed through to retention and expansion, so the map keeps earning its place instead of fading into a slide nobody revisits.

1. 1

   Mapping once and never updating

   A journey built in a single workshop and pinned to a wall ages into decoration. The map only stays useful if its stage metrics are refreshed continuously.

2. 2

   Drawing stages without metrics

   A pretty diagram with no numbers describes the experience but cannot show where it breaks. Every stage needs a measurable signal and a progression rate.

3. 3

   Leaving handoffs unowned

   Teams own their own stages but rarely own the seams between them. Those handoffs are exactly where customers fall through, so each one needs an explicit owner.

4. 4

   Mapping the journey you designed

   Customers rarely follow the neat path you drew. Build the map from observed behaviour, including the loops and exits, not from the experience you intended to deliver.

5. 5

   Ignoring how stages feel

   Progression numbers can look fine while customers quietly resent a stage. Pairing hard progression with a satisfaction or effort read catches churn risk that the flow alone hides.