What a journey map is
A customer journey map is a visual account of what a person does, thinks and feels while trying to achieve something with your organisation: buying a coat, renewing a permit, recovering from surgery. It reads left to right through time and top to bottom through layers of detail.
The point of a map is not the artefact. It is that a group of people with different jobs can look at the same thing and agree where the experience breaks. A good map is an argument you can point at.
An experience map, a user flow and an empathy map are different artefacts, and the words get swapped about. The guide Journey map, experience map, user flow or empathy map? lines up six of them, and says which to reach for.
The how-to guides
Six guides go further than this page does, one question each. Start with the one that matches the question you arrived with.
How to create a customer journey map, step by step
Seven steps from a blank canvas to a map your team will argue with, written for a first serious map. With a worked example you can download.
8 min readCustomer journey map examples for six industries
Four worked examples read out of the starter files, a shop, a buying committee, a care pathway and a new hire. Then the two industries with no starter of their own, and exactly which map to adapt for them.
9 min readHow to create a service blueprint, with an example
Four lanes, two lines and one encounter. The method for drawing a blueprint in a room with the people who do the work, and a worked column from the starter template.
8 min readHow to run a journey mapping workshop: a half-day agenda
A timed agenda for three and a half hours, with the people to invite and the people to leave out. Plus what to say when the room stalls on a stage name, and what the map needs from you afterwards.
9 min readCustomer journey stages explained
A stage is a change in what the customer is trying to do, not a department and not a funnel step. How to find the boundaries, how many to draw, what to call them, and three real stage sets quoted column for column.
8 min readJourney map, experience map, user flow or empathy map?
A journey map and its four neighbours: the experience map, the user flow, the empathy map and the user story map. What each one shows, where each one fails, and how to pick one before the session rather than during it.
8 min readAnatomy of a map
Almost every map has the same skeleton.
- Stages run across the top: Awareness, Consideration, Purchase, Onboarding, Loyalty, or whatever words your customers would use. Five to seven is usual. More than nine and you probably have two journeys.
- Lanes run down the side. Each lane answers one question for every stage: what does the customer do, which channels do they touch, how do they feel, what hurts, what do we measure.
- Cards sit in the cells. A card is one observation: a touchpoint, a quote, a number, a pain point.
Customer journey stages explained goes deeper on that top row, down to why one of the starters has no column named Purchase.
Tools differ mainly in how many kinds of lane they support. Journima has fifteen, from plain text to emotion curves, metrics, storyboards, embeds and linked maps. You will not use all of them in one map, and you should not try. The basic customer journey template uses three: customer actions, touchpoints and an emotion curve.
Personas
A persona is a described person who stands in for a group of customers with similar goals and behaviour. Maps without personas drift into describing an average customer who does not exist. Maps with too many personas become unreadable.
Two or three personas per map is the sweet spot. Give each one a name, a goal, and a handful of traits that actually change behaviour (price-led versus brand-led, self-serve versus wants help). Skip demographics unless they matter to the journey.
The emotion curve
The emotion lane is a line that rises and falls across the stages, showing how the person feels. It is the single most persuasive element on a map, because everyone in the room can read it at a glance.
Draw one curve per persona. The gap between the first-time buyer's dip at checkout and the returning customer's flat line is usually where the work is. Use a simple scale: minus two to plus two is enough; nobody can tell a six from a seven. The detailed customer journey template carries a curve across six stages, with a note on the dip at Comparison.
Journey map or service blueprint
A journey map describes the experience from the customer's side. A service blueprint adds what the organisation does to deliver it: frontstage staff the customer sees, backstage processes they do not, and the systems underneath, separated by a line of visibility. How to create a service blueprint has the method, the order to fill the lanes in, and a worked example.
Start with the journey. Add a blueprint when the cause of a pain point is clearly behind the counter and you need operations in the room. In Journima the two share one editor and one set of lane types, so a blueprint can sit nested under a stage of the journey. The service blueprint template has four lanes ready: customer actions, frontstage, backstage and supporting processes.
Evidence
A map drawn from a workshop's collective memory is a hypothesis. A map with interview quotes, support tickets and survey verbatims behind each pain point is a finding. Keep the two visibly different.
In practice: collect transcripts, pull out the observations that support or contradict what is on the map, and attach them to the relevant card. Tools that propose insights from transcripts save hours, as long as a person reviews each one before it is published. Accept, edit, or dismiss; never auto-publish.
Prioritising
Every map produces more pain points than any team can fix. Give each one a stable key (PAT-4, OPP-12) so it can be referred to in meetings and tickets. Score on two axes you agree on, usually customer impact and ease of delivery, and plot them. Let the amount of evidence behind an item show, so loud opinions and quiet data are both visible.
Running the workshop
- Decide the scope. One persona, one goal, start and end points. Write it at the top of the map.
- Draft the stages before the room. Five to seven. You will rename them; that is fine.
- Fill lanes one at a time. Actions first, then channels, then feelings, then pain points. Mixing lanes produces chaos.
- Keep the tool out of the way. One person drives, everyone talks. Autosave and drag-and-drop matter more than any feature list here.
- End with keys and owners. Every pain point gets an identifier and a person who will find the evidence.
There is a longer version of this list. How to run a journey mapping workshop is a half-day agenda, with what to put on the canvas first and how to run it remotely.
Keeping it alive
Most maps die within a month, because updating a slide is painful and nobody owns it. Three things keep a map alive:
- Metrics inside the map. When cart completion sits under Purchase and refreshes daily, people open the map to look at the number.
- The portfolio is the backlog. If the pain points are where the roadmap conversation starts, the map is where it continues.
- Shared views, not exports. Send a link to a saved view rather than a PDF. The link is always current.
Common mistakes
- Mapping the process you wish you had instead of the one customers experience.
- Twelve stages. Split it.
- One average persona.
- Emotion scored to one decimal place.
- No keys on pain points, so nobody can refer to them a week later.
- Exporting to a slide and never opening the tool again.
How to create a customer journey map, step by step is the method written to avoid them, from the first scoping question to the Monday after.
Journima is built around this way of working: an editor that behaves in a workshop, personas with their own curves, a research hub that keeps evidence attached, and a portfolio for the arguments that follow. Sign up if you would like to try it with your team.