In short
A user journey map is a visual timeline of the steps a specific user takes to accomplish a goal, annotated at each step with what they do, what they are thinking, how they feel, which channels and touchpoints they use, and where they encounter friction. Its purpose is to expose the gaps and pain points in an end-to-end experience, particularly the ones that fall between teams or outside the product. A good map is built from research on real users; a map built from assumptions is a diagram of what the team hopes is true.
What it is for
Most teams see the part of the customer's experience that they own. Marketing sees the ad and the landing page; product sees the app; support sees the ticket. The customer experiences all of it as one journey, and the worst moments are usually at the seams: between the promise in the ad and the reality of the signup, between the purchase and the delivery, between the problem and the reply.
A journey map puts the whole sequence on one page, from the customer's point of view, so that the seams become visible and someone can own them. It is a research artefact and a communication tool, and its value is in what it reveals, not in how it looks.
The anatomy
A typical map is a table with time running left to right:
Stages. The broad phases of the journey: becoming aware, evaluating, buying, onboarding, using, getting help, renewing or leaving. The names depend on the product.
Steps or actions. What the person actually does within each stage, specifically: searches for a term, reads reviews, asks a colleague, fills in the form, waits for an email.
Thoughts. What they are asking themselves or telling themselves at each step, ideally in their own words from research.
Emotions. Often drawn as a line rising and dipping across the journey. The dips are where to look.
Touchpoints and channels. Where each step happens: search engine, website, email, phone, app, a shop, a colleague.
Pain points. The specific things that go wrong, are slow, are confusing, or require effort.
Opportunities. What could be changed at each dip, and who would own it.
Maps are drawn for a specific persona or user type, because different users take different journeys, and for a specific goal. A map of "the customer journey" in general is too abstract to reveal anything.
Current state and future state
A current-state map documents what happens today, with all its friction, built from research. It is the diagnostic.
A future-state map shows the journey as it should be after the improvements, and is a design and alignment tool: this is what we are building toward, and here is where each team's work fits.
Start with the current state. Teams that draw the future state first are drawing an aspiration with no evidence that its dips are the real ones.
Building one from evidence
- Choose the persona and the goal. One user type, one end-to-end goal, such as going from first hearing about the product to a successful first month.
- Gather the evidence. Interviews walking users through their actual experience step by step; support tickets and sales call notes; analytics showing where people drop; session recordings of the key flows. The map is a synthesis of these.
- List the steps as users describe them, not as the process document says they should happen. The difference between the two is often the first finding.
- Annotate each step with thoughts, emotions, channels and pain points, quoting users where possible.
- Draw the emotion line and mark the lowest points.
- Identify the seams: where a step crosses from one team or channel to another. These are disproportionately where the dips are.
- Prioritise opportunities by the depth of the dip, the number of users affected, and the feasibility of the fix.
- Share it in a workshop with every team that touches the journey, and assign owners to the dips.
A map for one persona and one goal takes a few days of research and a day of synthesis.
Where journey maps fail
Built in a workshop from assumptions. The most common failure, as with personas. The map records what the team believes, decorated with emoji.
Too broad. Every user, every goal, every channel, on one poster. It looks impressive and reveals nothing.
Product-centric. Steps that start at the homepage and end at checkout, ignoring the search, the recommendation, the comparison and the invoice that surround them, which is where many of the problems are.
A deliverable rather than a tool. Produced, presented, filed. A map should generate a list of owned changes, or it was a drawing.
Never updated. Journeys change as the product and the market change; a map from two years ago describes a different company.
Related tools
A user flow shows the paths through an interface, screen by screen; it is narrower and more precise, and it belongs to the design of a specific feature rather than the whole experience. A service blueprint extends a journey map downward, showing the internal processes, systems and staff actions behind each customer step; it is the tool for fixing the seams once the map has found them. An experience map is a journey map for a broad activity independent of any product. The product design process uses each at a different stage.
When to make one
When customers are being lost somewhere between teams and nobody can say where; when a product is expanding into new stages of the journey, such as onboarding or support; when several teams disagree about what the customer's problem is; or at the start of a redesign, to make sure the redesign targets the real dips. If you would like a current-state map built from your existing customer conversations and data, book a call; it is usually a two-week piece of work with a short list of owned fixes at the end.
Common questions
What is the difference between a user journey map and a user flow?
A journey map covers the whole experience of reaching a goal over time, across channels and including steps outside the product, annotated with thoughts, emotions and pain points. A user flow is a precise diagram of the paths through an interface, screen by screen, for a specific task. The map finds where the experience breaks; the flow designs the fix within the product.
What should a customer journey map include?
The stages of the journey, the specific actions at each step, what the user is thinking, how they feel, the channels and touchpoints involved, the pain points, and the opportunities with an owner for each. It should be drawn for one specific user type pursuing one specific goal, and every annotation should trace back to research.
How do you create a user journey map?
Pick one persona and one end-to-end goal; gather evidence from interviews, support tickets, analytics and recordings; list the steps as users actually experience them; annotate each with thoughts, emotions, channels and friction; draw the emotion line and mark the dips; identify where steps cross between teams or channels; prioritise the fixes and assign owners in a workshop with every team involved.
What is the difference between a journey map and a service blueprint?
A journey map shows the experience from the customer's side. A service blueprint adds the layers beneath it: the front-stage staff actions, the back-stage processes and the systems that support each customer step. The map finds the problem moments; the blueprint shows what inside the organisation has to change to fix them.
Are journey maps worth the effort?
When they are built from real research and produce a list of owned changes, yes; they are among the few tools that make problems between teams visible. When they are assembled from assumptions in a workshop and filed as a poster, no. The effort is in the research, and a map without it is a drawing.
