Customer Journey Map: What It Is and How to Build One
Basics4 minInnovialabs editorial team
In short
A customer journey map (CJM) is a visual of everything a customer goes through to reach a goal with your product: stages, actions, touchpoints, thoughts, emotions and pain points. Its purpose is to show where the experience breaks so the team knows what to fix first.
What a CJM is
A customer journey map (CJM) shows, step by step, how a specific type of customer moves toward a goal: from first realising a need to getting the result and coming back. It combines what the customer does, where they interact with the company, and how they feel at each moment.
The map is useful because no single team sees the whole journey. Marketing sees the ad, sales sees the call, developers see the app, support sees the complaint. A CJM puts all of it on one page from the customer's side.
Key elements
| Element | What it describes | Example (ordering furniture online) |
|---|---|---|
| Persona and goal | Whose journey and why | A young family furnishing a new flat |
| Stages | Large phases of the journey | Search, compare, order, wait, delivery, use |
| Actions | What the customer does | Browses catalogue, measures the room, calls the store |
| Touchpoints | Where they interact with you | Website, Instagram, phone, courier, SMS |
| Thoughts and questions | What is on their mind | "Will it fit? When exactly will it arrive?" |
| Emotions | How they feel, often as a curve | Excited, then anxious while waiting |
| Pain points | What frustrates or blocks them | No exact delivery time, unclear assembly |
| Opportunities | Ideas for improvement | Delivery time slots, assembly video |
Stages should come from the customer's point of view ("compare options"), not from internal departments ("lead qualification").
How to build a CJM step by step
- Choose one persona and one goal. A map for "all customers" becomes vague. Start with your main persona and a concrete scenario.
- Set boundaries. Decide where the journey starts and ends: from the first search to the first purchase, or including repeat orders and support.
- Collect data. Interviews, support tickets, call recordings, reviews, analytics, and simply going through the journey yourself. Without data, the map shows the team's opinion.
- Define stages. Usually several large phases are enough.
- Fill actions and touchpoints for each stage, including offline ones such as calls and delivery.
- Add thoughts and emotions. Use real quotes where possible. Draw the emotional curve: highs and lows show where attention is needed.
- Mark pain points. Be specific: not "bad delivery", but "the customer does not know the delivery day and has to call twice".
- Find opportunities. For each serious pain point, write one or more improvement ideas.
- Review with the team across departments: everyone usually adds something the others did not know.
A whiteboard, a spreadsheet or a collaborative tool like FigJam or Miro works equally well. The format matters less than the content.
From map to design improvements
A CJM that ends as a nice poster is wasted. Turn it into work:
- Prioritise pain points by how often they occur and how strongly they affect the goal. Low emotional points right before purchase or payment are usually the most costly.
- Group fixes by type: interface changes, text and communication, process changes, new features.
- Write concrete tasks. "Show available delivery slots on the order page" instead of "improve delivery".
- Assign owners. Many fixes cross teams: a delivery notification touches design, development and logistics.
- Measure. Choose an indicator for each improvement, such as fewer calls about order status or more completed checkouts, and compare before and after.
- Update the map after changes and new research.
Common mistakes
- Building the map only from internal opinions.
- Mixing several personas and scenarios in one map.
- Describing the company's process instead of the customer's experience.
- Ignoring offline touchpoints such as calls, couriers and physical stores.
- Listing pain points without turning them into tasks.
- Creating the map once and never revisiting it.