User journey mapping is the practice of laying out, step by step, how a person goes from first hearing about your product to getting value from it, including what they do, think and feel at each stage. A good map makes the experience visible to everyone on the team, and points at the moments that most need fixing.
Most journey maps are built from workshops and interviews. This guide covers what user journey mapping means, the stages and parts of a map, how to build one step by step, the tools teams use (from whiteboards and Figma to analytics), and how to check a map against real behaviour so it doesn't become a poster of assumptions.
What does user journey mapping mean?
A user journey map is a visual timeline of one persona's experience while trying to achieve one goal. It usually includes:
- Stages: the phases of the journey, such as discover, evaluate, sign up, onboard, use, renew.
- Actions: what the person does at each stage.
- Touchpoints: where they interact with you: website, product, email, support, sales.
- Thoughts and emotions: what they're trying to figure out and how they feel.
- Pain points and opportunities: where things go wrong, and what you could do about it.
In UX, journey maps help designers see the experience end to end rather than screen by screen. In product and growth, they connect marketing, product and success around one shared picture. See customer journey in the glossary.
User journey map vs customer journey map vs user flow
- A user journey map covers one persona's experience over time, across touchpoints, including emotions.
- A customer journey map is often broader: the whole relationship, including purchase, billing and renewal. The terms are frequently used interchangeably.
- A user flow is narrower and more technical: the screens and decisions within one task, such as signing up.
Start with the journey map to find the problem stage, then use a user flow to fix the steps inside it.
The stages of a typical SaaS user journey
| Stage | Typical actions | Questions to answer |
|---|---|---|
| Discover | Searches, asks an AI assistant, reads a comparison | Where do people first hear about us? |
| Evaluate | Reads pricing, docs, case studies; starts a trial | What convinces them, and what worries them? |
| Sign up | Creates an account, verifies email | Where does sign-up lose people? |
| Onboard | Creates first project, connects data, invites a colleague | How long until first value? |
| Use | Uses core features repeatedly | Does a habit form? |
| Expand or renew | Upgrades, adds seats, renews | What triggers growth? What precedes churn? |
How to create a user journey map, step by step
- Choose one persona and one goal. "Operations lead at a 20-person company evaluating a project tool" is specific enough to map.
- Gather evidence. Interview five to ten recent customers and five people who didn't buy. Pull behaviour data for the same stages.
- List the stages and actions in order, as the customer experiences them, not as your org chart is arranged.
- Add touchpoints for each action, including ones you don't control, such as review sites or AI assistants.
- Add thoughts and emotions from interviews, in the customer's words where possible.
- Mark pain points and size them with data: how many people drop out at each stage?
- Pick the biggest opportunity, assign an owner and decide how you'll measure improvement.
- Revisit quarterly. Journeys change as the product and market change.
Validate the map with behaviour data
Workshops produce maps of what the team believes. Behaviour data shows what actually happens. Three checks turn a map into evidence:
Measure each stage as a funnel
Turn the stages into events (Viewed pricing, Started trial, Created project, Invited teammate, Paid) and build a funnel that follows each person in order. The step with the biggest drop is the stage that most needs work, whatever the workshop concluded.
Read real paths
Look at the events people actually performed before a key moment. You'll often find steps the map missed, such as people visiting docs before starting a trial, or returning three times to pricing before paying.
Segment the journey
The journey for visitors from a comparison page may look nothing like the journey for visitors from social media. Break the funnel down by source, plan or company size, and consider separate maps where they differ.
Our guides to user behavior analytics and micro conversions go deeper on these methods.
User journey mapping tools
Teams usually combine three kinds of tool:
- Whiteboards and design tools such as Figma, FigJam or Miro, for drawing the map with the team. Templates help, but the conversation matters more than the format.
- Research tools for interviews and surveys, to capture thoughts, emotions and reasons.
- Product analytics for the quantitative layer: funnels, paths, cohorts and timelines that size each stage and validate the map.
The design tool holds the picture; analytics keeps it honest.
An example map, condensed
Persona: operations lead at a 20-person agency. Goal: replace spreadsheet-based project tracking.
- Discover: asks an AI assistant for project tools for agencies; reads two comparison pages. Thinking: "Which of these won't need a week of setup?"
- Evaluate: reads pricing twice and the docs once; starts a trial. Worry: per-seat cost as the team grows.
- Onboard: imports a client list, creates a first project. Pain point: the import step fails on a date format; 30% of trial users stop here.
- Use: invites three colleagues in week one. Feeling: relief when the weekly status email replaces a meeting.
- Renew: upgrades when the team passes ten active users.
Biggest opportunity: the import step. Owner: onboarding team. Measure: the funnel from Started trial to Created project, before and after. (An illustrative map; user onboarding and time to value in the glossary cover the stages it highlights.)
The discovery stage is changing
A growing number of journeys now start with a question to an AI assistant. The assistant reads your pages from its own servers, then the person clicks through, often without a referrer. On a journey map, that's a touchpoint most teams can't yet see. If evaluation increasingly happens inside ChatGPT or Perplexity, your map should show it. See AI visibility and ChatGPT traffic in Google Analytics.
Common mistakes
- Mapping the ideal journey instead of the real one.
- Too many personas at once. One map per persona and goal.
- No numbers. Without data, every stage looks equally important.
- No owner. A map without an owner for its biggest opportunity becomes wall art.
- Ignoring the account. In B2B, the journey involves several people; map the buying group, not just the first user.
Mapping the journey with LogZuno
LogZuno supplies the behaviour layer for your map:
- Web analytics for the discover and evaluate stages, with channels including AI assistants, and visitors counted as people only after a real interaction.
- Events for sign-up, onboarding and use, sent from your backend or app.
- Funnels that follow each person through your stages, per user or per account.
- User timelines to read the real paths behind the numbers.
- Cohort retention for the use and renew stages.
See product analytics, LogZuno for product teams, and customer behavior analysis.
Key takeaways
- A user journey map shows one persona's path to one goal, with actions, touchpoints, emotions and pain points.
- Build it from interviews and data, stage by stage, and choose one opportunity to act on.
- Validate every stage with per-person funnels, real paths and segments.
- Include new touchpoints, such as AI assistants, that traditional analytics can't see.