A customer journey presentation is useful when a team needs to agree what the customer is trying to do, where the experience breaks and which improvement deserves attention first. It is not a decorative timeline. Build it from evidence, name the limits of what you know and connect every friction point to an owner and a next action.
For a broader marketing planning workflow, the marketing presentation guide helps place the journey in a campaign or growth decision. This article focuses on the journey itself: stages, moments, evidence, emotions, friction and action.
1. Start with one journey question
Decide what the map must help the audience choose. Examples include “Where should onboarding remove the most effort?” and “Which moment is causing qualified trials to stall?” A map that tries to represent every audience and channel becomes a wall of labels with no decision.
Define the customer segment, scenario and time window. A journey for a first-time buyer differs from a renewal journey. State whether the map reflects observed behavior, reported experience, an internal hypothesis or a mixture. This boundary is essential: a workshop assumption should not be presented as a measured customer fact.
Write the desired outcome in one sentence. For example, the team may want a prioritized experiment for the first week after signup. That sentence becomes the test for every slide: does this detail help the audience select an action?
2. Choose stages that follow the customer
Use stage names that describe what the customer is doing rather than what the company department is doing. “Recognize a need,” “compare options,” “start,” “reach first value” and “return” may be clearer than “marketing,” “sales,” “implementation” and “support.” The right stages depend on the scenario.
Give each stage a consistent set of fields: customer goal, key touchpoints, customer questions, evidence and friction. Avoid adding a new field for every interesting comment. Consistency lets the audience compare moments and spot patterns.
Keep the map legible by splitting it into two views when needed. The overview shows the stages and highest-friction moments. Detail slides show the evidence and context for one stage. A single oversized canvas may contain everything but communicate little in a meeting.
A worked example: finding and booking an evening course
Suppose a fictional training provider wants to understand why first-time visitors do not finish booking an evening course. The actor is a working adult looking for a suitable date, not the provider's sales team. The journey begins with finding a course and ends with receiving a usable confirmation. This follows the distinction in Nielsen Norman Group's journey-mapping guide: a map needs a particular actor, scenario, phases and opportunities, not just a list of internal departments.
The following invented data illustrate the presentation method. During one defined week, 240 unique visitors viewed a course page, 120 of those visitors opened the booking form, and 84 of those 120 completed a booking. Separately, the team observed five recruited participants attempting the task. The event counts describe the funnel; the five sessions help investigate what people encounter. They are not interchangeable samples.
| Customer moment | Evidence to show | Interpretation and boundary | Possible next step |
|---|---|---|---|
| Find a suitable course | 240 unique course-page visitors in the stated week. | This is the starting population, not proof that all visitors intended to book. | Keep the course, device and date filters visible beside the count. |
| Check whether attendance is possible | Three of five observed participants looked for the finishing time before choosing a date. | The sessions suggest an information need. They do not establish that 60% of all visitors have this problem. | Test showing the finishing time next to each date. |
| Enter booking details | 120 visitors opened the form; 84 completed a booking. | Form completion is 84/120 = 70%; 36 did not complete within this measurement window. The cause is not known. | Inspect the exit step and observed difficulties before replacing the whole form. |
| Know that the booking is confirmed | Four of five observed participants found the confirmation; one looked in the wrong email folder. | This is an observation from five sessions, not an email-delivery rate. | Retain the visible confirmation page and examine the wording of the email instruction. |
A headline such as "Some participants need the finishing time before they choose a date" fits the evidence. "Customers abandon because course times are unclear" does not. The latter joins an observed difficulty to an aggregate drop-off without showing that one caused the other. Keep an emotion such as frustration labeled as reported or observed; do not invent an emotional curve to fill an empty row.
For the meeting, put the four customer moments on the overview slide. Place the counts and the observation notes on a separate evidence slide. This keeps the journey readable while allowing someone to challenge the interpretation without losing the sequence.
3. Connect observations to evidence
Use a source label for each observation. A support transcript, product analytics event, interview note, survey response and stakeholder assumption are different kinds of evidence. They can all inform the map, but they should not appear interchangeable.
When using a quote, preserve the meaning and record the date and segment. Remove personal information that is not needed for the decision. A single quote can illustrate a friction point; it cannot establish how common the problem is. Pair qualitative observations with a count, rate or sample description when such information is available.
For quantitative signals, define the denominator and period. “Thirty users dropped” says little without the number who entered the step and the time window. If the metric is directional or incomplete, say so beside the chart. Accuracy builds more trust than a precise-looking number.
4. Describe friction as a moment, not a verdict
Write friction in the customer’s terms: “I do not know which file to upload,” or “I cannot tell whether my request was received.” Then distinguish the visible symptom from the possible cause. A slow page might reflect network conditions, unclear status feedback or a process outside the interface.
Use a severity rule that the team understands. You could rate impact, frequency and confidence separately rather than multiplying them into one unexplained score. For example, a high-impact issue with low confidence may deserve research before a large redesign.
Mark moments that delight or reassure the customer too. A map made only of problems can lead to unnecessary change. Knowing what is already working helps the team protect useful cues when it addresses a nearby friction point.
5. Move from friction to an owned action
Prioritize a small number of moments using criteria relevant to the decision: customer impact, business effect, confidence, effort and reversibility. Make the rule visible. A priority is a choice under constraints, not a claim that every other problem is unimportant.
For each chosen moment, name the proposed action, owner, measure and review date. “Improve onboarding” is not an action. “Test a shorter import checklist with ten new accounts and compare completion to the current flow” is specific enough to learn from, while still leaving room to revise the design.
Include the customer signal that would change the plan. If the issue is assumed to be missing information, a test that shows users understand the information but fail for another reason should redirect the team. This protects the presentation from becoming a fixed verdict.
In the course example, the first action could be a small design test, not a site-wide checkout rebuild. The course-content owner adds the finishing time beside the date on a prototype; a researcher asks new participants to select a course they can attend. The question is whether they can make that decision without leaving the date selector. Keep that usability result separate from booking conversion. If the team later wants to claim a conversion effect, it needs an appropriate comparison of live booking outcomes, not just a preference expressed in a prototype session.
The presentation can therefore end with a bounded request: approve this change for testing, identify who will supply accurate course times, and agree when to review the observed tasks. If people still cannot decide, inspect other missing information rather than declaring the original hypothesis confirmed.
6. Tell the story in a meeting
Start with the journey question and the segment. Show the overview, then zoom into the two or three moments that matter. For each moment, move from customer goal to evidence, friction, interpretation and action. End with the decision, owners and follow-up signal.
Keep labels plain. Replace internal abbreviations with terms a new teammate can understand. Use the same stage names on every slide and provide a short legend for any scale. If the map is based on a limited sample, include that fact near the conclusion rather than hiding it in an appendix.
After the meeting, publish the source notes and decision log with the map. A customer journey presentation earns its value when people can act on it and later compare the new evidence with the original hypothesis.
