What a journey map is for
Inside a business, each team sees its own slice of the customer’s experience: marketing sees the ad and the landing page, sales sees the calls, operations sees delivery, support sees the problems. Nobody sees the whole. A journey map stitches those slices together from the customer’s point of view, so gaps and contradictions become visible.
The output should be decisions, not decoration. Many journey maps end up as large, attractive posters that change nothing. The test of a good map is whether it leads to specific, owned improvements in the following quarter.
Choose a scope before you start
A journey for “all customers buying anything” is too broad to be useful. Pick one buyer persona or customer type, one scenario and a clear start and end point. For example: a first-time buyer of a home appliance online, from realising they need one to first use; or a finance head evaluating a new supplier, from first trigger to signed contract.
Compare scenarios
Types of journey map
Documents how the journey works today, warts and all.
- Best for finding pain points and quick fixes
- Must be built from evidence, not assumptions
- The most common and most useful starting point
Describes the journey you want to create.
- Useful for planning a redesign or new offer
- Should be built after a current-state map
- Turns into a roadmap of changes
Maps the customer’s wider day, not only interactions with you.
- Reveals moments and needs outside your current touchpoints
- Useful for finding new opportunities and channels
- Pairs well with jobs-to-be-done research
Adds the internal processes and systems behind each customer step.
- Shows which teams and tools create each experience
- Useful for operational fixes
- More detailed and more work to build
Step 1: gather evidence
Workshops are useful for assembling a map, but the content must come from evidence. Otherwise the map simply records what the team already believed. Combine qualitative and quantitative sources.
- Customer interviews about a recent purchase, reconstructing what happened step by step.
- Sales and support records: common questions, objections, complaints and their timing.
- Analytics: where people enter, drop off and return on your website or app. See funnel analysis.
- Session recordings and heatmaps to see behaviour on key pages. See heatmaps and session recordings.
- Reviews and social comments in customers’ own words.
- Mystery shopping: go through the journey yourself, including calling and messaging.
Step 2: define the stages
Stages should reflect the customer’s progress, not your departments. Customers do not experience “marketing” and “sales”; they experience realising a need, looking for options, choosing, buying, getting started and living with the product.
Fig. 01 · Timeline
Tap to explore
A typical journey structure
Step 3: map the rows
For each stage, record a consistent set of rows. Keep the number of rows small enough that the map remains readable.
| Row | Question | Example (illustrative) |
|---|---|---|
| Goals | What is the customer trying to achieve here? | Find an option that fits budget and timeline |
| Actions | What do they actually do? | Search, ask peers on WhatsApp, read reviews |
| Touchpoints | Where do they meet you? | Search result, product page, sales call |
| Thoughts and questions | What are they wondering? | “Will this work for a business our size?” |
| Feelings | How do they feel? | Uncertain, rushed, cautiously optimistic |
| Pain points | What gets in their way? | Pricing unclear; no reply for two days |
| Opportunities | What could we change? | Publish pricing logic; set a response-time target |
Pay special attention to the transitions between stages and between teams. Many of the worst experiences happen at hand-offs: from ad to landing page, from enquiry to first reply, from signing to onboarding.
Step 4: find and prioritise the moments that matter
A complete map will reveal many pain points. Not all deserve attention. Prioritise those that affect many customers, occur at decisive moments, or cause customers to abandon the journey. Then weigh impact against effort to fix.
Fig. 02 · Matrix
Tap to explore
Prioritising journey fixes
Running the mapping workshop
Once evidence is gathered, a workshop turns it into a shared map. Invite people from every team that appears in the journey: marketing, sales, operations, delivery, support and, ideally, someone who regularly speaks to customers. Keep the group small enough to work, typically under a dozen.
- 01Share the evidence first. Play interview clips, read support tickets aloud, show the drop-off data.
- 02Build the stages together. Agree the stage names in customer language.
- 03Fill the rows stage by stage. Use the evidence, and mark anything that is an assumption.
- 04Walk the map as the customer. Read it aloud from start to finish and listen for moments that feel wrong.
- 05Vote on the moments that matter. Then prioritise fixes, as below.
Mark assumptions clearly in a different colour or symbol. They are research questions for later, not facts. A map with honest gaps is more useful than one that looks complete because guesses were written in confidently.
Step 5: turn the map into action
- 01List the prioritised fixes with a named owner and date for each.
- 02Define a measure that will show the fix worked, such as drop-off rate at a step or time to first reply.
- 03Share the map widely, especially with teams whose work appears on it.
- 04Revisit the map after fixes, and update it at least annually.
Moments of truth
Not every step in a journey carries equal weight. A few moments shape the customer’s overall judgement far more than the rest: the first reply to an enquiry, the moment a delivery arrives, the first time something goes wrong and how it is handled. These are sometimes called moments of truth.
Identify them explicitly on your map, using interview evidence about what customers remember and mention. Then design them deliberately. A business that handles a problem well can earn more loyalty than one where nothing went wrong, because the recovery proves the promise. Conversely, a slow or defensive response at a moment of truth can undo good work everywhere else.
Common mistakes
- Mapping the journey you designed rather than the one customers experience.
- Covering every persona at once and producing an unreadable map.
- Stopping at the purchase, when onboarding and use drive retention and referral.
- Producing a beautiful poster with no owners or actions.
- Ignoring emotional states, which often explain behaviour better than actions do.
Checklist
0/10Journey mapping checklist
Journey maps connect naturally to full-funnel marketing planning and to customer experience work in online retail.
Key takeaways
- 01A journey map stitches together the customer’s experience across teams that each see only one slice.
- 02Scope it to one persona, one scenario and clear start and end points.
- 03Build it from interviews and data, including channels you do not own.
- 04Pay particular attention to hand-offs between teams and stages.
- 05A map is only useful if it ends in prioritised, owned fixes with measures.
Frequently asked
- What is customer journey mapping?
- Customer journey mapping is the practice of documenting, from the customer’s perspective, the stages, actions, touchpoints, thoughts, feelings and pain points involved in discovering, buying and using a product or service. It helps teams find and fix problems that no single department can see.
- What are the stages of a customer journey?
- A common structure is trigger, exploration, evaluation, purchase, onboarding, and use and renewal. Exact stages vary by category. They should describe the customer’s progress in their own terms rather than mirror internal departments.
- How do you create a customer journey map?
- Choose a persona and scenario, gather evidence through interviews, analytics and support records, define stages, record goals, actions, touchpoints, thoughts, feelings and pain points for each, then prioritise the most important fixes and assign owners and measures.
- What is the difference between a journey map and a service blueprint?
- A journey map shows the customer’s experience. A service blueprint adds the internal processes, people and systems behind each step. Blueprints are useful when the fixes you need are operational rather than about communication.
- How often should a customer journey map be updated?
- Update it after significant changes to your offer, channels or processes, and review it at least once a year. If fixes from the previous map have been made, re-map the affected stages to check they worked.
Published by Fabulous.Media, a network of specialist marketing agencies. Updated 9 October 2026. Platform features change often; check current official documentation before acting on platform-specific detail.





