A user journey map traces a persona's full path toward a goal — every step, thought, and emotion — not just the screens inside one product. It often reveals that the real problem is happening before or after the app even opens.
| Part | What it captures |
|---|---|
| Stages | The broad phases of the journey — e.g. Awareness, Research, Purchase, Onboarding, Ongoing use |
| Actions | What the user is actually doing at each stage |
| Thoughts | What's going through their mind — questions, doubts, expectations |
| Emotions | Often plotted as a simple line — confident, confused, frustrated, satisfied — that rises and falls across the journey |
| Pain points | Where the emotion line dips — the specific moments worth fixing first |
| Opportunities | Ideas for improving each pain point, added once the map is complete |
A team focused only on their own app's screens can perfect every one of them and still lose users — because the real friction was in the step before ("I couldn't figure out which plan to buy from the marketing page") or after ("I got the confirmation email but couldn't find my way back to actually use the product"). The journey map forces the full picture into view.
For a small project, this doesn't need special software — a shared document with one column per stage and a row each for actions/thoughts/emotions covers the essentials. The value is the exercise of walking through the whole journey in order, not the polish of the artifact.
One persona per map
Journey mapping pairs naturally with the previous persona lesson — map the journey for one specific persona at a time, not a vague "the user" that blends several different real user types together.