Define one actor, scenario and goal
Choose one customer, a clear starting point and an outcome—for example, a paid visitor submitting a qualified inquiry or a shopper completing checkout. Do not combine unrelated personas and channels in the same map.
Bring qualitative and quantitative evidence together
Use available funnel and landing-page data with customer feedback, usability observations and stakeholder input. Analytics shows where configured actions drop off, not why. Separate observed evidence from inferences and open questions; a heuristic review does not replace user research.
Make the map operational
Show stages, touchpoints, actions, questions and friction. Pair the map with a prioritized backlog that records evidence, business relevance, next step, likely owner and candidate measure.
Respect limits in identity and attribution
Cross-device activity, consent settings, CRM handoffs, offline sales and attribution can create gaps. Clarify measurable touchpoints, required access and hypotheses that need validation.
Scope handoffs as well as pages
A journey can span paid traffic, email, sales, support and post-submit or order messages. Include handoffs relevant to the selected goal, and state whether needs belong in PPC, CRO, lifecycle or internal operations.
Turn cross-team observations into decisions
Give each priority a decision owner and record dependencies across campaign, content, design, development, operations or sales. Next steps may be fixing a known break, investigating a question or testing a change when traffic and uncertainty support it.
Leave a usable record after the workshop
Document scope, evidence, assumptions, unanswered questions and prioritization logic. Site, campaign, sales or product owners then have a practical handoff and context for later measurement.
Define the next decision explicitly
Close with one or two evidence-backed decisions and questions that need more research. This keeps the work actionable instead of making every observation equally urgent.
Common questions
Is a journey map the same as a funnel?
No. A funnel tracks a defined sequence toward an action; a journey also covers the touchpoints, questions and decisions that can explain funnel patterns.
Do we need user interviews?
Not always. It depends on the question, access to users and existing evidence. Interviews or usability sessions can clarify issues analytics alone cannot.
What does a customer journey map show?
A journey map shows how a defined person works toward a goal across relevant stages and touchpoints. Include what the person does, needs, thinks, and encounters, then mark evidence and unresolved questions. Keep one audience and scenario in focus; otherwise a blended map can hide meaningful differences between journeys. Sources and context
