Choose one situation before drawing the journey
A journey for every customer and every product quickly becomes too general to help. Start with a defined person or group, a concrete task, and a clear beginning and end. For example, explore how an office coordinator finds and books a room for a team workshop, from recognising the need to completing the event. This is more useful than mapping all possible contact with a venue. Your target audience provides context, but the journey still needs a specific scenario. The same coordinator may behave differently when booking an urgent replacement room and when planning a recurring series with plenty of notice.
A journey is larger than its touchpoints
A touchpoint is an individual encounter, such as opening a venue page or speaking to its receptionist. The journey includes those encounters and what happens between them: asking colleagues about dates, waiting for approval, comparing options, or worrying about whether equipment will work. Some activities occur entirely outside the business's view. That is why a list of company channels is not yet a customer journey. The useful perspective is the person's task across time. Ask what they are trying to resolve at each stage, including the moments when they are not looking at your website or speaking with your team.
An illustrative example: booking a workshop room
Imagine a fictional venue offering rooms for small teams. Its coordinator can find attractive photographs and submit a booking request easily. The difficulty appears later: she needs to confirm the room layout with a colleague, but the reply provides only a price and date. She sends another email, waits, and then worries about getting internal approval in time. The venue may believe its enquiry process works well because every message receives an answer. A journey view reveals that the answer does not resolve the actual decision. The problem concerns continuity between information, approval, and booking, rather than the appearance of the original page alone.
Record actions, questions, and evidence
For each stage, note what the person does, what they need to know, and what helps or blocks progress. Include the relevant business response and any supporting evidence, such as an interview account or a recurring enquiry. Keep assumptions visibly separate. A team may imagine that customers enjoy a particular step when they actually tolerate it because no alternative exists. Avoid filling emotional labels into a template without a basis. If you do not know how people experience waiting for confirmation, record the uncertainty and investigate it. An honest incomplete map is more useful than a confident fictional account presented as customer research.
Expect loops, pauses, and multiple participants
People do not always move neatly from awareness to comparison to purchase. They may return to a question, abandon the search temporarily, or involve someone with a different responsibility. The room coordinator might choose a venue while a manager approves the expense and an attendee checks access requirements. Their activities overlap. Keep the map readable by focusing on the main scenario and marking important variations rather than drawing every possibility. When two groups have fundamentally different tasks, separate maps may be clearer. The aim is understanding, not a diagram so comprehensive that the team can no longer see where an actual improvement is needed.
Include what happens after the booking
The journey continues when a transaction is recorded. Arrival instructions, access to the room, equipment setup, questions during the event, and the later invoice can all influence the overall user experience. A simple booking page cannot compensate for an unclear arrival process when a team is waiting outside. In the fictional venue, the coordinator may need a message she can forward to participants. Providing it at the right time helps her complete an additional task. Looking beyond the sale also reveals whether the business's promise remains credible during use, which can affect whether people consider returning or recommending the venue.
Turn the map into an improvement decision
A map is useful when it changes what the team does. Identify obstacles that cause meaningful uncertainty, delay, or repeated work, then connect them with a responsible person. In the room example, including a layout confirmation in the initial response may be more useful than redesigning the entire website. Process improvement can address the internal handover needed to make that response reliable. Check whether the proposed change helps the customer's task and whether staff can maintain it. A nicer-looking map without an owner or next action usually remains a workshop output rather than a practical tool for improving the service.
Check the map against real behaviour
Review recent cases and ask people to describe what happened in their own words. Compare those accounts with the proposed sequence. Look for steps missing from the business's view and places where the map assumes information was understood simply because it was sent. Then test a focused improvement and review the relevant evidence again. For the fictional venue, staff could note whether layout questions still require repeated exchanges. Keep the map current when the service changes, but do not redraw it for every minor exception. It should be a usable shared explanation of a particular experience, with clear limits and visible questions for further learning.
Common questions
Do I need special software to map a journey?
No. A shared document, table, or simple board can work. The quality depends more on the scenario, evidence, and resulting decisions than on the drawing tool. Choose a format the people responsible for improvements can read and update without depending on a specialist every time.
Is the customer's journey the same as our sales funnel?
No. A sales funnel organises progression from the business's perspective, often through stages toward a sale. A journey follows the person's broader task and experience, including activities outside the business and after purchase. The two can inform each other, but they answer different questions.