Read Signals · eLearning · Phase 1
AI Signal Summary Prompt
When to use it: right after you've pulled raw customer feedback together, before it goes into the CX Signal Scanner. Teams that skip this step dump a wall of tickets and verbatims on the scanner and lose the pattern in the noise. This tool builds a reusable AI prompt that turns raw signals into a structured theme summary in minutes.
Working area — build the summary prompt
Reusable AI Prompt
Read Signals · E-Learning · Phase 1
CX Signal Scanner
When to use it: before mapping anything. Complaints, NPS verbatims, tickets, churn notes, sales feedback, and digital clues arrive loud and unsorted. The Scanner separates material evidence from noise — so the journey work starts from signals, not anecdotes.
Working area — grade your signals
| Signal (one factual line) | Source | Frequency | Impact | Trend | Verdict | Next step |
|---|---|---|---|---|---|---|
| – | ||||||
| – | ||||||
| – | ||||||
| – | ||||||
| – |
Verdict logic: total F + I + T of 7–9 = Act (feed the journey map) · 5–6 = Watch (set a review date) · 3–4 = Noise (archive). Impact of 3 always promotes at least to Watch.
Read Signals · E-Learning · Phase 1
Customer Persona Snapshot
When to use it: before drawing the journey. A journey mapped for “the average customer” represents nobody. The Snapshot anchors the map in one concrete customer reality — a person or account type your evidence actually describes.
Working area — one customer, six cells
Read Signals · E-Learning · Phase 1
Touchpoint Inventory
When to use it: before the mapping session. Teams consistently underestimate how many interactions a customer has — and how many have no owner. The Inventory lists every touchpoint, who owns it, and whether you actually have evidence about it.
Working area — inventory the interactions
| Journey stage | Touchpoint / interaction | Channel | Owner (one name / role) | Evidence? | Known issues / notes |
|---|---|---|---|---|---|
Blind-spot rule: a touchpoint with no owner and no evidence cannot appear on your journey map as a fact — only as an assumption to verify.
Map Reality · Live Online Sales Simulation · Phase 2
Journey Map Builder
When to use it: once signals are graded, the persona is real, and the touchpoints are inventoried. The Builder maps what the customer actually experiences — actions, emotions, friction — and grades every claim by evidence, so the map can defend itself in front of a skeptical leader.
Working area — one shared canvas, four stages
| Lane | Stage 1 | Stage 2 | Stage 3 | Stage 4 |
|---|---|---|---|---|
| Customer action | ||||
| Key touchpoints | ||||
| Emotion | ||||
| Friction & failure points | ||||
| Evidence grade | ||||
| Internal owner | ||||
| Candidate moments of truth |
Evidence grades: ● Verified = data or repeated direct observation · ◔ Partial = single source or dated · ○ Assumption = internal belief, to be tested. Candidate moments of truth flow into Tool 05.
Map Reality · Live Online Sales Simulation · Phase 2
Moment-of-Truth Prioritizer
When to use it: when the map shows more broken moments than the budget can fix. A moment of truth is an interaction that changes customer behavior — renewal, expansion, churn, referral. The Prioritizer scores the candidates so the choice is defensible, not popular.
Working area — score, then let the ranking argue for you
| Candidate moment | Customer behavior impact (1–5) | Business value impact (1–5) | Evidence strength (1–5) | Feasibility to improve (1–5) | Score | Rank | Justification (one line) |
|---|---|---|---|---|---|---|---|
| – | – | ||||||
| – | – | ||||||
| – | – | ||||||
| – | – | ||||||
| – | – |
Reading the ranking: the top-ranked moment(s) are highlighted automatically. A high behavior/value score with weak evidence means: verify before you invest. Doubling the weight of behavior + value over feasibility is deliberate — easy is not the same as important.
Map Reality · Live Online Sales Simulation · Phase 2
Experience Gap Diagnosis
When to use it: after a moment of truth is chosen and before a fix is proposed. Most CX fixes fail because they treat the symptom, not the gap. This tool forces the question: why does this moment fail — and matches the fix to the gap type.
Working area — diagnose before you prescribe
| Failing moment | Observable symptom | Gap type | Root cause (evidence-based) | Fix matched to the gap |
|---|---|---|---|---|
Gap-to-fix logic: Expectation → fix the promise or the reality · Design → redesign the process · Delivery → training, staffing, tools, accountability · Perception → communicate the value delivered · Recovery → build the service-recovery routine.
Move to Action · Field Seminar · Phase 3
CX KPI Tree
When to use it: when someone asks “what will this actually change?” The Tree connects an experience metric to a customer behavior to a business outcome. If you cannot draw the branch, you cannot defend the investment.
Working area — experience → behavior → business
Experience metric
Customer behavior
Business outcome
Move to Action · Field Seminar · Phase 3
Service Blueprint Lite
When to use it: when a priority moment keeps failing and nobody can say exactly why. The Blueprint exposes what happens behind the moment — frontstage actions, backstage processes, systems, and handoffs — so the fix lands where the failure lives.
Working area — one moment, behind the scenes
| Lane | Step 1 | Step 2 | Step 3 |
|---|---|---|---|
| Customer action | |||
| Frontstage (visible to customer) | |||
| Backstage (invisible) | |||
| Systems & support processes | |||
| Failure point & handoff risk | |||
| Owner of the repair |
— dashed line = line of visibility: everything below it is invisible to the customer, and where most failures hide —
Move to Action · Field Seminar · Phase 3
CX Action Brief
When to use it: when it’s time to ask for a decision. The Brief is the final deliverable of The Journey: one page leadership can review, fund, assign, and govern. Nine fields — if one is empty, the recommendation is not ready.
Working area — the manager-ready brief
Move to Action · Field Seminar · Phase 3
Journey Governance Canvas
When to use it: the day the action brief is approved. Most journey maps die in the ninety days after the workshop — not from bad mapping, but from missing ownership and review routines. The Canvas designs the routine that keeps the map alive.
Working area — design the routine