A customer sees one task even when your organisation sees several departments. Booking a service might involve a website, a confirmation email, a phone call and an in-person visit. A journey map makes those transitions visible. It is useful when it helps identify a specific obstacle and the people needed to improve it.
GOV.UK's service standard emphasises testing the parts of a service people interact with, including offline material. That perspective applies well to a small business examining its own customer experience. The mapping exercise below is an editorial method, not a complete research programme.
Choose one journey and one customer situation
Avoid beginning with “the entire customer lifecycle.” Choose a bounded task, such as rescheduling a repair visit after a customer becomes unavailable. Define where the journey starts and what successful completion means. The map then has a purpose beyond drawing every possible interaction.
Describe relevant circumstances without inventing a detailed persona. The customer may be using a phone, have limited time and need confirmation that the technician will receive the change. Those circumstances matter to the task. Unsupported demographic details can distract from the operational problem.
Trace the visible steps
List what the customer does: finds the confirmation, looks for rescheduling instructions, opens the booking page, calls support and receives a revised time. Add the information they need at each step. Which reference number is required? Is it available in the same message? How do they know the change is complete?
Observe the journey or collect accounts from people who recently attempted it. Mark assumed steps as assumptions. A staff workshop can reveal internal process knowledge, but it does not show exactly how customers experience the task. Keep a way to distinguish evidence from the team's best guess.
Add the internal handoffs
Under each customer step, record the team or system that supports it. The website may accept the request, support may confirm it and scheduling may update the technician's route. Note where information changes format or moves between systems. These boundaries are useful places to investigate inconsistency.
In an illustrative repair journey, support updates the booking record but the technician already has a printed route. The customer receives confirmation while the technician still expects the original visit. The map exposes a missing handoff rather than merely showing that customers dislike rescheduling.
Identify moments of uncertainty
Ask what the customer knows after each step. A submitted form may display “Success” without explaining whether the appointment has changed or only the request has arrived. A caller may receive a verbal assurance but no revised confirmation. Those gaps can create repeat contact even when the internal task is progressing.
Use a short problem statement: “Customers cannot tell whether the revised appointment is confirmed.” Then propose possible responses, such as a clearer status message and a checked notification to the technician. Avoid committing to a new feature before examining whether a simpler process change would solve the same problem.
- Bound the map around a real task and clear completion point.
- Record customer actions and required information.
- Mark observed steps separately from assumed ones.
- Show internal ownership and system handoffs.
- Identify uncertainty, repeated information and avoidable waiting.
- Choose one problem and test an improvement with users.
Keep the map connected to decisions
Assign the chosen improvement to someone who can coordinate the relevant teams. Check the full journey again after the change, including messages and offline actions. Improving one page may not help if the next handoff still fails. Record what changed and what remains unresolved.
A journey map is a model, and different customers may take different routes. It cannot capture every experience on one sheet. Its value is helping people see beyond their own stage of the process and agree a practical improvement to the task the customer is trying to complete.
Sources and further reading
This original guide was prepared with AI assistance. Examples are illustrative. The edition date is an assigned date in this 2026 catalogue. See our editorial policy and report a correction.