Customer journey map worksheet

A journey map is only useful when it maps one real persona doing one real journey, with evidence in each cell instead of guesses. This worksheet keeps the scope that tight. Fill every [bracket] before you share it, and mark any cell you filled from opinion — not data — with a ? so you know what still needs a number.

Why map the whole journey instead of just reading the ticket queue: McKinsey found that measuring satisfaction across a full journey is roughly 30% more predictive of overall customer satisfaction than measuring it at each individual touchpoint (McKinsey, "The three Cs of customer satisfaction"). Tickets tell you where a single interaction went wrong; the map tells you why the customer was already frustrated when they arrived.

---

Step 1 — Set the scope (do this first)

Fill these before you draw anything. One persona, one journey per map.

• Persona: [one named segment, e.g. "solo admin at a 20-person customer"]
• Journey: [the specific journey, e.g. "from signup to first successful export"]
• Trigger (start): [the event that begins it]
• End state (success): [what "done" looks like from the customer's side]
• Time span: [hours / days / weeks]
• Channels in scope: [web, email, chat, phone, in-app]
• Map owner: [name] · Re-review date: [date]

A map that covers "all customers" covers no one. If you have three personas, make three maps.

---

Step 2 — Fill the grid

One row per stage. Rename or delete any stage this persona doesn't actually live through.

Column notes

• Thinking & feeling is the one column you cannot fill from a dashboard — it comes from talking to customers (Step 3).
• Support signal is the column most teams skip and the one you already have data for: which stage generates contacts, and why.
• Friction / drop-off should name a specific step where people stall, not "it's confusing."

---

Step 3 — Back each cell with evidence

Do not ship a map made of opinions. Pull from:

• Ticket / contact volume by stage (helpdesk tags) — shows where support gets pulled in
• Top contact reasons per stage (your contact-reason taxonomy)
• CSAT / CES scored by stage or contact reason
• Help-center search logs — what they look for and don't find
• Product analytics — drop-off rate between steps
• A handful of real chat/session transcripts, read end to end
• 5–10 short customer interviews for the "thinking & feeling" column

Every cell still filled from opinion keeps its ? until someone finds the number.

---

Step 4 — Mark the moments of truth

Not all stages matter equally. A moment of truth is a stage where a bad experience is most likely to lose the customer or spike contacts.

• Circle the 2–3 stages that make or break this journey.
• For each, record:

---

Step 5 — Turn the map into action

A journey map with no owned actions is a poster.

---

Validation checklist

• Every stage has at least one real data point, not just an opinion
• The support-signal column is filled from actual ticket data
• At least one customer — not just the team — has seen the map and recognized their own experience
• Each moment of truth has an owner and a target
• Every friction point maps to an action with a metric to move
• The re-review date is on a calendar

---

Common mistakes

• Mapping the journey you designed instead of the one customers actually live.
• Covering every persona at once — the map becomes an average of no one.
• Stopping at the artifact. No owners, no metrics, no change.
• Treating it as one-and-done. Journeys drift as the product and customer base change; revisit [quarterly].