◀ Stage Select World 2 · Stage 2-06

Customer Journey Map

See your product the way your customers experience it

Teams see screens and features; customers experience a journey, with detours, dead ends, and moods. A journey map lays that experience out on one page, so you can find exactly where you delight people and where you lose them.

Ready?

Step-by-step lessons

Master Journey Mapping

Four short lessons: what a journey map is, how it's built, how to read emotions on it, and how to turn it into action.

1

The Core Idea

A customer journey map is a visual timeline of everything a customer does, thinks, and feels while trying to reach a goal with your product, from the moment they first hear about it to the day they become loyal (or quietly leave).

Everyday example, dinner at a restaurant

The restaurant's kitchen tracks its own view: "table 5's food went out in 12 minutes, great." But think about the diner's whole evening: the warm welcome (lovely), the 20-minute wait for a menu (annoying), the delicious meal (delight), and then 15 minutes trying to flag someone down for the bill at the end (leaving on a sour note). The kitchen's metrics all looked fine, yet the guest remembers the frustrating bits and may not come back. A journey map captures that whole lived experience, the parts your internal dashboards never see.

The pizza night story

Imagine ordering pizza through an app. The app team sees five screens working perfectly: browse, customize, pay, track, rate. Each screen passes its tests.

The customer experiences something else: hungry at 8 PM, overwhelmed by 40 menu options, annoyed the address form forgot their street again, anxious for 35 minutes because "tracking" just shows a spinning circle, and finally relieved when the doorbell rings.

Same product, two realities. The journey map documents the customer's reality, because that's the one that decides whether they order again.

Quick check

What is the main thing a journey map adds that a list of app screens doesn't show?

2

The Anatomy of a Map

A journey map is a grid. Columns are stages, the phases of the journey in time order. Rows are swimlanes, the dimensions you track at every stage.

Everyday example, a road-trip diary

Picture a diary of a road trip laid out as a table. Across the top, the columns are each place you stopped: "Home → Gas station → Beach town → Mountain lodge." Down the side, the rows are what you're recording at each stop: what you did, what you were thinking, how you felt, and what went wrong. Read a column top-to-bottom and you get the full picture of one moment; read a row left-to-right and you see how, say, your mood rose and fell across the whole trip. A journey map is exactly this grid, for a customer instead of a traveler.

The typical stages (columns)

Awareness → Consideration → Purchase → Onboarding → Usage → Loyalty

Adapt them to your product, a hospital, a bank, and a game will name these differently.

Actions

What the customer physically does at this stage. "Compares three apps, reads reviews."

Thoughts

What's going through their head. "Is this one trustworthy? Why is it cheaper?"

Emotions

How they feel, plotted as a curve across the stages.

Pain points

Where friction, confusion, or disappointment strikes.

Opportunities

Ideas for removing each pain, the row that feeds your roadmap.

Quick check

On a journey map for a fitness app, where does this entry belong: "Worried the gym plan is too hard, considering quitting"?

3

The Emotion Curve & Moments of Truth

The most valuable line on the map is the emotion curve, how the customer feels, stage by stage. Peaks show what to protect; dips show where customers are silently deciding to leave.

Everyday example, a first date

A first date has an emotional arc: nervous at the start, warming up over dinner, maybe a dip during an awkward silence, then a high if it ends well. And a few instants matter far more than the rest, the moments of truth: the first impression at the door, and especially how someone reacts when a drink gets spilled. A person who laughs it off and helps clean up wins more trust than an evening that was merely smooth and forgettable. Products are the same: how you handle the moment something goes wrong builds more loyalty than a hundred flawless-but-unremarkable sessions. Aim your energy at the deepest dips and the make-or-break moments.

Moments of truth

A few interactions matter far more than the rest, the make-or-break moments where the relationship is decided:

The first impression (does this look worth my time?), the first value (did it actually help me?), the first failure (what happens when something breaks?), and the first support contact (do they care?).

A brilliant recovery at a moment of truth builds more loyalty than ten flawless ordinary sessions.

Quick check

Your food-delivery emotion curve: excited while ordering, neutral at checkout, deep dip while waiting with no updates, relieved at delivery. Where should the team invest first?

4

From Map to Action

A map that hangs on a wall changes nothing. The payoff comes from three habits:

Everyday example, patching the leakiest hole

If your boat is taking on water, you don't repaint the deck or polish the rails, you find the biggest leak and plug it first. A journey map is how you spot the leaks: the deepest emotion dips are where customers are "leaking" out of your product. The discipline is to (1) map the real journey from data, not the one you wish were true, (2) rank the leaks by how many people they sink and how badly, and (3) turn the worst one into a fix you can test. A gorgeous map that doesn't lead to patching a leak is just a painting of a sinking boat.

1

Map reality, not hope

Build the current-state map from research and analytics, interviews, tickets, funnel data. A map based on how you wish the journey went produces a fantasy roadmap.

2

Rank the pain points

Score each pain by how many customers hit it and how badly it hurts (this is opportunity analysis applied to the map).

3

Turn dips into experiments

Each major pain becomes a testable hypothesis: "if we add live tracking, waiting anxiety drops and reorder rate rises."

Quick check

A teammate builds a beautiful journey map entirely from the team's own assumptions in a two-hour workshop, no customer data. What's the biggest risk?

Review the concepts

Journey Map Flashcards

Five cards covering the structure and the key concepts. Click to flip.

Click to flip

Tip: say the answer out loud before flipping.

Explanation

In practice

1 / 5
Did you recall it?
Apply what you learned

Practice Scenarios

15 situations where a journey map earns its keep — reading emotion curves, spotting moments of truth, scoping fixes, and avoiding fantasy maps. Pick the strongest move, then read why the others miss.

Scenario 1easy

Sign-ups for your meal-kit service are healthy, but most customers cancel within the first month.

How does a journey map help?

Scenario 2easy

Your team wants to 'redesign the whole onboarding flow' — six screens, full quarter of work.

What does journey-map thinking suggest?

Scenario 3easy

A customer's very first order on your platform fails to deliver. Support can see it happened but has no special protocol for it.

Why does the journey map say this deserves special investment?

Scenario 4easy

A PM maps a single journey but tries to represent both a first-time casual buyer and a returning power user on the same emotion curve. The curve looks confusingly flat and contradictory.

What's the fix?

Scenario 5easy

Your journey map's emotion curve is high everywhere inside the app, but churn is high. Then someone notes the map only covers on-screen steps — nothing about the 3-day shipping wait or the confusing return process.

What's the gap?

Scenario 6medium

Two pain points show up on the map. Pain A: a mildly clunky settings page, hit by 90% of users. Pain B: a checkout crash, hit by 3% of users but it completely blocks purchase.

How do you decide which to fix first?

Scenario 7medium

Leadership wants to jump straight to designing the "ideal future" journey without mapping how the journey works today.

What's the risk of skipping the current-state map?

Scenario 8medium

The map shows a big emotion peak right after users hit their "first real value" moment. A teammate says "peaks are fine, ignore them — only fix dips."

Is ignoring peaks the right call?

Scenario 9medium

Your map's "opportunities" row is full of vague sticky notes like "improve onboarding" and "make it less confusing."

What turns these into something actionable?

Scenario 10medium

A B2B PM realizes their product's journey involves an evaluator, an approver, and an end-user — each with a totally different experience of the same purchase.

How should the journey mapping handle this?

Scenario 11hard

Analytics show a huge drop-off at one specific step, but the journey map's emotion row for that step just says "neutral." The two don't match.

What should you do?

Scenario 12hard

Your product has a smooth, high-emotion journey — except for one severe dip: the moment a user's free trial ends and they hit a hard paywall with no warning.

Why is this dip especially worth attention?

Scenario 13hard

A stakeholder wants the journey map to include every possible edge case and micro-step, producing a 40-column monster nobody can read.

What's the journey-mapping principle here?

Scenario 14hard

Six months after building a journey map that drove several fixes, the team never looks at it again — even though the product and onboarding have changed a lot since.

What's the issue?

Scenario 15hard

Your journey map clearly shows the deepest dip is during a slow, anxious delivery-wait — but the delivery is handled by a third-party logistics company you don't control.

Does the map still help, even though you don't own that step?

Lock it in

Guess the Term

Read the clues and name the concept. The fewer clues you need, the more points you score.

Round 1 Score 0
Keep it handy

Journey Map Quick Reference

The whole framework on one screen.

The Grid

Columns = stages in time order. Rows = what you track at every stage.

Columns

Stages

Awareness → Consideration → Purchase → Onboarding → Usage → Loyalty.

Rows

Swimlanes

Actions, thoughts, emotions, pain points, opportunities.

Signal

Emotion curve

Peaks = protect. Dips = fix first.

Danger

Moments of truth

First impression, first value, first failure, first support contact.

Rules of Thumb

1

Current state before future state

Map reality from research and analytics first; the ideal journey is a separate map.

2

One persona per map

Different personas travel different journeys, don't average them into mush.

3

Include off-product moments

Waiting, word-of-mouth, support calls, much of the journey happens outside your screens.

4

End with experiments

Every major dip becomes a testable hypothesis, not just a sticky note.

How to Build One

From a blank grid to a roadmap of fixes.

1

Pick one persona & goal

One traveler, one journey, e.g. "first-time buyer completing a purchase."

2

Lay out the stages

The time-ordered phases, including off-product ones (shipping, support).

3

Fill rows from real data

Actions, thoughts, emotions, pains, from interviews, tickets, analytics.

4

Plot the emotion curve

Find the deepest dips and the moments of truth.

5

Rank & turn into experiments

Score dips by reach × severity; make each a testable hypothesis.

Common Mistakes

Where journey maps go wrong.

The fantasy map

Built from assumptions in a workshop, not from real customer data.

Averaging personas

Two personas on one curve flattens the real highs and lows.

Stopping at your screens

Missing off-product moments hides where churn is really born.

Set-and-forget

A map never revisited drifts stale as the product changes.

Notification