Customer Journey

A customer journey map traces stages, touchpoints, customer actions, thoughts/emotions, and pain points from first awareness through retention or advocacy. It is the experience lens on the same segments personas describe — showing where friction kills conversion or expansion.

Journey maps can be current-state (what happens today) or future-state (target experience after redesign).

Conversion and churn are journey problems, not single-screen UI bugs. Mapping exposes handoffs — signup to onboarding, sales to success — where accounts die. It aligns product, marketing, and support on measurable fixes instead of departmental blame.

For services, journeys reveal where clients wait, worry, or need reassurance between workshops.

Build after personas exist, before prototype or major UX investments. Use current-state maps for diagnostic sprints; future-state maps after strategy sets differentiation.

Re-map when activation or retention metrics move materially or when you add a channel.

1. Pick persona and scenario — one job-to-be-done per map.
2. Define stages (e.g. discover, evaluate, buy, onboard, use, expand).
3. List touchpoints per stage — ads, site, sales call, product, billing, support.
4. Capture actions and emotions honestly (include anxiety peaks).
5. Mark pain points and delights with severity.
6. Attach metrics — conversion %, time-to-value, CSAT — where known.
7. Prioritise fixes — top three pains with owners.
8. Link to buyer utility map for Blue Ocean utility leaps.

• Stages match how customers describe the process, not internal sprint names.
• Emotion line or notes show peaks and valleys, not flat "neutral."
• Pain points specific ("wait 3 days for SSO") with evidence.
• Backstage processes noted when they cause visible friction.
• Future-state map shows what changes per stage, not vague "better UX."

• Mapping the happy path only — missing failure routes and support loops.
• Too granular micro-clicks — unreadable wall of sticky notes.
• No metrics — cannot tell if fixes worked.
• Internal process map disguised as customer journey.
• Multiple personas crammed into one emotional line.
• Journey workshop without sales/support in the room — blind spots remain.

Northvale Systems supplier journey: invite → document upload → validation queue (pain: 12-day wait) → approval → PO eligibility. Future-state adds status tracker and rejected-document reasons in one screen — cut resubmission loops.

Acme Analytics journey for finance controller evaluating revenue analytics. Discover via peer webinar; evaluate with sandbox connecting Stripe; buy needs security review stage (anxiety peak); onboard requires chart-of-accounts mapping (pain: 5-day delay); use weekly board export; expand to departmental dashboards. Metrics: 40% drop at security review; mapping led to pre-built security pack and CISO office hours — activation improved 12 points.

Future-state shortened security stage with shared responsibility matrix upfront.

Harbor Consulting journey for plant manager hiring lean diagnostic. Referral intro call → site visit scheduling (pain: 2-week wait) → diagnostic workshop → report readout → proposal (anxiety: price shock) → engagement kickoff. Harbor added fixed-price diagnostic summary within 48 hours and a sample report PDF at evaluate stage — shortened sales cycle by three weeks.

Emotion peak at proposal addressed with milestone-based pricing on map.

Clearwater Initiative journey: train committee → weekly test → lab SMS → community meeting if fail → repair ticket. Pain peak at repair wait — added local mechanic retainer to shorten stage.

Use /journeys (also covers customer-journey-map alias) on schema customer-journey with stage rows CJM-ST-01, touchpoints CJM-TP-01, pains CJM-PP-01. CX phase chip opens same guide. Pairs with buyer utility map and personas. Prefix CJM-. Strategy Pack journeys phase generates initial draft you refine.