How to Create a Customer Journey Map: A 5-Week Roadmap With Example
8 min read ยท 2026-10-11
To learn how to create a customer journey map, pick one customer type and one journey with a clear start and end. Gather evidence from interviews, analytics and support tickets. Then draw the stages, actions, touchpoints, thoughts and pain points in one shared workshop. Check the draft with real customers, and turn the worst pain points into owned items on your roadmap. A small team can do all of this in about five weeks without stopping its other work.
Most guides list the steps and stop there. This one gives you a week-by-week plan, a worked example and a clear way to move from map to action. A journey map is only worth the effort if it changes what your team builds next. Generate your roadmap with AI (first one free), then adjust the weeks to fit your team.
The roadmap at a glance
Goal: A validated customer journey map for one persona, plus a ranked list of fixes with owners on your roadmap. Duration: 5 weeks
Set the scope (Week 1)
Decide exactly which journey you are mapping and why, so the map stays small enough to finish.
- Write one sentence that says what the map should help you decide, for example "why trial users stop before inviting a teammate".
- Choose one persona or customer segment, not "all users".
- Set a clear start point and end point for the journey.
- Name a core team of three to five people from product, design, support and sales.
- Book the mapping workshop and the review session now, before calendars fill up.
Milestone: A one-page scope note, approved by the person who owns the outcome.
Gather evidence (Weeks 1 to 2)
Collect what customers actually do and say, so the map shows reality and not team opinions.
- Interview five to eight customers from the chosen segment, including some who dropped off.
- Pull funnel data for each step of the journey from your analytics tool.
- Read recent support tickets, chat logs and sales call notes linked to this journey.
- Walk through the journey yourself on a fresh account and screenshot every screen and email.
- Sort quotes and observations into a shared document, tagged by journey step.
Milestone: An evidence file with interview notes, funnel numbers and screenshots for every step.
Draft the map (Week 3)
Turn the evidence into one visual map in a single focused workshop.
- Run a two to three hour workshop with the core team.
- Agree on four to seven stages across the top.
- Fill in each row for every stage: actions, touchpoints, thoughts, emotions and pain points.
- Mark every sticky note that has no evidence behind it with a question mark.
- Clean up the map into a digital version within two days.
Milestone: A complete draft map where every pain point links to at least one piece of evidence.
Validate the map (Week 4)
Check the draft with people outside the room before you act on it.
- Show the map to three or four customers and ask what is wrong or missing.
- Review it with frontline staff such as support agents and account managers.
- Test the open question marks with quick follow-up calls or data checks.
- Update the map and keep a short log of what changed.
Milestone: A version 1 map that customers and frontline staff agree is accurate.
Prioritize and plan fixes (Week 5)
Pick the pain points worth fixing first and put them on the roadmap with owners.
- List every pain point and rate each one on impact and effort.
- Pick the top three to five and write each as a problem to solve, not a feature.
- Assign one owner and a target quarter to each.
- Add them to your product roadmap and share the map with the wider team.
- Set a review date to measure the change and refresh the map.
Milestone: Three to five journey fixes on the roadmap, each with an owner, a metric and a date.
What a customer journey map is
A customer journey map is a visual of the steps one type of customer goes through to reach a goal with your product or service. It shows what they do, where they do it, what they think and feel, and where things go wrong. It reads left to right, like a timeline, with stages across the top and layers of detail below.
It is not a sales funnel and it is not a user flow. A funnel counts how many people move from step to step. A user flow shows the screens inside your product. A journey map covers both, plus what happens outside your product: the search before signup, the email a customer ignores, or the call they make to a colleague before buying.
The rows every journey map needs
Keep the layout simple. Each stage across the top gets the same set of rows below it. If your map has more rows than these, people stop reading it.
- Stages: the big steps of the journey, such as Discover, Sign up, Set up, First value, Invite team.
- Actions: what the customer does at each stage, in their words.
- Touchpoints: where it happens, such as your website, an onboarding email, the app, or a support chat.
- Thoughts: real questions customers ask at that moment, taken from interviews or tickets.
- Emotions: a simple high, neutral or low line that shows how the stage feels.
- Pain points: what slows them down, confuses them or makes them leave.
- Opportunities: ideas to remove each pain point, added only after the map is validated.
A worked example: a B2B app free trial
Say you run a team task app and many trials end without the user inviting anyone. The scope note says: "Map the journey of a team lead from first signup to inviting their first teammate, so we can decide what to fix in onboarding next quarter."
Here is how the stages could look after research:
That last insight is the reason to map. The team had planned to build a bigger invite button. The map shows that a ready-made sample project would do more, because it helps the lead feel the workspace looks finished before inviting anyone. That becomes a roadmap item with an owner, a quarter and a metric: the share of trials that invite at least one teammate.
- Discover: the team lead searches for a tool, compares a few options and reads the pricing page. Thought: "Will my team actually use this?"
- Sign up: they create an account. Pain point from tickets: the signup form asks for company size and role before showing anything.
- Set up: they create a first project. Pain point from interviews: the empty project screen gives no hint of what to do first.
- First value: they add tasks and assign some to themselves. Emotion rises here.
- Invite team: they hesitate. Thought from interviews: "I don't want to invite people until it looks ready." This is the real drop-off, and it is about confidence, not a missing button.
How to run the mapping workshop
The workshop is where most maps go wrong. People bring opinions, the loudest voice wins, and the map ends up showing how the team wishes customers behaved. A few rules keep it honest.
Print or share the evidence file before the session and ask everyone to read it. Start with stages only, and agree on them before adding detail. Then fill one row at a time across all stages, not one stage at a time. This keeps the map balanced and stops the group from spending an hour on signup.
You can run the session on a physical wall, in Miro or FigJam, or in a simple slide in PowerPoint. The tool matters less than the rule: one shared map that everyone can see and edit.
- Give each person a different colour of sticky note so you can see who added what.
- Write customer thoughts as direct quotes whenever you have them.
- Use a question mark on anything that comes from memory and not evidence.
- Keep a parking lot for solution ideas, so the group stays on the problem.
- End by asking each person to vote for the three pain points that hurt customers most.
How to turn the map into roadmap items
A finished map that sits in a folder changes nothing. The last week of the plan is the most important one. Take every pain point and ask two questions: how much does this hurt customers, and how hard is it to fix? Rate both on a simple scale from one to five.
Then write each chosen fix as a problem with a measure. "Team leads hesitate to invite teammates because the workspace looks empty, measured by invites in the first week" is far more useful than "Improve invite flow". It gives the team room to find the best solution and tells everyone how success will be judged.
If you want a head start on the plan itself, Generate your roadmap with AI (first one free), describe your journey and goal, then drag the phases into place.
- Link each roadmap item back to its stage on the map.
- Give each item one owner, not a group.
- Add a target quarter, not an exact date, unless the fix is small.
- Schedule a map review three to six months later to see what moved.
Common mistakes to avoid
- Mapping every customer at once makes the map vague, so choose one persona and one journey per map.
- Building the map from team memory alone gives you opinions, so bring interview quotes and real data into the room.
- Adding solutions while drawing the map hides the real problem, so keep ideas in a parking lot until the map is validated.
- Skipping the customer check means you act on guesses, so show the draft to a few customers and frontline staff before planning fixes.
- Making the map too detailed to read stops people from using it, so stick to the core rows and cut anything nobody would act on.
- Ending with a nice poster and no next step wastes the work, so put the top fixes on the roadmap with owners and dates.
Frequently asked questions
What are the steps to create a customer journey map?
Set a clear scope with one persona and one journey. Gather evidence from interviews, analytics and support tickets. Draw the stages and rows in a team workshop, validate the draft with customers, then turn the top pain points into roadmap items with owners.
How long does it take to create a customer journey map?
A focused team can finish one map in about five weeks while doing its normal work. Most of that time goes into research and validation, not drawing. A rough first draft from existing data can be done in a day, but treat it as a guess until you check it with customers.
What is the difference between a customer journey map and a user flow?
A user flow shows the screens and clicks inside your product. A customer journey map covers the whole experience, including what happens before and after the product, plus the customer's thoughts and emotions. Use flows to design screens and journey maps to decide which problems to solve first.
How often should you update a customer journey map?
Review it every three to six months, or after a big change to your product, pricing or onboarding. Check whether the fixes you shipped moved the metric you set. Update the stages and pain points, then feed new priorities into your next roadmap cycle.