Customer journey map: from user evidence to product priorities
A customer journey map shows how people experience a task over time. It brings their actions, questions and obstacles into one view so a product team can decide where to investigate or improve the experience.
Start with one audience and one question
Choose the user group, task and part of the journey you need to understand. For a team planning tool, you might investigate how a new project lead gets colleagues into the first shared plan.
Include the relevant activity outside your product. The lead may collect requirements in a chat, wait for a manager's approval or copy data from a spreadsheet. Those dependencies can explain a delay that looks like inactivity in your analytics.
Collect actual experiences before drawing the map
Use interviews, observed sessions, support conversations and product events to reconstruct real episodes. Keep a source beside each observation and separate a participant's account from the team's interpretation.
Do not assign an emotion because a user clicked repeatedly or left a page. You may have observed a difficulty, but the reason and the person's feelings need further evidence. Mark unanswered questions on the working map.
Let the journey determine the stages
Lay out individual experiences in time order, then look for common steps and transitions. Group them into stages that make sense for this task. There is no requirement to force every journey into awareness, purchase and loyalty.
Where groups follow substantially different paths, keep separate maps or clear branches. Combining a first-time user with an experienced administrator can hide the very obstacle you are trying to understand.
Describe the barrier precisely
Record what the user was trying to do, what happened and how it affected the task. "Could not invite a colleague because the role required permission from an unavailable administrator" gives the team more to investigate than "Poor onboarding."
Attach relevant evidence about frequency and severity without treating a small research sample as a market-wide percentage. A rare issue that blocks access can matter more than a frequent but minor inconvenience.
Use the map to choose a product decision
For each important barrier, decide whether you understand the cause well enough to propose a change or need more research first. Name the user behavior the change should improve and the person responsible for the next action.
In the planning-tool example, a confusing invitation status could lead to a prototype test of clearer feedback. If access is blocked by the organization's permission policy, the decision may instead involve the administrator workflow. Similar drop-offs can require different changes.
Combine the map with funnel and retention data
A funnel measures movement between defined steps, while a journey map organizes evidence about the experience around them. Neither model establishes a cause just by displaying a drop-off.
Use product data to investigate how widespread a pattern is, then return to user evidence to understand it. Update the map when the experience changes so the team does not prioritize a barrier that an earlier release already removed.
| Step | Evidence to collect | Possible next action |
|---|---|---|
| Create a first plan | How a new lead chooses the first content | Test a relevant starter plan |
| Invite a colleague | Invitation status, permissions and the recipient's experience | Investigate feedback or access rules |
| Use the shared plan again | Whether the team returns when the task recurs | Compare repeat use and interview participants who stopped |
FAQ
How many stages should a customer journey map have?
Use the stages found in the experience you are researching. A narrow onboarding map and a months-long service journey do not need the same structure.
Can a journey map be built from assumptions?
An assumption map can help plan research, but label it clearly. Do not present imagined behavior or emotions as findings about your users.
Who should own the map?
Assign someone to maintain it and involve the teams responsible for the affected experience. Product, design, research, engineering and support may each hold part of the evidence.
Does the map prove why customers leave?
No. It organizes evidence and possible explanations. Validate a proposed cause with suitable research or an experiment before treating it as established.
Sources
Discuss your product's next step
I help define product priorities, plan launches and investigate where users drop out.
