Journey Map
A journey map is a visualization of the process a person goes through to accomplish a goal, laid out as a timeline of stages across channels and touchpoints. Alongside each stage it records what the person does, thinks and feels. This lets a team see the whole experience from the customer's side, including the parts no single department owns, and spot where it breaks down.
How a Journey Map Works
Nielsen Norman Group describes five core components:
- Actor. The person whose journey is shown, usually a persona. One map holds one point of view, so the story stays clear.
- Scenario and expectations. The situation the map covers and the goal the actor is trying to reach, with what they expect to happen.
- Journey phases. The high-level stages, for example discover, try, buy, use and seek support.
- Actions, mindsets and emotions. What the actor does in each phase, what they are thinking and how they feel, often drawn as an emotional line that rises and falls.
- Opportunities. Insights on where to improve the experience and who in the organization owns each fix.
A journey map is only as reliable as the data behind it. Maps built on interviews, support tickets and behavioral data from user research show the real experience. Maps built from internal assumptions mostly show what the team already believes, and are best labeled as hypotheses to check.
Why Journey Maps Matter
Products rarely fail at one screen. Customers move between marketing pages, sales calls, onboarding emails, the product itself and support, and each is usually owned by a different team. A journey map puts all of these on one page, which makes handoff gaps visible and gives teams a shared reason to fix them. For product managers it also helps prioritize: the stage where emotions dip hardest and most customers drop away is often a better investment than the feature that is loudest internally.
To see how behavioral data can feed this kind of analysis, read about automating user journey maps from behavioral data.
Journey Map Example
A team selling bookkeeping software to small accounting firms maps the journey of an office manager adopting the tool. The phases are: hear about it from a peer, start a trial, import client data, invite colleagues, and get help. Interviews show confidence is high during the trial but drops sharply at import, where the manager has to reformat spreadsheets and wait two days for a support reply. The opportunity is clear and cross-team: the product team builds a guided import, and support adds a same-day import help slot during trials.
Journey Map vs. Related Maps
- User flow. Zooms in on the steps of one task inside one product, usually minutes long. A journey map zooms out across channels and days or weeks.
- Service blueprint. Shows the internal people, systems and processes that support each stage of the journey, the backstage view.
- User story map. Arranges planned user stories along a user's workflow to plan what to build and release. It is a delivery planning tool, while a journey map is a discovery and understanding tool.