A customer journey map is a visual account of the steps a person takes to achieve a specific goal with a product or service. It shows their actions, questions, touchpoints, and friction across time. The map helps a team see the experience from the customer's point of view and decide what to improve first.
What goes into a customer journey map?
Choose one customer type and one goal before drawing stages. A map of every possible person and every interaction becomes too broad to guide a decision. The stages should follow the person's actual path rather than a company's internal department names. An early sketch may cover recognizing a need, comparing options, signing up, first use, and getting help, but research may reveal a different sequence.
For each stage, record what the person tries to do, the channel or person they meet, what they need to know, where they pause, and the evidence behind that observation. Distinguish direct customer evidence from the team's assumptions. The UK Government Service Manual recommends gathering several users' experiences before consolidating them into an experience map.
- Customer goal and the boundaries of the journey.
- Stages, actions, and online or offline touchpoints.
- Questions, expectations, and moments of friction.
- Evidence source, owner, and a possible improvement at each important point.
How do you use the map without turning it into decoration?
Look for a point where an unresolved question prevents the next action. Check how often the issue occurs and whether it affects the outcome the customer wants. Then choose one change that the team can test, with an owner and a signal that would show improvement. A map should be revisited when the offer, channel, or customer evidence changes; it is not a permanent portrait of every customer.
A journey map describes the customer's experience. A service blueprint adds the behind-the-scenes systems and operations that enable it. If a failure is caused by handoffs or internal processes, a blueprint may be the better follow-up. Record any consequential choice in a decision log so the reason for the fix is not lost.
What are common mistakes?
Do not infer feelings from analytics alone or present a single interview as a universal pattern. Avoid treating purchase as the end of the journey when setup, use, support, and renewal determine whether the customer achieves the goal. Resist assigning a numerical score to each touchpoint without a clear definition. The useful output is a prioritized question and a testable change, not a perfectly polished poster.
A simple journey for a small business software trial
A founder wants to let a five-person team try a scheduling tool. They see a search result, compare two pricing pages, create an account, invite teammates, and attempt a first booking. In interviews, several trial users say they are unsure whether invited teammates need a paid seat. The map marks the pricing comparison and invitation screen as touchpoints, notes the unanswered question, and links to the interview notes. The team tests a clearer seat explanation next to the invite action and watches whether more new accounts complete a team booking. That test addresses one observed obstacle; it does not assume every trial user has the same concern.