map-a-customer-journey

name	map-a-customer-journey
category	design
description	Map an evidence-based customer journey across goals, actions, channels, system states, handoffs, failures, and recovery. Use when diagnosing a real end-to-end experience or aligning teams around one customer outcome.

map-a-customer-journey

Create a decision artifact grounded in observed behavior. Limit the map to one audience, scenario, and outcome so stages and breakdowns remain actionable.

Inputs

• Define the customer or user group, starting event, desired outcome, time span, and channels in scope.
• Gather research, support cases, analytics, process records, service blueprints, and frontline knowledge.
• Record evidence source, date, segment, and limitations for each claim.

Procedure

1. Write the journey question and explicit boundaries, including what happens before and after.
2. Identify stages from changes in customer goal or system state rather than internal department names.
3. For each stage, record customer goal, action, question, channel, input, output, and observable result.
4. Add system state, backstage process, owner, handoff, policy, dependency, and wait time.
5. Include thoughts or emotions only when direct evidence supports them.
6. Mark breakdowns, dead ends, repeated work, access barriers, uncertainty, and recovery behavior.
7. Attach qualitative and quantitative evidence to important moments.
8. Distinguish common paths, meaningful variants, and unsupported assumptions.
9. Prioritize opportunities by customer harm, frequency, strategic relevance, feasibility, and evidence strength.
10. Review the map with customers and frontline owners, then assign next investigations or changes.

Boundaries

Never invent customer feelings, merge incompatible segments for convenience, or expose identifiable research participants. Do not use the map to blame a team. Label missing evidence and obtain consent for any new research or recording.

Done

• The map names one customer group, scenario, start, outcome, and scope
• Stages connect customer actions to system state, ownership, handoffs, and evidence
• Breakdowns, variants, assumptions, and recovery paths are visibly distinguished
• Prioritized opportunities have owners and a defined next test or decision