FieldEdge Academy ← Back to The Journey

FieldEdge Academy · Customer Experience Management

The Journey Toolkit

Eleven practical tools to turn customer insight into measurable CX action — from signal to funded, owned, governed improvement. Work directly in this page: every field saves in your browser.

The eleven tools — in journey order

How to use this page. Click any field and type — your work autosaves in this browser. Scoring tools calculate as you go. Use Export HTML to download a copy with your entries baked in, or Print / Save PDF for a clean handout (each tool prints on its own page). These tools are introduced and practiced under pressure in The Journey program.

01

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.

How to use it

  1. Describe the source, volume, and a few example quotes or tickets you're working from.
  2. Generate the prompt, then paste it into your AI tool of choice.
  3. Feed the structured themes it returns into the CX Signal Scanner as your evidence rows.

Watch out

An AI summary compresses evidence, it doesn't replace it. Before you act on a theme, trace it back to the real customer quotes — a fabricated or overstated pattern is worse than no summary at all.

Working area — build the summary prompt

Reusable AI Prompt

02

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.

How to use it

  1. List each signal in one factual line and name its source.
  2. Grade it on Frequency (how often it appears), Impact (effect on customer behavior or value), and Trend (getting worse, stable, improving).
  3. Read the verdict: Act signals feed the journey map; Watch signals get a review date; Noise gets archived — politely.

Watch out

The loudest voice is not the strongest signal. An angry email forwarded by the CEO is one data point. Grade it like every other row — frequency and trend protect you from anecdote-driven priorities.

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.

03

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.

How to use it

  1. Pick one customer the signals point to — not the easiest one, the most material one.
  2. Fill the six cells from evidence. Every claim should trace to a scanner row, a verbatim, or data.
  3. Write the quote last: one sentence this customer would actually say about the experience today.

Watch out

Internal averages wear disguises. If a cell reads like your segmentation deck (“mid-market, growth-oriented”), it’s not a persona — it’s a spreadsheet. Use their words, their situation, their pressure.

Working area — one customer, six cells

Who they are
What they're trying to achieve
Pressures & constraints
Where the experience hurts
Channels & touchpoints they use
What success looks like to them
In their words (one quote)
Evidence sources for this persona
04

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.

How to use it

  1. Walk the lifecycle stage by stage and list every interaction — human, digital, paper, silence included.
  2. Name one accountable owner per touchpoint. “Everyone” is spelled “no one.”
  3. Mark the evidence column honestly. Touchpoints with no owner and no evidence are your blind spots.

Watch out

The gaps between touchpoints are touchpoints. The three weeks of silence between signature and kickoff is an interaction the customer experiences vividly. Inventory the handoffs, not just the contacts.

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.

05

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.

How to use it

  1. Set four to six stages across the top — the customer’s milestones, not your internal process steps.
  2. Fill each column top to bottom: what the customer does, where the friction is, how they feel.
  3. Grade every column’s evidence: Verified, Partial, or Assumption. Assumptions are allowed — hiding them is not.

Watch out

A map that decorates a wall governs nothing. If two functions disagree about a stage (Sales says onboarding takes two weeks; Service says six), the map records the conflict and the evidence grade — that disagreement is a finding, not a formatting problem.

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.

06

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.

How to use it

  1. Bring the candidate moments nominated on your journey map.
  2. Score each 1–5 on the four criteria. Scores need one line of justification each — that debate is the exercise.
  3. The tool totals and ranks automatically. Take the top one or two into diagnosis and action — not five.

Watch out

Beloved is not the same as decisive. The well-liked welcome kit scores high on warmth and low on behavior change. If a moment doesn’t move renewal, expansion, churn, or referral, it is not a moment of truth — however nice it feels.

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.

07

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.

How to use it

  1. Describe the failing moment and its observable symptom (what the customer sees or feels).
  2. Classify the gap type — the same symptom can hide very different causes.
  3. Write the fix that matches the type. A delivery gap is not solved by a communication campaign.

Watch out

Beware the fix that promises before it repairs. Launching a brand campaign over a broken delivery process widens the expectation gap — you are now advertising the failure. Capability first, promise second.

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.

08

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.

How to use it

  1. Start on the right: which business outcome is this moment supposed to move (retention, expansion, cost-to-serve, referral revenue)?
  2. Work backwards: what customer behavior drives that outcome, and what experience metric predicts the behavior?
  3. Set a baseline, a target, and an owner for each metric. A metric without an owner is a decoration.

Watch out

Satisfaction is not a business case. “NPS up” convinces no CFO. The middle column — observable customer behavior — is what makes the tree credible. If the behavior link is a guess, grade it as one and plan to test it.

Working area — experience → behavior → business

Experience metric

Customer behavior

Business outcome

Link confidence — what is verified vs. assumed
Measurement plan
09

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.

How to use it

  1. Blueprint one moment of truth, not the whole journey — three to five customer steps maximum.
  2. Fill each column downwards: what the customer does, what they see, what happens out of sight, which systems and teams are involved.
  3. Mark the failure point and its owner. Most failures live below the line of visibility — in handoffs between the rows.

Watch out

Do not blueprint to admire the complexity. The output is one sentence: “this moment fails because X breaks between team A and system B — and here is who owns the repair.” If the blueprint doesn’t produce that sentence, keep digging.

Working area — one moment, behind the scenes

Moment being blueprinted
Failure sentence (fill last)
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 —

10

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.

How to use it

  1. Write the customer problem in customer language — no internal jargon, no solution smuggled into the problem statement.
  2. Let the evidence do the persuading: scanner rows, map grades, prioritizer scores, blueprint findings.
  3. Close every accountability loop: one owner, one KPI, one timeline, one governance routine. Then ask for the decision.

Watch out

A brief that cannot be refused cannot be approved either. Name the risk honestly and state what you are not doing. Leaders fund recommendations that show their trade-offs — not pitches that hide them.

Working area — the manager-ready brief

1 · Customer problem
2 · Evidence base
3 · Priority moment of truth
4 · Owner
5 · CX KPI
6 · Timeline
7 · Risk
8 · Expected impact
9 · Governance routine
The ask (one sentence)
Decision & date (for the approver)
11

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.

How to use it

  1. Name one journey owner — a person, not a committee — and give them real decision rights.
  2. Set the review rhythm: which forum looks at the journey, with which data refreshed, how often.
  3. Define the update triggers: the events that force the map to change, so it tracks reality instead of history.

Watch out

A quarterly slide is not governance. Governance means someone can reallocate budget, stop an initiative, or escalate — based on what the journey data says. If the review can’t change a decision, it’s theatre.

Working area — design the routine

Journey owner
Decision rights
Review forum & cadence
Data refreshed before each review
Map update triggers
Escalation path
Cross-functional commitments
First 90 days

Tools are where the discipline starts. Practice is where it holds.

Every tool on this page is practiced under pressure in The Journey — through interactive scenarios, live Teams missions, and the in-person Field Seminar, using the Northstar Mobility case or your own journeys.

Request a pilot Get the CX Field Guide