Skip to main content
Your product is one stop on a much longer journey. Before users arrive, they have a problem. They search for solutions, evaluate options, sign up, onboard, use the product, run into friction, maybe get help, maybe churn. A user journey map makes that full picture visible - including the parts that happen outside your product entirely 🗺️

​
What it is

A user journey map is a visual representation of the steps a user goes through to accomplish a goal, from first awareness through to the outcome they were trying to achieve. It typically captures:
  • Stages - The high-level phases of the journey (Awareness, Consideration, Onboarding, Activation, Retention, etc.)
  • Actions - What the user does at each stage
  • Thoughts - What they’re thinking or trying to figure out
  • Emotions - How they feel (frustrated, confused, delighted, anxious)
  • Touchpoints - Where they interact with your product, team, or brand
  • Pain points - Where things break down or fall short

​
Why it’s useful

The map forces you to see the experience from the customer’s perspective, not the product’s. Internal teams naturally think in features and screens. Journey maps think in goals and feelings. Two things consistently surface that other research methods miss: The gaps between touchpoints - What happens between your onboarding email and the user’s first login? Between support ticket resolution and the user returning to the product? These gaps are often where churn quietly happens. The emotional arc - A user can complete every step of your onboarding successfully and still feel overwhelmed or uncertain. The functional journey and the emotional journey aren’t always the same 😬

​
Building one

Journey maps are most useful when built collaboratively - with your product trio, CS, and ideally some customer quotes or research embedded directly in the map. A common mistake is building a journey map from internal assumptions rather than customer research. The result looks complete but reflects how the team thinks the journey works, not how it actually does. Ground every stage in something a real customer said or did. Tools like Miro, FigJam, or even a well-structured spreadsheet work fine. The format matters less than the rigour of the underlying research.

​
Journey map vs. story map

These two are often confused. A story map is a planning tool - it organises features and user stories for delivery. A journey map is a research and empathy tool - it captures the customer’s experience to surface opportunities. Both are useful. They answer different questions 💡 Lesson learned: the most valuable moment in any journey mapping session is when someone from CS points at a stage and says “this is where we get the most calls” and the PM realises that stage has never been on anyone’s roadmap 👀