A customer journey roadmap is the ordered list of changes you will make to the journey, quarter by quarter, with an owner and a measure for each. The map tells you where the journey breaks. The roadmap decides which break you fix first, which waits, and which you leave alone. This article answers how to build that list from your current stage data, sequence it sensibly, and track each item's effect in the levelpartner.ai platform so the plan does not stall after the first quarter.
A map is a diagnosis, a roadmap is a treatment plan
Most firms finish a mapping exercise with fifteen good ideas and no order. Six months later, the three easiest ideas are done and the one that mattered most is still on the list. A roadmap fixes that by ranking ideas on two things: how much revenue the broken stage costs you, and how long the fix takes.
Fix the stage that loses the most revenue first, unless a smaller fix will take a week and the larger one will take a quarter. Then do the quick fix first, while you plan the large one.
Before you start
- A current journey map with pain points listed. See customer journey mapping if you do not have one.
- Stage conversion figures from your dashboard for at least one quarter.
- An average deal value or client value you trust.
- One leader with the authority to set priorities across teams.
How to set it up
- List every change suggested by the journey map on a single sheet.
- Beside each change, name the stage it affects.
- Estimate the revenue lost at that stage last quarter using stage drop and average deal value.
- Estimate the effort for each change in days, roughly.
- Rank the list by revenue lost, then move any change under a week of effort to the top.
- Assign no more than three changes per quarter, each with one owner.
- For each change, add a dashboard widget showing its stage's conversion.
- Record the baseline figure for each report before the change goes live.
- Book a quarterly review to compare each figure against its baseline.
Suppose the agency's map produces eight ideas, and quoting is the leakiest stage: 60 proposals a quarter, average value £18,000, only 12 signed. That is £864,000 of proposed work a quarter that does not sign. A faster proposal template is a three-day job, while a new pricing structure is a quarter's work. The roadmap order would be the template in month one, pricing in quarter two and the website redesign deferred to quarter four. These figures are illustrative.
How many items per quarter
Three at most. A team of 10 to 250 people running its normal business cannot absorb more journey changes than that without them half-finishing. Each change needs time to settle before you can read its effect, usually four to eight weeks of data.
Running too many changes at once also makes it impossible to tell which one worked. If conversion improves after five simultaneous changes, you have learned nothing you can repeat.
Deciding what to leave out
A roadmap is as much about what you will not do. Write a short "not this year" list beneath it. When someone proposes an idea from that list mid-quarter, the conversation is quick because the decision was already taken.
What it replaces
The roadmap replaces the improvement backlog that grows forever and the habit of starting a new initiative every time someone attends a conference. It also replaces the quarterly strategy slide that names priorities but no owners or measures.
Time it takes each week
Building the first roadmap takes half a day. Each owner spends an hour or two a week on their change while it is in progress. The quarterly review takes an hour. The roadmap itself needs no weekly maintenance beyond owners updating status.
The mistake most people make
Putting the most visible change first instead of the most valuable one. A new website is visible and exciting. A rewritten follow-up sequence is not. If the follow-up stage loses more revenue, the follow-up goes first.
When not to use one
If the journey has one obvious hole, fix it. You do not need a roadmap to tell you that enquiries go unanswered for three days. Roadmaps earn their place once the obvious fixes are done and the remaining ideas compete for time. For the strategic choices that sit above the roadmap, read customer journey strategy.
Troubleshooting
The baseline was never recorded
You cannot prove the change worked. Pull the same report for the quarter before the change and use it as a late baseline. Next time, record the figure on day one.
Owners report progress but numbers do not move
The change targets the wrong cause. Go back to the evidence for that stage, often conversation transcripts, and check what buyers actually say.
The roadmap slips every quarter
Too many items, or owners with no time allocated. Cut to two items and agree the hours each owner will spend on them.
Results are hard to read
Use a dashboard with one widget per roadmap item. The customer journey visualization guide shows how to lay one out.
Frequently asked questions
How far ahead should the roadmap go?
Detail the next quarter, outline the one after, and keep a short list beyond that. Plans beyond six months rarely survive contact with new data.
Who owns the roadmap?
One senior person, often the operations or commercial lead. Individual items have their own owners.
Should the roadmap include technology changes?
Only where a technology change fixes a journey stage. A platform change with no stage attached belongs on a different list.