Customer journey mapping is the practice of charting every step a customer takes with your company, from first hearing about you to renewing or leaving, and recording what they do, think, feel, and struggle with at each step. A map has five stages (awareness, consideration, purchase, retention, advocacy) and five layers per stage (actions, touchpoints, thoughts and feelings, pain points, and opportunities). You build it in seven steps: pick a persona and scope, list the stages, fill in actions and touchpoints, capture emotions, mark pain points, spot opportunities, and assign an owner to each fix. The map is only useful when someone acts on the opportunities column.
Most customer journey maps die as a poster on a wall. This guide is written to prevent that. Below is the exact structure of a working map, a template you can copy into a spreadsheet in ten minutes, a filled-in example for a B2B software company, and answers to the questions people ask before they start. The goal is a map your team uses to decide what to fix next, not a piece of decoration.
What is customer journey mapping?
Customer journey mapping is the process of visualizing the full sequence of interactions a customer has with your company, then layering on what they are trying to do, how they feel, and where they get stuck. The output is a table or diagram that puts the customer's actual experience in front of the teams who shape it, so pain points stop being invisible. A good map is honest about the low points, specific about the touchpoints, and ends in a list of opportunities with owners.
The reason it matters is that no single team sees the whole journey. Marketing sees the ad and the signup. Onboarding sees the first two weeks. Support sees the tickets. Billing sees the invoices. The customer experiences all of it as one continuous relationship, and the friction usually lives in the handoffs between those teams. A journey map is the one artifact that shows the seams. That is also why journey mapping is a back-office discipline as much as a marketing one: most of what the customer feels is produced by operations, which is the argument behind our foundational guide to customer experience operations.
The five customer journey stages
Almost every journey map uses the same five stages. The names vary by company, but the shape does not: the customer becomes aware of a need, weighs options, buys, uses the product over time, and then either advocates for you or churns. Mapping stage by stage keeps you from jamming a twelve-month relationship into one row.
| Stage | What the customer is doing | Their mindset | Typical touchpoints | The team that owns it |
|---|---|---|---|---|
| Awareness | Realizes they have a problem and starts looking | "Is this even solvable? Who does this?" | Search, ads, referrals, review sites | Marketing |
| Consideration | Compares options and evaluates fit | "Which one is right for us, and can I trust it?" | Website, demo, pricing page, sales calls | Sales, Marketing |
| Purchase | Signs up, pays, and gets set up | "Did I make the right call? How do I start?" | Checkout, contract, first invoice, onboarding | Sales, Onboarding, Billing |
| Retention | Uses the product and gets support | "Is this still worth it? Are they helping me?" | Product, support tickets, account reviews | Support, Success |
| Advocacy | Renews, expands, or refers others | "Would I recommend this? Do I stay?" | Renewal notice, referral ask, NPS survey | Success, Marketing |
Notice how many stages the operational teams own. The purchase and retention stages, where onboarding, billing, and support live, are where most maps reveal their worst pain points, because that is where the promise made in sales meets the reality of running the account. If your map has rich detail in awareness and consideration but goes thin after the sale, you have a marketing journey map, not a customer journey map.
The five layers of every journey map
Within each stage, a complete map records five layers. These are the rows that make the map more than a funnel diagram. Miss the emotion and pain-point layers and you are left with a process chart that tells you nothing about how the experience feels.
- Actions: the concrete steps the customer takes ("uploads first document," "waits for approval").
- Touchpoints: where each action happens (your app, an email, a phone call, a portal).
- Thoughts and feelings: what is going through their head, ideally in their own words from real feedback.
- Pain points: the moments of friction, confusion, waiting, or effort.
- Opportunities: the specific fix, with an owner, that would remove the pain point.
The thoughts-and-feelings and pain-point layers are where you should be pulling from real data, not guessing. Support tickets, survey verbatims, and session recordings are gold here. If you already run a voice of customer program, its feedback log is the natural feeder for these two rows.
How to create a customer journey map in 7 steps
Here is the build process a working CX team follows. It takes an afternoon for a first draft and a few weeks of real feedback to sharpen. Do not wait for perfect data to start; a rough map built from what you already know beats a blank one you are still researching.
- Pick one persona and one scope. Do not map "all customers" or "the whole relationship" at once. Map one persona (for example, "the operations manager at a mid-size firm") through one journey (for example, "from signup to first successful outcome"). Narrow scope is what makes a map actionable.
- List the stages. Start from the five stages above and rename them to match how your customers actually move. A self-serve product might collapse consideration and purchase; an enterprise deal might split them into five sub-stages.
- Fill in actions and touchpoints. For each stage, write the concrete steps the customer takes and where each one happens. Walk it as if you were the customer, clicking through your own product and reading your own emails.
- Capture thoughts and feelings. Add what the customer is thinking at each step, using real quotes from support tickets and surveys wherever you have them. This is the row that turns a process chart into a journey map.
- Mark the pain points. Flag every moment of friction, waiting, confusion, or repeated effort. Be honest, especially about your own handoffs. The billing surprise, the third time they had to re-explain a problem, the two-day wait for approval: those are the wins hiding in plain sight.
- Turn pain points into opportunities. For each pain point, write one specific fix and one measurable target. "Onboarding is confusing" is not an opportunity. "Add a guided setup checklist; get 80 percent of accounts to first outcome within 14 days" is.
- Assign an owner to every opportunity. A map with no owners changes nothing. Put a name next to each fix, rank them by impact, and bring the top few to your next planning meeting. This is the step that decides whether the map lives or becomes wallpaper.
A customer journey map template you can copy
Here is the template as a grid: stages across the top, layers down the side. Copy it into a spreadsheet, put each stage in its own column, and fill the five layer rows for each. That is the entire structure. You do not need dedicated software to start; a shared sheet with these rows will carry you a long way.
| Layer | Awareness | Consideration | Purchase | Retention | Advocacy |
|---|---|---|---|---|---|
| Actions | (fill in) | (fill in) | (fill in) | (fill in) | (fill in) |
| Touchpoints | (fill in) | (fill in) | (fill in) | (fill in) | (fill in) |
| Thoughts and feelings | (fill in) | (fill in) | (fill in) | (fill in) | (fill in) |
| Pain points | (fill in) | (fill in) | (fill in) | (fill in) | (fill in) |
| Opportunities (owner) | (fill in) | (fill in) | (fill in) | (fill in) | (fill in) |
A real customer journey map example (B2B software)
Here is the same template filled in for a mid-market B2B software company selling to an operations team. It is deliberately unglamorous, because a real map is a list of ordinary friction, not a marketing narrative. The pain points below are the kind that show up in almost every SaaS journey audit.
| Layer | Consideration | Purchase / onboarding | Retention |
|---|---|---|---|
| Actions | Books a demo, compares two vendors, checks pricing | Signs contract, sets up account, gets first invoice | Uses product daily, files a support ticket, hits renewal |
| Touchpoints | Website, sales call, review sites | Contract, setup wizard, first invoice email | App, support inbox, account review, renewal notice |
| Thoughts and feelings | "Can I trust this to actually work?" | "I signed, now what? Why is this bill different from the quote?" | "It mostly works. I wish support were faster." |
| Pain points | Pricing page hides the real number until a call | No guided first step after signup; first invoice does not match the quote | Customer re-explains the same issue across three agents; renewal notice arrives with no warning |
| Opportunities (owner) | Publish clear pricing (Marketing) | Add setup checklist; reconcile quote-to-invoice (Onboarding, Billing) | Carry ticket history across handoffs; send renewal 60 days out (Support, Success) |
Every opportunity in that bottom row is an operations fix, not a marketing message. The setup checklist is an onboarding-process decision, the kind we break down in our guide to the customer onboarding process steps and stages. The quote-to-invoice mismatch is a billing-experience problem that quietly erodes trust, which we cover in the piece on billing mistakes that break customer trust. And "re-explains the same issue across three agents" is a support handoff failure that a well-run shared inbox is built to prevent. The journey map does not fix anything by itself; it points precisely at which team owns the next fix.
How is customer journey mapping different from a process map?
A process map shows the steps your company takes to deliver something; a customer journey map shows the steps the customer takes and how they feel doing it. The difference is point of view. A process map might show "invoice generated, invoice sent, payment received" as a clean three-box flow. The journey map for the same moment shows the customer opening an invoice that does not match their quote, feeling misled, and firing off a support ticket. Same event, opposite lens. You need both, but only the journey map tells you where the experience hurts.
What data do you need to map the customer journey?
You need three kinds of input: behavioral data (what customers actually do, from product analytics and session recordings), attitudinal data (how they feel, from surveys and support tickets), and internal knowledge (what your teams already know about where things break). Start with what you have. Support ticket themes and survey verbatims alone will get you a credible first draft. As the map matures, layer in metrics like time-to-first-value, ticket volume by stage, and the survey scores you already collect, so each stage carries a number and not just a story. The metrics that predict churn map cleanly onto the retention and advocacy stages.
How often should you update a customer journey map?
Review the map quarterly and rebuild it whenever the journey materially changes, such as a new onboarding flow, a pricing change, or a support reorganization. A journey map is not a one-time deliverable; it is a living document that should track what you have actually fixed. The most useful habit is to revisit the opportunities column every quarter, mark what shipped, measure whether the pain point eased, and add whatever new friction has appeared. A map that never changes is a sign nobody is acting on it.
Do you need customer journey mapping software?
No. A shared spreadsheet with stages across the top and the five layers down the side is enough to build and maintain a working map. Dedicated tools like Miro, Figma, or specialized CX platforms help when you want a polished visual for stakeholders, real-time collaboration across a big team, or live metrics wired into each stage. But the tool is not the value. The value is the honest conversation about where customers struggle and the discipline of assigning an owner to each fix. Teams reach for software too early and end up with a beautiful map nobody acts on. Start in a sheet, prove the map drives decisions, and upgrade the tooling only when the manual version is straining.
Turn the map into fixes
A customer journey map earns its keep in the opportunities column. Everything before it, the stages, the touchpoints, the emotions, exists to get you to a ranked list of specific fixes with owners. Build the map narrow, fill the pain-point row with real customer words, and end every planning cycle by shipping the top opportunity and measuring whether it moved. The journey is continuous and so is the work: as the closed feedback loop keeps surfacing new friction, the map is where you decide what to fix next. Keep it honest, keep it owned, and it becomes the one document your marketing, onboarding, billing, and support teams can all point at when they argue about what the customer actually needs.