Customer Journey, Stages and Touchpoints

Map the journey around the customer’s goal

A customer journey is a sequence of experiences and interactions connected to the customer’s attempt to achieve a goal with or around an organization. The journey starts from “What is the customer trying to accomplish?” rather than from the internal organization chart. In one service, stages might be Explore, Choose, Start, Use, Get Help, Renew or Leave. These labels are not universal rules; they vary with the goal and service. What matters is that each stage represents meaningful progress toward a customer goal.

Distinguish three terms. A stage is a meaningful part of the journey with a goal or transition. A touchpoint is a moment when the customer encounters the organization or something representing it. A channel is the medium through which an interaction occurs, such as phone, app, website or branch. An app is a channel; “receiving a successful-payment notification in the app” is a touchpoint. A channel can recur across stages, and one stage can contain several touchpoints.

The journey is not always a straight line

A customer may return to an earlier stage, skip a stage, switch channels or rely on a partner. A new customer may read guidance before buying, while a returning customer goes straight to use. Someone may start on the phone and finish on the website. A journey map therefore summarizes useful patterns; it does not claim that every individual follows the same route. Research on journey mapping warns against assuming that all customers encounter the same touchpoints or that all touchpoints matter equally.

When naming stages, avoid internal labels that mean little to the customer, such as “Back-office processing 2.” Those labels may be useful later in a service blueprint, but the core journey map should let the reader understand what the customer is trying to achieve. This does not mean ignoring internal processes; it means placing them in the appropriate layer so customer language and organizational language are not confused.

Test the journey against more than one path

Before accepting an initial map, ask: Is there a new-customer path and a returning-customer path? Does the journey change when something goes wrong? Does a partner affect an interaction? Can the customer move from one channel to another? You do not need dozens of maps at the start. The goal is to expose variations that change expectations, friction or responsibility and to leave unknowns as assumptions needing evidence rather than turning them into facts.