A customer journey map follows a person’s attempt to achieve a goal across time and touchpoints. It can reveal how a service feels when the customer moves between teams, channels, and waiting periods that the organisation manages separately.
A delivery company may regard ordering, dispatch, and customer support as three successful processes. A customer waiting for an unexplained delay experiences one unresolved problem. Journey mapping gives the team a way to examine those connections.
Define whose journey is being mapped
Choose an actor, a situation, and a beginning and end that serve the question. “All customers, from awareness to loyalty” is usually too broad for detailed investigation. “A first-time customer trying to rearrange a missed delivery” creates a more manageable scope.
Nielsen Norman Group’s journey-mapping guidance explains how the process can bring fragmented organisational understanding together. The map should still distinguish research evidence from workshop assumptions. A proposed future journey and an account of today’s experience are different artefacts.
Use interviews, observation, service records, and other relevant evidence to understand the sequence. Diary studies can help when an experience unfolds over days and would be difficult to reconstruct in one sitting.
Follow the work between the visible touchpoints
In the illustrative missed-delivery journey, the customer may check an email, search for a reference number, call support, and wait for a promised update. Include that waiting and repeated work, rather than mapping only the screens the company owns.
Record actions, questions, and reported feelings where the evidence supports them. An emotion curve drawn from the team’s imagination is an assumption, even if it makes the diagram more visually expressive. Show gaps honestly and use them to guide further research.
Keep materially different paths visible. Someone able to wait at home has different options from someone coordinating a delivery around a shift. Combining them into an average path can hide the constraint that makes the service fail.
Connect the finding to responsibility
Once the journey is understood, identify where the experience could improve and who can investigate or change it. “Communication is poor” leaves responsibility vague. “The delivery window changes after the confirmation email, but no updated message is sent” points to a specific gap.
A service blueprint may be useful when the team needs to map the operational processes behind that gap. The customer journey remains focused on the person’s experience, while the additional view explains how the organisation produces it.
Keep the map useful after the workshop
Attach source references, a date, and an owner. Revisit the affected part when the service changes, and evaluate whether the change resolves the observed difficulty.
A map becomes valuable through those decisions. It should help colleagues see work the customer is doing unnecessarily and coordinate a response across boundaries, rather than becoming a polished picture of a journey nobody checks again.