Customer Journey Mapping: How to Create a Customer Journey Map (with Example)

Every company has a customer journey, whether anyone has drawn it or not. The problem is that each team sees only its own piece: marketing sees the campaign, sales sees the deal, support sees the ticket. The customer experiences all of it as one story.

A customer journey map puts that story on one page. Done well, it shows where customers get stuck, which moments matter most, and which team owns the fix. Done badly, it becomes a poster that nobody looks at after the workshop.

This guide covers what a journey map is, the main types, how to build one step by step, what to measure at each stage, how to check the map against real customer feedback, an example you can adapt, and how to keep it useful.

What is a customer journey map?

A customer journey map is a visual representation of the steps a customer takes to reach a goal with your company, seen from the customer's side. It usually runs left to right through stages such as awareness, consideration, purchase, onboarding, use, support and renewal, and stacks several layers under each stage:

• Customer goal: what the customer is trying to achieve at that stage.
• Touchpoints: where the interaction happens (website, ad, store, app, email, call, chat, invoice).
• Actions: what the customer actually does.
• Thoughts and emotions: what they are thinking and how they feel, often drawn as a line that rises and falls.
• Pain points: where it breaks, slows down or disappoints.
• Opportunities: ideas to fix or improve each moment.
• Metrics and owners: how you measure the stage and which team is responsible.

The key word is perspective. An internal process map describes what your company does. A journey map describes what the customer goes through, including the parts you do not control, such as comparing you with a competitor or asking a friend.

Why customer journey mapping matters

• It gives everyone the same picture. Marketing, sales, product, operations and support see how their piece connects to the rest.
• It shows where customers drop off. A stage with many complaints, a low score or a big drop in conversion stands out once everything is on one page.
• It turns feedback into context. A comment like "the process was confusing" is hard to act on until you know whether it was about checkout, onboarding or a return.
• It helps you prioritise. You can compare stages by impact and fix the moments that matter most, rather than the loudest complaint of the week.
• It builds a customer-centric habit. Teams start asking "what does this look like for the customer?" before they launch something.

Types of customer journey maps

Most teams start with a current-state map. It is grounded in what actually happens, and it gives you the evidence you need to agree on a future state.

How to create a customer journey map, step by step

Step 1: Set a goal and a scope

Decide what the map is for. "Reduce cancellations in the first 90 days" or "understand why online orders lead to so many support calls" is a good goal. "Map the whole customer experience" is too broad for a first map.

Choose one scenario with a clear start and end, for example "from first visit to second order" or "from signed contract to first value".

Step 2: Choose a persona

Journeys differ by customer type. A first-time buyer, a returning customer and a business account all go through different steps. Pick one persona per map, based on real data: who buys most, who churns most, or who generates the most support contacts.

A useful persona fits on a card: who they are, what they are trying to achieve, what they worry about, how they prefer to interact and what success looks like to them. Base it on interviews, survey answers, CRM data and support conversations, not on assumptions in a meeting room.

Step 3: Define the stages

Write the stages in the customer's language, from their point of view. A typical set:

• Awareness: the customer realises they have a need and hears about you.
• Consideration: they compare options, read reviews and ask questions.
• Purchase: they decide, sign up or check out.
• Onboarding or delivery: they receive the product or start using the service.
• Use: they get value, or fail to, over time.
• Support: they ask for help when something goes wrong.
• Loyalty: they renew, buy again, recommend you, or leave.

Adjust the stages to your business. A clinic might use "find a clinic, book, visit, follow-up". A software company might split onboarding into "set-up" and "first value".

Step 4: List every touchpoint

For each stage, list every place the customer interacts with you: ads, search results, website pages, social media, reviews, emails, chat, phone, store, app, delivery, invoices, surveys. Include indirect touchpoints such as review sites and word of mouth.

A good way to find them is to walk the journey yourself. Buy your own product, call your own support line, try to return something. Then compare your list with your analytics and support data.

Step 5: Add goals, actions, thoughts and emotions

For each stage, write down what the customer is trying to do, what they actually do, what questions are on their mind and how they feel. Use their words wherever you can: quotes from interviews, survey comments, reviews and support tickets are more convincing than paraphrases.

Draw the emotional line across the stages. The low points are where to look first.

Step 6: Mark the pain points, with evidence

Pain points are moments of friction, confusion, delay or disappointment. Mark each one with evidence: how many comments mention it, how the stage scores, how many customers drop off there. A pain point backed by data gets fixed; one based on a hunch gets debated.

The next section explains how to use survey and feedback data for this.

Step 7: Choose metrics and owners

Give each stage at least one metric and one owner. If a stage has no owner, problems there tend to stay unsolved because every team assumes someone else is handling it. The table in the next section suggests metrics for each stage.

Step 8: Prioritise and act

List the opportunities and score them by impact on the customer and the business, and by effort. Fix a few high-impact moments first, measure the effect at that stage, and update the map. A journey map is a working tool, not a deliverable.

What to measure at each stage

Feedback metrics tell you how customers feel about a stage; behavioural metrics tell you what they do. You need both: a stage with good scores and a big drop-off is just as much a problem as a stage with poor scores.

For the survey side, our guides on CSAT and NPS cover how to ask, calculate and read each metric.

Using survey and feedback data to improve your journey map

A journey map built only from workshops reflects what your team believes. Customer feedback shows what customers actually experience. Use it in three ways.

Ask at the right moments

Place short surveys at the end of key stages: a CSAT question after checkout, delivery or a closed support case; a CES question after a self-service task or a return; an NPS question for the overall relationship. Always add an open question such as "What is the main reason for your score?" The score tells you which stage hurts; the comment tells you why.

Tag existing feedback by stage

You already have a lot of journey data in support tickets, chat logs, call transcripts, app store reviews, Google reviews and survey comments. Tag each comment with the stage it is about (and the touchpoint, if you can), then look at volume and sentiment by stage. The stages with the most negative comments are your first candidates for pain points.

Customers rarely say which step they are talking about, so tagging by stage takes judgement. Doing it by hand works for a few hundred comments; beyond that you need text analytics.

Break it down by segment

Averages hide problems. New customers may struggle with onboarding while long-standing customers are frustrated at renewal. Compare each stage by segment, channel and region to see which customers break where.

If you are starting from scratch, our guide on how to collect customer feedback covers the methods and channels.

Customer journey map example

Here is a simplified current-state map for an online retailer, persona "first-time buyer", scenario "from first visit to second order".

The map makes the priorities obvious: show shipping costs earlier, keep tracking updated and let customers print return labels themselves. Each fix has an owner and a metric to confirm it worked.

Common customer journey mapping mistakes

• Mapping your process instead of the customer's experience. If the stages read like your org chart, start again from the customer's side.
• Building the map on assumptions. Without interviews, survey comments and support data, the map shows what the team hopes is true.
• One map for every customer. Different personas go through different journeys. Start with the most important one.
• Too much detail too soon. A first map that tries to cover every edge case never gets finished. Start with one scenario.
• No metrics or owners. A pain point without an owner and a metric does not get fixed.
• Treating it as a one-off project. Products, channels and customer expectations change; a map that is not updated becomes wrong within months.

How to keep your journey map alive

• Review it on a schedule, for example every quarter, with the stage owners.
• Connect it to live data. Track the metric and the feedback for each stage continuously rather than once a year.
• Watch for changes. A sudden rise in negative comments at one stage usually means something changed: a new carrier, a new checkout, a pricing update.
• Close the loop. When you fix a pain point, measure the stage again and tell customers what you changed.

For a deeper look at monitoring journeys over time, see customer journey performance monitoring.

Where Pivony fits

• Customer journey analysis maps every comment from surveys, support tickets, call transcripts, app reviews and other sources to the journey stage it belongs to, even when the customer does not say which step they mean. You see satisfaction and sentiment by stage and segment, and root cause analysis inside each stage shows what to fix first.
• The VoC platform brings all of that feedback together and analyses every comment by theme and sentiment.
• Sonic Survey lets you ask CSAT, NPS and open questions after key journey moments, in writing or by voice, triggered by events such as a purchase or a CRM update.

Next step

Want to see where your journey breaks? Request a free 24h root cause scan on a sample of your reviews, tickets or survey comments, or book a demo.