Customer Journey Map
A customer journey map charts the whole relationship between a person and a company — from first hearing of it, through evaluating, buying, onboarding, using, getting help, and deciding whether to stay — across every channel and every internal team that touches them. Where file 04 zooms into one product scenario, this map zooms out to the business: marketing, sales, product, support, and billing all appear on the same timeline, usually for the first time.
The honest terminology note
In the wild, "user journey map" and "customer journey map" mean the same thing more often than not. NN/g says so directly: the terms "can be used interchangeably," both referencing a visualization of a person using your product or service (Gibbons, "Journey Mapping 101"). This section still keeps two files, as a working convention:
- File 04 (user journey map) — product-scenario scope: one actor, one scenario, mostly inside the product experience.
- This file (customer journey map) — relationship-with-company scope: the full commercial lifecycle, owned by many teams.
Same anatomy (actor, scenario/expectations, phases, actions/mindsets/ emotions, opportunities — see file 04), different altitude. When someone hands you "a journey map," ask which altitude they mean before arguing about rows.
When to use one
- Funnel diagnosis: conversion drops between marketing's numbers and product's numbers, and nobody owns the seam.
- Channel handoffs: what sales promised vs. what onboarding delivers; what the ad claimed vs. what the pricing page says.
- Silo detection: each team optimizes its own stage and the customer feels the joints. The map makes the joints visible by putting the owning team under each touchpoint.
- Retention and renewal work: churn usually roots earlier than the cancellation click — the map lets you trace it back.
Best fit: SaaS, services, e-commerce, consulting — any business where the relationship outlives the transaction and crosses several teams.
What it adds beyond a user journey map
- Touchpoint ownership — a row naming the team accountable for each touchpoint. This single row does most of the political work.
- Pre- and post-product stages — ads, content, sales calls, invoices, renewal emails: experiences product teams never see but customers don't distinguish from "the product."
- Business metrics per stage — visitors, trial starts, activation, ticket volume, churn — pairing the feelings row with the numbers row shows where emotion and revenue drop together.
Example: SaaS relationship with owning teams
Path: Google Search → Blog post → Landing page → Pricing → Signup → Welcome email → Product use → Support ticket → Renewal
| Touchpoint | Customer moment | Owning team | Classic seam/failure |
|---|---|---|---|
| Google Search | "There must be a tool for this" | Marketing (SEO) | Ranks for the wrong intent |
| Blog post | Learns approach, gains trust | Content | Great advice, weak path onward |
| Landing page | "Is this for people like me?" | Marketing | Claims the product can't keep |
| Pricing | Computes real cost | Marketing + Sales | Hidden tiers, "Contact us" wall |
| Signup | Commits, hands over email | Growth/Product | Long form kills the impulse |
| Welcome email | First owned-channel contact | Lifecycle/CRM | Generic blast, no next step |
| Product use | Value moment (or not) | Product/Eng | Onboarding assumes sales demo happened |
| Support ticket | Trust stress test | Support | No context: asks what plan they're on |
| Renewal | "Was it worth it?" | Sales/Finance | First contact in months is an invoice |
Read the seams column vertically: almost every classic failure lives at a handoff BETWEEN owners, which is why no single team ever fixes them without a map. Each touchpoint that lives inside the product has a detailed flow file: signup (Authentication Flows), welcome and first use (Onboarding Flows), purchase (Checkout Flows), lifecycle email (Notification Flows). For the full-lifecycle view with metrics per stage, see End-to-End Flow.
How to build it
- Pull the data each team already has: analytics funnels, CRM stages, support-ticket themes, churn interviews, NPS verbatims — plus customer research of your own (07-process-strategy/ UX Research Methods). The evidence rule from file 04 applies fully.
- Draft phases in the CUSTOMER's language (Discover, Try, Buy, Get value, Get help, Decide to stay) — not the org's (MQL, SQL, Closed-Won).
- Map touchpoints per phase; annotate each with owner, channel, and evidence of pain.
- Walk it with one person from every owning team in the room; the map's value is the argument it forces.
- Turn seams into opportunities with a named owner — cross-team pains need a cross-team owner or they survive the workshop.
Common mistakes
- Drawing the org's sales funnel and labeling it a journey — the map must follow the customer's timeline, including the parts where they ignore you.
- No ownership row — a beautiful map of problems nobody is assigned.
- Only mapping acquisition; the post-sale half (use, support, renewal) is where retention businesses live or die.
- Averaging all customers into one; segment first (new vs. renewing, self-serve vs. sales-led), map the segment that matters now.
- Treating it as marketing's artifact; if product and support didn't contribute, the middle of the map is fiction.
Checklist
- Scope declared: which customer segment, which relationship span
- Phases named in customer language, pre-sale through renewal
- Every touchpoint annotated with owning team and channel
- Doing/thinking/feeling rows evidenced, not invented (see file 04)
- Business metric per stage placed next to the emotion curve
- Seams between teams explicitly marked as risk points
- Opportunities assigned to named cross-team owners
- Post-sale stages (use, support, renewal) as detailed as acquisition
- Reviewed with all owning teams; revisit cadence agreed
Sources
- Nielsen Norman Group — Gibbons, S. (2018). "Journey Mapping 101" (nngroup.com/articles/journey-mapping-101/) — anatomy; the explicit note that user/customer journey map are interchangeable terms.
- Nielsen Norman Group — Gibbons, S. (2017). "UX Mapping Methods Compared: A Cheat Sheet" (nngroup.com/articles/ux-mapping-cheat-sheet/) — journey map as goal-directed and tied to a specific business.
- Kalbach, J. (2016; 2nd ed. 2020). Mapping Experiences. O'Reilly — alignment diagrams across the customer lifecycle.