ITIL 4 DSV: Customer Journey

The Customer Journey domain checks that you can describe the end-to-end journey a consumer takes with a provider, name its stages and touchpoints, and use journey mapping to improve service design and delivery.

Core rules

• The ITIL 4 DSV customer journey has eight stages: Explore, Engage, Offer, Agree, Onboard, Co-create, Deliver and support, and Realize. A journey can loop back; it is not a rigid waterfall.
• A touchpoint is any interaction between customer and provider; channels are the media used. Moments of truth are the touchpoints that shape perception most strongly.
• Map the journey to the service value chain to see which activities create value at each stage, and use service blueprinting to connect front-stage touchpoints with back-stage support.
• Journey mapping should use evidence such as interviews and analytics, and should record emotions and pain points, not just process steps.

Worked example

A broadband provider maps a new-customer journey. Explore and Engage show strong interest, but Onboard shows a 30% drop-off because the activation form asks for the same data twice. Reasoning: the journey view shows the problem is not the offer or the network but a touchpoint in Onboard. Fixing the form removes a moment of truth that damages conversion and creates avoidable support calls, so it is prioritised for both revenue and cost reasons.

Traps

Do not confuse the customer journey with the service value chain: the journey is the customer's end-to-end experience; the value chain is the provider's operating model. Do not treat the journey as strictly linear, and do not equate user experience with customer experience - the customer and the daily user may be different stakeholders. Avoid mapping only the happy path; exceptions, handoffs, and waiting time are where many failures live.