Customer Journey Mapping

Customer Journey Mapping (CJM) helps you understand how customers experience a service, from the moment a need arises until their task is completed. The aim is to identify unnecessary obstacles and decide what needs to improve. But a map is only useful when it reflects real experiences and leads to action.

What seems logical from inside a business may be unclear to the customer. You know the product, terminology and routines. The customer may simply be trying to find a price, book an appointment or get an answer to a question.

Start by challenging what you take for granted. Try the service from the customer’s perspective, but also investigate how other people actually use it. You cannot set aside everything you know, and empathy alone will not tell you where people get stuck.

What is Customer Journey Mapping?

A customer journey map shows the steps a customer or user takes to reach a goal. It may include websites, phone calls, emails, face-to-face meetings and transitions between them. Nielsen Norman Group describes journey maps as a representation of actions, thoughts and emotions throughout a specific experience, with opportunities for improvement.

A simple mapping exercise should answer these questions:

  • Whose journey are you mapping? What needs, circumstances and expectations does the user have?
  • What is the user trying to achieve? Describe one specific task or situation.
  • What happens along the way? Which steps and touchpoints does the user encounter?
  • Where do obstacles arise? What causes uncertainty, waiting, errors or extra work?
  • What needs to change? Who is responsible, and how will you assess the impact?

The method can be used in online shops, cafés, advisory services and public services. A user journey does not have to involve a purchase or follow a straight line. People switch channels, go back and ask others for help.

An example: Free coffee with an unnecessary obstacle

A café I visited offered free coffee refills. That was good service in principle, but the coffee pot was positioned just before the till. To get a refill, customers had to squeeze between people queuing to pay or wait until the area was clear.

From the café’s perspective, the offer was available. From the customer’s perspective, it was harder to use than it needed to be.

One possible improvement would have been to move the coffee pot somewhere easier to reach. But even that change needs to be assessed in practice: Is the location safe, does it work for staff, and does it actually make getting a refill easier?

The point is not that the café needs an extensive analysis. It is that a good intention can lose its value when nobody considers the entire task from the customer’s perspective.

A barista pouring milk into a cup of coffee to create latte art.
Small gestures can make a difference to the customer experience. Read What Is “That Little Extra”?.

How to create a customer journey map in six steps

1. Choose one user group and one task

Define what you want to understand. “Our customers” is too broad. “A first-time customer booking an appointment on their phone” gives you a clearer starting point.

Describe relevant differences in needs, experience and circumstances. Personas can be useful when they are based on research, but a name, age and photograph are not enough. Do not assume that all young people prefer self-service or that all older people need help.

2. Gather evidence before drawing conclusions

Talk to users about specific experiences, observe how they complete the task, and review customer service enquiries. Usage data can show where people stop, while conversations and observations can help you understand why.

You can start by creating a provisional map with colleagues. Clearly distinguish between what you know, what you assume and what needs further investigation. A map based on internal assumptions should not be presented as evidence of the customer experience.

3. Map the entire journey

Start where the need arises and follow the task through to completion. Include preparation, waiting and follow-up, even when these happen outside your organisation’s own channels.

Record what the user does at each step, what information they need and how they move to the next stage. An application may be easy to submit while gathering the supporting documents is difficult.

4. Identify obstacles and investigate their causes

Distinguish between what you observe and how you explain it. If many people abandon a form, that does not necessarily mean the form is poorly designed. They may lack information, want to compare alternatives or have discovered that the service does not meet their needs.

Pay particular attention to unclear terminology, repeated data entry, unexpected costs and transitions where users do not know what happens next. Also record what works well, so improvements do not undermine it.

5. Map questions and reactions

What questions does the user need answered along the way? When do they feel reassured, uncertain or frustrated? Use specific feedback, and distinguish between what users say and your interpretation.

Someone may complete a task and still be unsure whether they have done it correctly. Completion alone does not tell you whether the service provides enough guidance.

6. Choose actions, assign responsibility and measure results

Prioritise obstacles according to their impact and how many people they affect. An error affecting a few people may matter more than a minor irritation affecting many. Also consider what is feasible and who needs to be involved.

For each action, describe the problem, propose a change, assign someone responsibility and decide how to assess its impact. Consider testing a simple version before building a larger solution.

Time spent, errors, completion and the need for help can all be useful measures. Assess them together: Fewer customer service enquiries are not necessarily an improvement if getting help has also become harder.

Illustration of a balance scale comparing revenue and growth with the workload of support, operations, onboarding and maintenance.
A difficult customer journey can create extra work for the business too. Read Why Profitable Services Lose Money.

NAV: Online information is not the same as guidance

In my experience with NAV, information about most things is available online, but finding what applies to my situation, understanding the requirements and knowing what to do next can feel like navigating a maze.

This illustrates why mapping should start with the user’s task. Someone may need to find out whether a scheme applies to them, understand which documents are required and follow up on their case afterwards. Each page may be clear on its own while the route between them is difficult to navigate.

A customer journey analysis can help identify these transitions. But the map does not change the rules or how the service is organised. The findings must be used by people with the responsibility and authority to make improvements.

Common mistakes in Customer Journey Mapping

  • Drawing the desired experience as though it already exists. Distinguish between the current situation and your proposal for a better service.
  • Combining different needs in one map. Create separate journeys when the differences matter to the solution.
  • Mapping one channel and overlooking the rest. The transition from a website to a phone call or an in-person meeting may be where the problem occurs.
  • Guessing how users feel. Use conversations and observations, and flag uncertain interpretations.
  • Stopping when the map is finished. Prioritise actions and follow up to see whether they work.

From customer journey maps to better services

You do not need to start with a large project. Choose one task that often causes questions, errors or unnecessary waiting. Follow users through it, and bring together the people responsible for its different parts.

Some problems can be solved with a clearer button label or better placement of information. Others require changes to systems, routines or collaboration. Mapping helps you distinguish between them.

I notice how easy it is to write headings that seem clear when I know the content. When I revisit an older article, I may discover that the connections were less obvious than I thought. The same blind spot can arise when we develop products and services.

The value of Customer Journey Mapping lies in the improvements users notice: fewer obstacles, clearer answers and an easier path to completing their task.

Leave a Reply

Your email address will not be published. Required fields are marked *