What is a user journey map?

What does a journey map contain?

Five rows across the stages, and two of them decide whether the map is worth building: questions, and evidence.

Stages. The phases of the decision. For B2B SaaS: problem recognition, solution exploration, vendor comparison, internal justification, and purchase. Internal justification is frequently omitted and is often where deals stall.

Actions. What the person does at each stage, including everything off your site.

Questions. What they need answered before moving on. Unanswered questions are where journeys stop, which makes this the row that generates work.

Friction. What makes each stage harder, drawn from evidence rather than imagination.

Evidence. The source behind every claim in the other four rows, named row by row.

Why do most journey maps fail?

They are built from assumptions. A workshop where the team imagines the buyer produces a map of the team's beliefs. Without voice of customer input and behavioral data, it is fiction with good typography.

They are too abstract to act on. "Consideration" is not a stage anyone can optimize. "Comparing us against two named competitors on a spreadsheet their manager will read" is.

They assume one linear path. Real B2B journeys loop, stall, restart, and involve several people with different questions. A single linear map describes none of them.

They ignore the buying committee. For B2B, the person researching is frequently not the person deciding or the person paying. One map for "the user" hides that the champion needs ammunition for a conversation you never see.

They are produced once and never updated, which turns them into decoration.

How do you make one useful for CRO?

1. Build it from evidence. Sales calls, support tickets, session recordings, search queries, and analytics paths. Every claim traceable.
2. Map one segment at a time. A map covering all buyers describes an average buyer who does not exist.
3. Include off-site stages, since much of a B2B journey happens on review sites, in communities, in AI answer engines, and in internal conversations you cannot observe.
4. Attach each site page to a stage, which immediately reveals two things: stages with no supporting content, and pages written for the wrong stage. A page written for someone ready to buy, receiving traffic from people who are still defining the problem, is a message match failure the map makes visible.
5. Record the questions, and check each one is answered somewhere. Unanswered questions at a stage are the most directly actionable output a journey map produces.
6. Date it, so its age is visible to whoever cites it a year later.

Related terms

Voice of customer · Conversion funnel · Message match · Segmentation analysis · Usability testing

Service: Conversion Rate Optimization.

FAQ

What is the difference between a journey map and a conversion funnel?

A funnel measures how many people pass each measurable on-site step. A journey map describes the whole experience including off-site stages, questions, and emotional state. Funnels quantify, journey maps contextualize.

How long should a user journey map take to build?

Days to weeks, almost all of it gathering evidence rather than drawing. A two-hour workshop produces a map of what the team believes, which is a different artifact answering a different question.

Do you need a journey map for CRO?

Not always. It earns its cost when the problem spans several stages or when different teams hold conflicting assumptions about the buyer. For a single underperforming page, funnel and behavioral data get there faster.