Mapping user journeys teams actually use
Journey maps that drive decisions instead of gathering dust.

Zander Whitehurst
9 min read
Journey maps have a reputation problem. Many teams make one, print it, stick it on a wall and never look at it again. It becomes a beautiful artefact that changes nothing.
I have made a few of those wall decorations myself. One of them was nearly three metres long and had colour coded emotional curves. It looked incredible. It influenced precisely zero decisions. The journey maps that actually work are usually much simpler and much more focused.
What a journey map is for
A journey map shows the steps someone goes through to achieve a goal, along with what they think, feel and struggle with along the way. Its purpose is to help teams see the experience from the user's perspective and decide where to improve it.
If a journey map does not lead to decisions, it is not doing its job.
Start with one goal and one person
Trying to map everything at once creates maps that are too big to be useful. Pick one specific goal, such as "set up a new team account", and one type of person, such as "a team lead at a small company".
Focus makes the map useful. You can always create more maps later.
Base it on evidence
The best journey maps come from research, not assumptions. Use interviews, support tickets, analytics and usability tests to understand what really happens.
If you do not have research yet, you can create an assumption map with your team. Just label it clearly and treat it as a set of hypotheses to test, not a description of reality.
Map the stages and steps
Break the journey into broad stages, such as discover, sign up, set up, first use and ongoing use. Within each stage, list the specific steps people take.
Include steps that happen outside your product. People search, ask colleagues, read reviews and switch between tools. Those moments often shape the experience as much as anything you design.
Capture thoughts, feelings and pain points
For each stage, note:
- What people are doing. The actions they take.
- What they are thinking. Their questions and expectations.
- How they feel. Confident, confused, frustrated or relieved.
- Pain points. Where things go wrong or slow down.
Use real quotes wherever possible. A quote like "I had no idea whether it had worked" says more than any summary.
Highlight opportunities
This is the most important part, and the part many maps skip. For each pain point, note an opportunity to improve. Then prioritise them based on how much they affect people and how easy they are to address.
The map becomes a tool for deciding what to work on, not just a picture of the current state.
Keep it alive
Journey maps go stale when they live in a forgotten file. Keep yours somewhere the whole team uses and update it as you learn more. Refer to it in planning sessions and design reviews.
One trick I love: when a team ships an improvement, mark it on the map. Seeing pain points disappear over time is genuinely motivating, and it reminds everyone why the map exists.
Make it collaborative
Build journey maps with your team rather than presenting a finished one. Engineers, PMs, support and sales all see different parts of the experience. When they help create the map, they understand it and care about it far more.
A two hour workshop with sticky notes, real research and the right people often produces a more useful map than weeks of solo work.
Start small
Pick one journey your users struggle with. Map it in a simple table with stages across the top and actions, thoughts, feelings and pain points down the side. Add opportunities underneath.
It does not need to be beautiful. It needs to help your team make a better decision this month. That is what makes a journey map worth making. We practise turning research into decisions like this in the AI Product Design Bootcamp.
Memorisely