CX maps that operators will actually use

A journey map is not a mural. It is a punch list.

We ask CX teams to name: the moment of pain, the owner, the metric, and the smallest test. Everything else is decoration. If the map cannot be read in a stand-up, it will not be used in a stand-up.

I have watched beautiful maps die on SharePoint at a supermarket group, a telco, a Canadian bank, a health service, and a top-tier law firm. Woolworths. Singtel. RBC. NHS Digital. Allens client intake. Different customers. Same death. The artefact was optimised for a steering pack, not for a shift lead, a store manager, a branch ops lead, a ward clerk, or a practice coordinator.

Customer Experience as a workshop pillar is not "empathy." Empathy is table stakes. CX that pays is an operating list: who does what by when, how we know it moved, what we will try this week.

Why operators ignore your map

Operators are not anti-design. They are anti-artefacts that do not change the queue.

A Woolworths store or fulfilment lead cares about the moment a substitute fails, a delivery window slips, or a refund takes three conversations. A Singtel frontline lead cares about the moment a plan change creates a bill shock and a second call. An RBC branch or digital-ops lead cares about the moment onboarding stalls on a document nobody warned the customer about. An NHS Digital or trust service owner cares about the moment a referral disappears between systems. An Allens coordinator cares about the moment a client sends a dump of documents and three partners assume someone else scoped it.

Your map named all of those in swimlanes, in a 36-inch PDF, in a colour key that needs a legend. The operator needed a list:

1. Seam
2. Owner (role, not "the bank")
3. Metric this week
4. Smallest test
5. Date we look again

That list fits on a wall. That list survives a stand-up. That list is CX.

If the map cannot be read in a stand-up, it will not be used in a stand-up.

The one-page map

Use this structure. One seam per row. Ten seams is too many. Three to five is a programme.

Seam (customer words)	Owner	Metric	Smallest test	Look-again date
"I do not know if my substitution is acceptable"	Fulfilment lead, named banner	Repeat contacts per order	Script + photo confirm on 50 orders	14 days
"My bill doubled after a plan change"	Care ops, named segment	Second-call rate	Plain-language SMS + 24h callback	14 days
"You asked for the same document twice"	Onboarding ops	Cycle time, drop-off	Checklist sent before the appointment	21 days
"My referral vanished"	Service manager + digital owner	Lost-referral count	Human concierge for one pathway	30 days
"Who is scoping this matter?"	Practice coordinator + partner	Time to first scoped email	Intake template on the next 20 matters	21 days

Woolworths-shaped grocery and fulfilment work lives in row one. Singtel-shaped telco care lives in row two. RBC-shaped banking onboarding lives in row three. NHS Digital-shaped (or trust-shaped) pathways live in row four. Allens-shaped legal intake lives in row five.

You do not need the persona paragraph on this page. You needed it in the research. The operator needed the row.

What to cut from the mural

Cut the phases that exist to make the slide symmetric. "Awareness, consideration, purchase, use, loyalty" is a textbook. It is not a punch list. Cut the emotion curve unless a number moves with it. Cut the channel icons unless a channel owner is named. Cut the 40 opportunities. Keep the five you will fund.

Keep the quotes if they are short and true. A Woolworths customer saying "just tell me what you substituted" is better than a journey stage called Delight. A Singtel customer saying "I only called because the SMS was unclear" is better than a box called Educate. An RBC client saying "I already uploaded this" is better than a stage called Verify. An NHS patient saying "I do not know if the GP received it" is better than a stage called Refer. An Allens client saying "I still do not know who is doing the work" is better than a stage called Engage.

How to build the punch list in a room

Hour 1. Walk the last real case, not a persona. Pull a ticket, an order, a matter, a referral. Woolworths: last week's failed substitute. Singtel: last week's bill-shock call. RBC: last week's abandoned onboarding. NHS: last week's lost pathway. Allens: last month's bloated intake.

Hour 2. Mark the seams where the customer repeated themselves or the work bounced. Max five.

Hour 3. Assign owners who are in the room or who will be phoned before close. No owner, no row.

Hour 4. Pick the smallest test per seam. Script, checklist, concierge, SMS, template. Not a platform.

Hour 5. Write the metric and the look-again date. Circulate the one-pager. Do not send the mural unless someone asks, and even then send it as an appendix.

That is Customer Experience T&E with a residue. Collective Campus runs this shape because the other shape (a two-day journey-mapping festival) produces a PDF the SharePoint ghost will enjoy.

Operators, not "the business"

Stop saying "we need to socialise this with the business." Name the role.

• Woolworths: store manager, fulfilment lead, online ops, complaints.
• Singtel: care floor, billing ops, retail, a product owner for the plan.
• RBC: branch ops, digital onboarding, KYC ops, a journey owner.
• NHS Digital / a trust: service manager, clinician lead, digital owner, call handler.
• Allens: practice coordinator, partner, knowledge, billing.

If those people did not mark the page, the page is a rumour.

Metrics that survive a stand-up

Pick metrics the operator already believes.

Repeat contact. Grocery, telco, bank, health, legal: if they came back, you failed a seam.

Cycle time. Order to door. Plan change to accurate bill. Application to ready-to-use. Referral to first appointment. Intake to scoped email.

Exceptions and rework. Substitutions rejected. Bills reversed. Documents re-requested. Referrals re-keyed. Matters re-scoped.

Complaints per volume. Not a vanity NPS of the workshop.

RBC and other Canadian banks already live inside conduct and complaint reporting. NHS services live inside waiting-time and incident physics. Woolworths lives inside availability and substitution physics. Singtel lives inside billing and churn physics. Allens lives inside utilisation and client-experience physics that partners will not call CX but will fund if it reduces rework.

Wall policy

One wall. One page. Five rows. Owners in ink. Look-again dates circled. Tests older than 30 days without a result get a red line and a funeral. New research goes to the appendix, not the wall.

If Woolworths, Singtel, RBC, NHS Digital, or Allens ran only that policy for a quarter, they would retire half their CX artefacts and move the seams that actually hurt. That is the point. The mural was never the point.

Frontline language is the quality bar

If a Woolworths team leader cannot say the row in one breath, rewrite it. If a Singtel floor coach needs the facilitator to decode "moments of truth," rewrite it. If an RBC onboarding officer cannot see themselves in the owner cell, you named a department, not a person. If an NHS ward clerk or call handler would laugh at your stage names, you wrote a consultancy deliverable. If an Allens coordinator would have to translate the page for a partner, you wrote for a conference.

Quality is not visual polish. Quality is whether the next stand-up uses the page without you. That is why we ask for a punch list. Journey maps that require a legend require a priest. Operators do not keep priests.

Research still matters. It does not get the wall.

We are not anti-research. Woolworths online and fulfilment teams need to know why substitutions fail. Singtel needs to know which plan-change SMSs create the second call. RBC needs to know which document request is the drop-off. NHS Digital-shaped services need to know where the referral actually dies (often between systems, not in a persona's "feelings"). Allens needs to know which matter types produce the foggy first email.

Do the research. Put the evidence in an appendix or a short note. Promote to the wall only what has an owner, a metric, and a test. If your research vendor's contract rewards a 60-page journey, rewrite the contract. Buy a punch list and two weeks of aftercare. Collective Campus would rather be hired for the second.

A 14-day operating rhythm

CX programmes die when the map is "done." Treat the punch list like a backlog.

• Twice a week: 15 minutes, only red rows (tests that slipped or metrics that got worse).
• Every 14 days: look-again on each live test. Keep, kill, or rewrite the row.
• Every 30 days: funeral for any row with no result. Public, short, written.
• Never: a quarterly "journey refresh" that redraws swimlanes and changes nothing on the floor.

Woolworths-shaped and Singtel-shaped operations already have daily huddles. Hang the list there. RBC and NHS already have performance forums. Hang the list there. Allens has practice meetings. Hang the list there. If you need a new CX steering pack to talk about the list, you have added a room. See the productivity piece. Delete one to add one.

A briefing for the CCO

One page to the Chief Customer Officer, or the retail GM, or the managing partner:

We will not deliver a mural. We will deliver five seams with owners. Each seam will have a test in 14 days. We will report repeat contact, cycle time, or rework. We will kill tests that do not move a number. We will not book a sequel mapping workshop.

If they want the mural anyway, they want theatre. You now know. Spend the budget on the floor.

A five-line punch list for a bank or a telco

Operators do not keep swimlanes. They keep lists they can read in a huddle. Here is a five-line punch list written the way a floor coach at Telstra or a digital-ops lead at NAB, RBC, or ANZ would actually use it. Steal the rows. Change the nouns. Do not add a persona paragraph to the wall.

Line 1. Seam: "I already sent this document and you asked again." Owner: onboarding ops lead, named. Metric: repeat document requests per application. Smallest test: checklist sent 48 hours before the appointment, on the next 40 files. Look-again: 21 days.

Line 2. Seam: "My plan changed and the first bill looked like a different product." Owner: care ops for that segment, named. Metric: second-call rate in seven days. Smallest test: plain-language SMS plus a 24-hour callback on one plan family. Look-again: 14 days.

Line 3. Seam: "I do not know if the application is alive." Owner: journey owner plus branch or retail ops. Metric: inbound "where is my application" contacts. Smallest test: status SMS at two existing milestones, no new portal. Look-again: 21 days.

Line 4. Seam: "You transferred me and I started again." Owner: floor coach plus the receiving queue owner. Metric: warm-transfer failures, or reopened tickets. Smallest test: a three-line handoff script the receiving agent reads back. Look-again: 14 days.

Line 5. Seam: "The fee appeared without a sentence I could use." Owner: product owner for the fee plus complaints. Metric: fee-related complaints per volume. Smallest test: one-sentence explanation on the existing notice, marked by conduct. Look-again: 21 days.

NAB-shaped and RBC-shaped banking live in lines 1, 3, and 5. Telstra-shaped and Singtel-shaped telco care live in lines 2 and 4. ANZ-shaped squads can hang any of these on a heartbeat. Lloyds-shaped UK retail can hang the fee and onboarding lines on a consumer-duty conversation. Do not invent a movement number in the first week. Write the baseline you already have. If you do not have a baseline, the first 21 days are for counting, not for a mural refresh.

A practical wall rule: five lines, owners in ink, tests older than 30 days without a result get a red line and a funeral. New research goes to the appendix.

The 21-day look-again

CX programmes die when the map is "done." A look-again is a 25-minute room with a job: keep, kill, or rewrite each live row. It is not a journey refresh. It is not a steering pack. Book it the day you write the punch list. Put it on the same cadence as a huddle the operator already attends.

Before the room (a paragraph, not a pack). For each of the five lines: what we tried, what the metric did, what blocked us, the ask. If a line has no result, write "no result" and prepare the funeral sentence. Honesty is the quality bar.

In the room. Owner of the line speaks first. Operator speaks second. Facilitators do not narrate. Three options only: keep the test, kill it, or rewrite the seam because we framed the wrong pain. No new swimlane. No new persona.

After the room. Same-day residue: which lines live, which died, who owns the next 21 days. Circulate to the floor, not only to the CCO. Woolworths-shaped fulfilment huddles, Singtel-shaped care floors, RBC and NHS performance forums, Allens practice meetings: hang the updated list where the work is.

Day 7 is allowed as a stuck-work check if a test never started. Day 21 is the look-again. Day 30 is the funeral for anything still empty. If you need a quarterly "CX showcase" to talk about the list, you have added a room. Delete one to add one.

A practical look-again invite:

21-day look-again, 25 minutes. Bring the five-line list and the numbers you already believe. We will keep, kill, or rewrite. We will not redraw the mural. If your line has no result, bring a funeral sentence.