UX glossary
Journey Map
A journey map shows step by step what a person experiences, thinks and feels while working toward a goal with a product or service. It reveals weak spots across channels and departments.
Imagine a gym that can’t figure out why so many new members cancel after two months. Marketing says the ads are working. The front desk says sign-up runs smoothly. The trainers say the equipment is excellent. Every department only sees its own slice. Nobody knows where things actually go wrong for members.
Explained simply
A journey map, often called a customer journey map or user journey map, is a visualization of the path a person takes to reach a goal. It shows step by step what the person does, what they think along the way and how they feel. The Nielsen Norman Group describes it, in essence, as a timeline of actions enriched with thoughts and emotions so that a story emerges.
Think of a travel diary that doesn’t just list the stops but also tells you where things got stressful, where you got lost and where it was truly great. That’s what a journey map does for a product or service.
What a journey map is made of
It starts with two decisions: whose path you’re showing, usually a persona, and which scenario you’re looking at, such as “returning a package for the first time.” Each map shows a single point of view.
Below that come the phases, for example discover, compare, sign up and use. For each phase, you note what the person does, what’s on their mind and at which points of contact, known as touchpoints, they interact with the offering. An emotion curve makes the highs and lows visible. At the end come the opportunities: where can the experience improve, and who owns that?
Related, but not the same, is the service blueprint. It builds on the journey map and also shows which internal processes and teams sit behind each touchpoint.
An example
Back to the gym. Before, all there is to go on are numbers: lots of sign-ups, lots of cancellations. Then the team interviews former members and maps the journey together on a wall. The emotion curve shows a clear low in week two: the introductory session was over, there was no personal plan yet, and many people felt lost among the machines.
The fix costs little: a short appointment after two weeks to put a plan together. Without the map, the problem would have fallen through the cracks between the front desk and the gym floor, because no single department owned it.
Common misconceptions
A journey map is not a pretty poster for a presentation. Its value comes from the team working on it together, based on real data. A map that one person invents alone at their desk mostly shows that person’s guesses. Digital whiteboards like Miro help when the team works remotely. For how journeys connect to the overall experience, see What Is User Experience?
In practice
- Start with a clear scenario. “The entire customer relationship” is too big. A specific goal like “canceling a contract” gets you useful insights faster.
- Back every phase with data. Interviews, support tickets and usage data show what really happens. Be open about where you’re still making assumptions.
- Turn findings into concrete tasks. For every low point, note who will take care of it. Otherwise the map stays an inventory with no consequences.
Related terms
Persona, User Research, Jobs to be Done