Customer journey mapping

Customer journey mapping shows the steps a person takes to achieve a goal, what they encounter and where the experience breaks down. Start with one customer goal and map the current experience from its real starting point to an outcome the customer can recognise. Fill the map with customer evidence; a workshop of staff assumptions produces a hypothesis, not a verified account.

Choose a useful boundary

Name the customer group, situation and goal before drawing stages. “Return an online purchase and receive the refund” is more useful than “the returns journey”. It prompts the team to include finding the returns policy, sending the item, waiting and checking whether the refund arrived. This is an illustrative example, not a researched journey.

Set the endpoint by the customer's task. A submitted form, transferred call or closed case may be an internal milestone while the customer is still waiting. Include steps outside your own channel when they affect the goal, such as an email, a shop visit or contact with a delivery partner. If customer groups take substantially different routes, map them separately rather than hiding the differences in one average path.

Build a current-state map from evidence

Gather accounts of recent journeys and, where appropriate, observations and service records. Ask what prompted the task, what the person did next, what they expected and how they knew whether it worked. Service records can help locate contacts and delays, but may miss work the customer did before contacting you. Mark gaps and disputed explanations rather than filling them with a tidy story.

A compact map can use these rows:

Keep the timeline readable. Show a detour or exception when it changes the experience; a failed delivery may create a different route from an ordinary return.

Use labels consistently: a stage is a phase or group of steps, while a step is one action. A touchpoint is where an action meets a channel, such as downloading a form online; a channel is how someone interacts with a service, such as through an app, call centre or face-to-face. A need is the specific outcome sought at a step, not the overall goal.

Record how the user feels at each stage, alongside expectations and pain points; positive moments matter too. A delight point is a highlight that creates a positive emotion, while a pain point is an issue likely to create negative emotions or perceptions. Distinguish these experiences from a team's interpretation of their cause.

Research can combine quantitative data about what users do with qualitative evidence about how they think and feel. Define the user from research, including motivations, barriers or concerns and what happens before and after the interaction. This helps keep the map grounded in the person's context, not just their contact with the service.

Key Steps in Building a Current-State Customer Journey Map

Customer Journey Timeline Example: Online Return Process

Make the map readable

Choose a layout that makes sequence and variation easy to scan; a journey does not have to be shown as a straight line. Swim lanes or similar layouts can organise information across the journey, while a grid or infographic can present a visual timeline. Sticky notes or a cloud-based tool such as Miro are options; the format matters less than a shared, readable view.

Read the map as a decision tool

Look for an unanswered customer need, a handoff where context is lost, or a point where the person believes the task is complete but the service has more steps to perform. Discuss what the evidence shows before naming a cause.

If customers contact support after lodging a return, the map may reveal uncertainty about status. It does not establish whether the cause is unclear wording, a processing delay or a failed refund.

Give each candidate issue an owner and a next check. Some changes may involve content; others require a process or system investigation. A service blueprint can connect a troublesome customer stage with the teams, systems and rules behind it.

Use the map to focus discussion on where users get stuck, confused or frustrated, then identify opportunities and prioritise work according to its impact on the user experience. A map can also show how several products, agencies or policies combine in one experience, helping teams understand where their work fits.

Pros and Cons of Using Customer Journey Maps in Public Services

Use the right map for the next question

A journey map shows what a customer experiences while reaching a goal. An internal process diagram shows how work moves between people or systems. Start with the journey when the customer problem is unclear; add the process view to investigate an operational cause.

A future-state map can describe a proposed experience after the current one is understood. Treat it as a design to check, not evidence that the service already works that way. After a change, revisit the same customer goal and check both the result and the work required to reach it. Update the map when new evidence changes the account.

Current-State vs Future-State Journey Mapping

Share the map with the team

Keep the map where the team can refer to it and walk stakeholders through the journey, rather than treating it as a workshop artefact. A shared view can build empathy, align teams and help break down organisational silos. It can also show stakeholders the part they play in a complex service experience.