Key takeaways
  • A journey map visualises the experience across touchpoints, with emotion, pain points and opportunities.
  • It creates the most cross-functional alignment of any artefact in a single workshop.
  • Avoid the "happy path only" trap; keep it a living artefact, not a wall poster.

Of all the artefacts in modern product work, the journey map is the one that earns the most alignment in the least time. Run a half-decent journey-mapping workshop with the right people in the room (product, design, engineering, customer support, sales) and by the end of the morning the team agrees more about the customer than it has done in six months of standups. Not because the map is correct (it usually isn't, on the first pass) but because the act of building it forces a roomful of people to put their disagreements about the customer onto the wall, in stickies, where the disagreements can be seen and resolved.

I'm cautious about most workshop artefacts. A lot of them are decorative. They're the kind of thing a consultancy produces, photographs nicely, and never gets opened again. The journey map can absolutely be that artefact. But done well — with the right inputs, the right room, and an unflinching look at the bits of the experience nobody wants to put on the wall — it's the closest thing product work has to an X-ray. You can see where the user is in pain. You can see where they nearly leave. You can see where they don't quite get to the value they came for. And once you can see that, the prioritisation arguments stop being about opinions and start being about pixels on a wall.

The anatomy of a journey map.

A journey map is a matrix. Columns are stages of the user's experience (typically four to six) and rows are lenses through which to view each stage. The standard rows are: Actions (what the user does at this stage), Thoughts (what they're thinking: questions, expectations, fears), Emotions (a continuous wavy line plotted across all columns, the row that does the most work), Pain Points (the moments where it goes wrong), and Opportunities (where the team could intervene). Some teams add rows for touchpoints, channels, or internal-team owners. Fewer rows, sharper map.

Diagram · The five rows of a journey map across five stages
A journey map matrix — five stages across the top, five lenses down the side, with an emotion line plotted across all stages A journey map laid out as a matrix. The columns left to right are five stages of a user's experience: Awareness, Consideration, Activation, Use, and Renewal. The rows are five lenses: Actions — what the user does at each stage; Thoughts — what they're thinking; Emotions — a continuous wavy line plotted across all stages, peaking high at Awareness and Activation, dropping sharply at Use, recovering at Renewal; Pain Points — marigold dots placed where the experience breaks (the low point at Use, a second pain point at Renewal); Opportunities — marigold-deep star markers showing places the team could intervene. The emotion line is the dramatic feature of the artefact — its peaks tell you where the product is delighting, its valleys tell you what to fix. The bottom of the diagram carries a caption noting that the emotion line is the row that does the most work. Awareness Consideration Activation Use Renewal ACTIONS what they do THOUGHTS what they think EMOTIONS the line peaks tell you what's working valleys tell you what to fix PAIN POINTS where it breaks OPPORTUNITIES where to act sees an ad · word of mouth reads landing page · pricing signs up · first action weekly use · collaboration invoice · renewal “Could this solve X?” “How long to set up?” “That was easier than…” “Why won't this load?” “Worth renewing?” NEUTRAL ! ! pricing unclear fix load clarify price renewal nudge The emotion line carries the artefact. The actions row tells you what happened. The emotions row tells you what to fix.
Stages across the top, lenses down the side. The emotion line is the row that earns the artefact its keep — its valleys are the prioritisation list for the next sprint.

The emotion row is, by some distance, the most valuable. The other rows describe what happens. The emotion row describes whether what happened was any good. A user can complete a flow without abandoning (the actions row will report a tidy little chain of completed steps) and still have hated every minute of it. The emotion line is what surfaces that. When the line drops sharply between Activation and Use, you know the product over-promises and under-delivers. When it climbs steadily, you know the product gets better the more you use it. The shape of the line is a strategy signal.

Macro maps and micro maps.

There are two scales of journey map worth knowing about, and the failure mode of most teams is to confuse them. The macro map covers months — from a user first hearing about the product, through purchase, activation, daily use, and renewal or churn. It's the map you want for cross-functional alignment, for strategy debates, for onboarding a new exec. The micro map covers a single session: what happens in the ten minutes the user is trying to complete one task. It's the map you want for fixing a specific friction point in a specific flow.

Both are useful. Neither substitutes for the other. The mistake is building a macro map and trying to use it to optimise a checkout funnel, or building a micro map and trying to use it to argue about the renewal product. Pick the scale that matches the question you're trying to answer.

When to map.

Three situations earn the time:

  • Cross-functional alignment. Product, design, support, sales and marketing are using different language about the same customer. The journey map is the artefact that forces a common vocabulary. Worth a day of everyone's time on its own.
  • Churn investigation. You know users are leaving, you don't know where in the experience the wheels come off. A journey map with the emotion line drawn from the support tickets, the NPS comments and a handful of churned-user interviews will show you the drop.
  • New feature scoping. A new capability is being added that touches multiple stages — the journey map shows where it lands in the existing experience, what it disrupts, what it depends on.

What it isn't useful for: replacing user research. A journey map drawn from the room's combined intuition is a hypothesis. It tells you where to look. It doesn't tell you what you'll find. Map first, then interview against the assumed pain points and confirm or correct them.

The "happy path only" trap.

The single most common failure mode of journey-map workshops is mapping only the happy path. The team picks a successful, in-the-zone user and walks them through a successful, in-the-zone session. The emotion line is a gentle hill. The pain points row is empty. The opportunities row is full of marketing taglines. The map is useless — because the entire point of the artefact is to surface what goes wrong, and the team has just produced a sanitised version that surfaces nothing.

Always map at least two journeys: the happy path and the unhappy path. The unhappy path is the user who got stuck, who churned, who complained, who downgraded. The two maps next to each other are dramatically more useful than either on its own. You can see exactly where the experiences diverge, and that divergence is your prioritisation list.

The emotion line tells you more than the actions. The actions tell you what happened. The emotions tell you what to fix.

How to run the workshop.

Three rules for the workshop itself. First, run the first pass in a room with stickies and a wall, not in Miro or Figjam. Digital is faster but it produces sterile maps; physical produces messier, more honest maps because people don't pre-edit their stickies. Digitise it the next day if you want a polished version, but draft on the wall.

Second, include support and sales, not just product and design. Support knows where users complain; sales knows what users were promised. Without them in the room, you'll map a journey that isn't the one your users actually take. Include one or two engineers as well; their constraints quietly shape what's possible in the opportunities row.

Third, time-box ruthlessly. A first-pass journey map should take half a day, not three days. The map you build in half a day, you'll iterate on. The map you build in three days, you'll defend.

Living artefact, not wall poster.

The same rule that applies to personas applies here: a journey map that sits on a wall and never updates is dead. The user's experience changes when the product changes. After a major release, walk the map again. Where did the emotion line move? Did the pain point at Activation disappear (good) or migrate to Use (bad)? If you can't tell, the map isn't earning its keep. Update it or kill it.

A useful tell: after each major release, the PM should be able to point at the map and say "this is the line we moved, this is what we tried, this is what worked." If the map gets quoted in roadmap arguments and release-review write-ups, it's alive. If it doesn't, it's decoration.

How we use this at Product Pieces.

Journey mapping shows up in two of our standard Set Pieces. In Reset the Backlog, we sometimes run a one-morning journey map to find out where the most painful user friction sits before we re-prioritise the queue. In a Discovery Set Piece, the map is the central artefact of the engagement. It's where the customer interviews, the support data, and the analytics get triangulated into a single shared picture. We never deliver a map without a follow-up — a list of prioritised opportunities the team agrees to act on. The map without the action list is a poster; the action list without the map is opinion. Both together is the deliverable.

Next issue: N°25, The Design System. Infrastructure, not decoration.