Map a user's journey across stages, actions, thoughts and feelings, and mark the pain points and opportunities.
Why it matters
Interviews and personas tell you who your user is. A journey map tells you what they go through over time to reach a goal, including the parts that happen away from your product. It shows the team where things go wrong, which is where design effort pays off. Journey maps are also one of the best tools for getting a whole team (design, engineering, support, management) to see the same picture.
The core idea: one persona, one scenario, over time
A journey map always answers three questions first:
- Who? One persona (or one clear user type).
- What scenario? One goal with a start and an end, such as "Sam collects this month's internet bill from three housemates".
- Current state or future state? A current-state map shows what happens today, based on research. A future-state map shows what you want to happen after your design. Start with current state.
Then the map is laid out as a grid. Columns are stages of the journey, left to right. Rows are lenses:
| Row | What goes in it |
|---|---|
| Actions | What the user does at each stage |
| Touchpoints | Where it happens: app, chat, email, in person |
| Thoughts | What they are thinking, ideally real quotes |
| Emotions | A line rising and falling between positive and negative |
| Pain points | Problems and frustrations |
| Opportunities | Ideas for improvement (added last) |
The emotion line is what makes journey maps memorable. The low points are your pain points, and they become the focus of design.
Worked example: collecting the internet bill
Persona: Sam, the reluctant house bookkeeper. Scenario: collect three shares of a 60 dollar internet bill. Current state.
| Stage | Bill arrives | Work out shares | Ask housemates | Wait | Get paid (or not) |
|---|---|---|---|---|---|
| Actions | Opens email, downloads PDF | Divides by four in calculator | Screenshots bill into group chat | Checks bank app daily | Marks spreadsheet, chases one person |
| Touchpoints | Calculator | Group chat | Bank app | Spreadsheet, chat | |
| Thoughts | "Again already?" | "Easy enough." | "I hope this doesn't sound pushy." | "Did they see it?" | "I'll just pay it myself." |
| Emotion | Neutral | Neutral | Low | Lower | Lowest |
| Pain points | Feels like nagging | No visibility of who has seen it | Absorbs cost to avoid conflict |
Reading the emotion line, the worst moments are not the maths. They are asking and chasing. Opportunities follow directly: let the request come from "the house" rather than Sam, show who has seen and paid without Sam asking, make paying one tap from the request. Each opportunity is tied to a pain point and to evidence from interviews.
How to make one
- Pick the persona, scenario and scope. Write them at the top.
- List the stages from start to end. Five to seven stages is typical.
- Fill in actions and touchpoints from your interview notes.
- Add thoughts, using real quotes where you have them.
- Draw the emotion line.
- Mark pain points at the low points.
- Only now, add opportunities beneath the pain points.
- Share it with someone who was not involved and ask what they would fix first.
Paper and sticky notes work perfectly. Digital templates are available in free whiteboard tools.
Journey maps vs. other maps
- A user flow (lesson 3 of this module) zooms in on the screens and decisions inside one product task.
- An experience map covers a general human activity, not tied to one product.
- A service blueprint adds backstage processes: staff, systems and policies.
Pick the zoom level that matches your question.
Common mistakes
- Mixing personas or scenarios. Two personas on one map produce an average journey that is true for nobody.
- Inventing the content. A current-state map with no research behind it is a guess. Mark assumptions clearly if you must use them.
- Only mapping your product. Many pains happen outside the app (in the group chat, at the bank). Include them.
- Jumping to solutions too early. Fill in what happens first; add opportunities last.
- Making it a poster and forgetting it. A journey map is useful when it drives a decision: pick the top one or two pain points to design for.
Quick recap
- A journey map shows one persona working through one scenario over time.
- Stages run across; actions, touchpoints, thoughts, emotions and pain points run down.
- The emotion line's low points are where design will have the most impact.
- Add opportunities last, each linked to a pain point.
Try it
On the Do tab you will map the current-state journey for your persona and choose the pain point you will design for.