Journey mapping in retail: why the map is not the outcome

Why 90% of journey maps end up on a wall

Almost every journey map follows a sad pattern: it gets built in a workshop, printed on a fancy wall, everyone learns the journey, and the wall just stays there. Three months later nobody remembers why it mattered.

What I've seen fail:

• The journey is documented, not operated. A map describes; a system lets you decide what to do on the next order.
• Friction is enumerated, not prioritized. Without priority, nobody knows what to touch first.
• The map lives with CX; it never reaches sales, ops or product. The journey crosses areas; with no clear owner, the wall stays alone.

My methodology: from friction to system

The approach I use has three layers, and the map is only the first.

Layer 1 — The map: moments + friction + data

I build the journey with three axes at once:

• Moments: purchase, replenishment, incident, onboarding, offboarding. Five, not thirty.
• Observable friction: what the customer does or says, not what we feel internally. VoC, CRM events, tickets, complaint rate.
• Data present: which system records that moment today? Who owns it? Is it measured?

If a friction has no owner and no metric, that's the first problem.

Layer 2 — Prioritization: impact, effort, experience

Every friction gets scored on three dimensions:

• Business impact (potential churn, LTV, operational cost).
• Effort required (person-days + integrations + political complexity).
• Experience delivered to the customer (what do they feel after the change?).

Prioritizing by impact alone falls into "the most urgent is the only thing". Prioritizing by experience alone doesn't pay the ROI. The trick is the cut: the high impact + low current experience quadrant is where ROI of change is cleanest.

Layer 3 — The system: owner, rules, data

Here's where the map stops being a map. Each priority friction becomes a system:

• Owner (a person, not a committee).
• Rules (what happens at each moment, what decision is taken).
• Data (what's measured, in which system, on what cadence).

This turns the journey map into a collection of mini-systems somebody operates. Same as product work: you don't solve the whole map; you solve the points that hurt most, with an owner.

A trap I learned the hard way

When prioritizing retail journeys, the most expensive bias is prioritizing the friction that shouts loudest, not the one that moves the most LTV.

The friction of an enterprise Tier-1 customer who barely complains but did renegotiate the contract: costs millions. The friction of a small customer who complains three times a week: costs less but sounds louder.

The fix isn't to silence voice of customer. The fix is to cross VoC with LTV and actual churn, not singular complaints. That crossing is what turns a map into decisions.

How to start without a workshop

1. Pick one journey (repeat purchase or onboarding are most revealing).
2. List the 5 most important moments. If you have more than 5, you're imagining.
3. For each moment, note: owner, metric, observable friction.
4. If you can't fill all three: that's a gap in your operations, not a journey problem.

The map this sequence produces is actionable in a week. If you want it in your operation with your real moments, I respond within 1 business day with a scoping brief that maps your journey → your owners → your data.