CX Task Force Playbook · Innovation & Design

How Great Experiences
Get Built

A complete visual guide to the frameworks, tools, and methodologies CX leaders deploy — from first insight to scaled experience.

① Discover 1½ Synthesise ② Define ③ Design ④ Prioritize ⑤ Build & Test 3K Lean ⑥ Measure
↓   scroll to explore
01
Phase One
Discover & Understand

Before designing anything, CX leaders immerse themselves in the customer's world. This phase is about generating raw human insight — the fuel for everything that follows.

🔍
Design Thinking
Human-Centered Process

The foundational 5-stage process that keeps teams anchored to human needs throughout the entire innovation cycle.

Empathize
›
Define
›
Ideate
›
Prototype
›
Test
Iterative — loop back at any stage based on learnings
🧠
Empathy Mapping
Customer Understanding Tool

A 4-quadrant workshop tool that helps teams get inside the customer's head before designing any solution.

💭 Think & Feel "Am I getting value? I'm frustrated with wait times."
👁️ See "Long queues, confusing signage, staff look stressed."
👂 Hear "Friends say: just use the app. Ads say: fast & easy."
💬 Say & Do "Sighs. Checks phone. Asks staff for help twice."
⚙️
Jobs-to-Be-Done
Motivation Framework

Customers don't buy products — they hire them to do a job. JTBD uncovers the deeper motivation behind every interaction.

🔧
Functional
Job
😊
Emotional
Job
👥
Social
Job
Example: "Help me feel in control of my finances" (emotional) not just "send money" (functional)
💡
Unarticulated Customer Needs
Jeanne Liedtka · Darden / UVA

Customers can only describe needs they’re already aware of. The richest design opportunities live in what they can’t yet say but would immediately recognise — the gap surveys can never reach.

💬 Articulated
“I want faster service.” — What surveys capture. Already known.
👁 Observable
Re-checks phone after ordering (anxiety). Never mentions it. Visible only through observation.
✨ Unarticulated
“I want to feel known before I reach the counter.” — Never on a feedback form. Immediately recognised when delivered.
LIEDTKA’S 4-QUESTION ARC
What is?
Current reality. Empathy & observation.
What if?
Possibilities. Reframe & imagine.
What wows?
Concepts customers immediately recognise.
What works?
Prototype. Test. Learn. Ship.
📡
Voice of Customer (VoC)
Listening Program · Formal & Informal Channels

Systematic multi-channel capture of customer feedback. Combines formal structured listening (surveys, interviews, tickets) with informal ambient signals (social, behavioural, observed). Real intelligence comes from both.

📝 Formal channels Structured · Solicited · Recorded
📊
Surveys
NPS · CSAT · CES
🎙️
Interviews
Depth · Context
💬
Support
Tickets · Chats
👁 Informal channels Ambient · Unsolicited · Observed
📱
Social
Listening · Sentiment
🖱️
Behavioural
Clicks · Drop-offs
🔍
In-Field
Ethnography · Obs.
💡 Why both matter: Formal channels tell you what customers say. Informal channels reveal what customers do — and these often disagree. Programs relying on surveys alone systematically miss the gap between stated and actual experience.
💬
Voice of the Employee (VoE)
VoE · Internal Insight · Formal & Informal Channels

Employees at the service interface hold knowledge customers and managers never share with each other. Like VoC, structured VoE combines formal measurement (eNPS, reviews, exit interviews) with informal day-to-day signals (debriefs, suggestions, hallway feedback).

📝 Formal channels Scheduled · Quantified · Recorded
📈
eNPS Survey
Pulse · Engagement
📋
Reviews
Performance · 360°
👋
Exit Interviews
Departure insight
👁 Informal channels Ambient · Conversational · Continuous
🗣️
Shift Debriefs
End-of-shift · Stand-ups
💭
Suggestion Box
Slack · Anon channel
☕
Skip-level / 1:1
Coffee chat · Hallway
💡 The classic gap: Employee NPS routinely runs below customer NPS in struggling organisations. Front-line staff see friction before customers report it. Formal eNPS quantifies the gap; informal debriefs explain its cause.
🐝
Fly on the Wall
Pure Observation · Ethnography

The researcher is present but invisible — observing natural behaviour without any interaction. Reveals what customers actually do, not what they say they do.

Rule: No eye contact. No questions. No reactions. Pure silent recording.
👁 Observation example: Behaviours you only notice by being present — phones rechecked for confirmation, counter scans for missing orders, silent walk-outs. None of it captured in surveys.
✓ Unfiltered
no observer effect
✓ Behaviour
not self-report
✓ Context
seen in the wild
👟
Walk a Mile
Customer Immersion

The researcher becomes the customer and lives the full end-to-end experience. Different from Gemba (observing the workplace) — this is being the user across every touchpoint for days or weeks.

📱Download the app for the first time as a new customer
🚶Order from 3 different stores across 5 days
⭐Attempt to earn and redeem loyalty rewards
📞Contact customer support with a real problem
"The checkout has 7 different screens and I have a PhD in UX." — Leila, Task Force lead, after her Walk a Mile week.
🧀
Fishbone Diagram
Ishikawa · Cause & Effect

Traces every symptom back to root causes across six structured categories — preventing teams from prematurely converging on the most visible problem (usually Technology).

CX Issue PEOPLE No CX training Staff turnover PROCESS Too many steps No handoff SLA TECHNOLOGY Siloed systems No personalisation POLICY Revenue over CX No CX ownership ENVIRONMENT Poor wayfinding Channel friction MEASUREMENT Lagging only No CES tracked
Example: Root-cause analysis often surfaces dozens of contributing factors — only a handful require technical fixes; the rest are policy or process.
SIX BONES: People · Process · Technology · Policy · Environment · Measurement
insights enter the
↓
1½
Phase One and a Half
Synthesise & Sensemake

The hardest-to-teach, easiest-to-skip phase. Research doesn't become insight — someone has to make it insight. Jon Kolko (frog design, Exposing the Magic of Design) formalised the methods teams use to bridge raw data and real design direction. Most CX playbooks jump from Discover straight to Define; the best ones stop here first.

🧩
Design Synthesis
Kolko · Sensemaking

The act of organising, pruning, and interpreting messy qualitative data to produce meaningful patterns and frameworks. It's the interpretive work between collection and design — what Kolko calls "the muddy middle."

DATA
raw signals
INFO
organized
KNOWLEDGE
synthesised
WISDOM
actionable
Most CX teams stop at "Information." Kolko's argument: the leap from Information → Knowledge is the money move.
→?
Abductive Reasoning
Best-Explanation Logic

The reasoning move that generates genuinely new ideas. Deduction confirms. Induction generalises. Abduction leaps — it proposes the best possible explanation for data we don't fully understand.

DEDUCTIVE
Rule → Conclusion   (certain, but no new ideas)
INDUCTIVE
Pattern → Rule   (likely, still no leaps)
ABDUCTIVE ★
Effect → Best Explanation   (might be wrong — but only way to new frames)
💥
Provocative Insight Statements
Kolko's Signature

Insights aren't findings. A Kolko-style insight is a provocative statement of truth — it takes a position, makes stakeholders uncomfortable, and resists watered-down consensus.

❌ FINDING
"Customers are dissatisfied with wait times."
✓ INSIGHT
"Waiting isn't the problem — waiting unseen is. Customers don't mind lines; they mind feeling invisible in them."
THE 4-PART TEST: Does it provoke? · Is it a truth claim? · About behaviour? · Implies design?
🧬
First Principles Thinking
Aristotle · Musk

Strip a problem to its irreducible truths and reason up from there. The opposite of reasoning by analogy — the cure for “that’s just how it’s done.”

❌ ANALOGY
“Coffee apps have 7 screens because all coffee apps do.”
✓ FIRST PRINCIPLES
“What does the customer fundamentally need? Recognition + caffeine. Everything else is convention. Rebuild from there.”
THE 3 MOVES: Spot the assumption · Decompose to atoms · Rebuild fresh
vs. 5 Whys: 5 Whys finds root cause inside a system. First principles asks whether the system should exist as it does.
🪜
The “So What?” Ladder
Liedtka · McKinsey

A three-rung discipline that forces every research finding to earn its place by producing meaning, then action. The cure for thick decks that leave readers asking “okay, but…?”

1. WHAT?
The observation. “31% of app orders abandon at payment.”
2. SO WHAT?
The meaning. “Friction lands at the moment we ask for commitment.”
3. NOW WHAT?
The action. “Move auth to the start. Or remove a screen.”
RULE: No finding ships without all three rungs answered.
📦
The Black Box Test
Storytelling Clarity Check

A simple test for your explanation: could a smart 10-year-old understand it? If yes, your story works. If no, you’re hiding behind jargon — and so will your audience.

❌ FAILS THE TEST
“We’re optimising the conversion funnel by reducing cognitive friction at the commitment touchpoint to drive cohort retention.”
✓ PASSES THE TEST
“Right now our regulars have to tap 7 times to order a coffee they get every day. We’re going to make it one tap. They’ll come back more.”
THE 4 RULES: One concrete image · Plain verbs · A “why it matters” · No acronyms unexplained
Pairs with So What: So What gives you meaning. Black Box Test makes that meaning land.
🔁
Reframing
Semantic Shift Tool

Force a design problem through a different semantic frame to generate new design implications. Not a metaphor — a generative move that makes things designable you couldn't previously see.

REFRAME: "The loyalty app" as...
🕯️
A ritual
openings, sequence, closings
🤵
A host
notices you, remembers
✉️
A letter
authored, to someone
🎹
An instrument
affordances, fluency
✕
Insight Combination
Kolko · Idea Generation

Forcibly pair a customer insight with a pattern from broader culture. The random collision triggers abductive leaps that single-discipline thinking rarely produces.

INSIGHT
"Regulars want to be known, not counted."
✕
PATTERN
Spotify Wrapped — emotional annual story
↓
→ EMERGING IDEA
"Coffee Wrapped" — your year in drinks, baristas, mornings. Shareable, emotional, proves we saw you.
🤝
Designing With, Not For
Participatory Design · Kolko

Kolko’s argument from Wicked Problems: customers aren’t subjects of study — they’re co-authors of the experience. The ladder of participation:

1 · AT
Design in isolation, hope for acceptance.
2 · FOR
Research customers, then design for them.
3 · WITH
Customers as active collaborators in the room.
4 · BY
Customers lead; the team facilitates.
📐
MECE Principle
Barbara Minto · McKinsey · Strategy Consulting Staple

Originated at McKinsey by Barbara Minto in The Pyramid Principle and adopted across BCG, Bain & every major consulting house. Every breakdown of a problem should be Mutually Exclusive (no overlap between buckets) and Collectively Exhaustive (nothing missing). It’s the discipline that turns messy CX synthesis into a defensible structure.

✗ Overlap
double-counted
Categories overlap. Same item counted twice. Findings look fuller than they are.
✗ Gap
missing
Categories are clean but incomplete. A whole bucket of customer behaviour goes unseen.
✓ MECE
complete & clean
Every observation fits exactly one bucket. Together they cover everything. Synthesis is defensible.
M · Mutually Exclusive
No item belongs in two categories. If a customer complaint can be filed under both “app issue” and “process issue,” your buckets aren’t clean. Tighten the definitions.
CE · Collectively Exhaustive
No customer pain falls outside your model. If 12% of complaints don’t fit any category, add “other” isn’t the fix — that’s a missing bucket telling you something.
Apply MECE in CX work
Root causes
Fishbone branches must be MECE
Segments
Personas with no overlap, no gaps
Journey stages
Every touchpoint belongs to one stage
Opportunity areas
No double-counted initiatives
insights flow into
↓
02
Phase Two
Define & Frame

Synthesize raw discoveries into a clear strategic direction. This is where insight becomes intent — the North Star is set, personas built, and the real problem named.

🔄
Outside-In Thinking
Strategic Lens

Flip the organizational perspective — design experiences from the customer's viewpoint inward, not from internal processes outward.

✗ Inside-Out · Default mode
Question: “How do we increase basket size?”
Optimises: Internal KPIs, margin, conversion
Asks: What can customer give us?
→
✓ Outside-In · The reframe
Question: “What does Priya need her morning to feel like?”
Optimises: Customer outcomes; revenue follows
Asks: What can we give customer?
🔁 The flip: Inside-out optimises for internal KPIs first; customer outcome follows. Outside-in starts with the customer’s emotional journey and lets the operational metrics align.
□○
Value Proposition Canvas
Osterwalder & Pigneur · Strategyzer

Tests whether your offering actually fits what customers need. Maps Pain Relievers, Gain Creators & Products against Customer Jobs, Pains & Gains. If they don’t align, you have a fit gap.

□ Value Map · Maker
✨ Gain Creators
"Your Usual" 1-tap reorder · Named greeting at counter · Surprise free upgrades
📦 Products & Services
Coffee app · In-store experience · Barista tablet · Loyalty programme
🩹 Pain Relievers
1-tap reorder · Queue position display · Order confirmation animation
Fit Assessment Example
⚠️
Gains gap. When the offering creates value the company wants rather than value the customer wants.
⚠️
Jobs gap. When the product solves a different job than the one customers are hiring it to do.
⚠️
Pains worsened. When optimisation in one area introduces new friction in another.
○ Customer Profile · Receiver
⭐ Gains
Feel recognised · Order ready on arrival · Frictionless start to the day
🎯 Jobs to be Done
Start the day in control · Feel known by the brand · Reliable caffeine
🔥 Pains
Anonymous transaction · Unpredictable wait · 14 taps to reorder · Upsell pressure
VALUE MAP MAKER — OFFERING ✨ Gain Creators 📦 Products & Services 🩹 Pain Relievers FIT? do they align? CUSTOMER PROFILE RECEIVER — NEEDS ⭐ Gains 🎯 Jobs to be Done 🔥 Pains
⚠️ The classic trap: Redesigns frequently add Gain Creators that serve the company (revenue, basket-size, upsell efficiency) while inadvertently worsening customer Pains (more taps, more interruptions, more anonymity). The VPC surfaces this misalignment before a single screen is built — the Value Map and Customer Profile must visibly fit.
vision enables
↓
03
Phase Three
Design the Experience

Map, blueprint, and canvas the ideal experience end-to-end. This is where the team translates vision into tangible, orchestrated journeys.

4D
The 4Ds Framework
CX Innovation Process

A double-diamond inspired process that structures the full innovation arc — from raw discovery through scaled delivery.

D
Discover
Research · VoC · Ethnography
D
Define
Problem framing · Insight synthesis
D
Develop
Ideation · Co-creation · Prototyping
D
Deliver
Pilot · Scale · Measure
🗺️
Customer Journey Mapping (CJM)
End-to-End Experience Visualization

Visualizes the complete customer journey across all touchpoints — capturing actions, emotions, and opportunities at every stage.

Stages
Aware
Consider
Purchase
Onboard
Use
Advocate
Touchpoints
Ad / Social
Website
Checkout
Welcome Email
App / Support
Referral
Emotion
😐
Neutral
🙂
Curious
😊
Hopeful
😟
Frustrated
🙂
Engaged
😍
Delighted
Pain Points
Noise
Compare
Drop-off
⚠️ Slow
Maze
Quiet
Opportunity
Target
Clarify
1-tap
💡 Automate
Self-help
Reward
1Aware
Touchpoint
Ad / Social
Emotion
😐 Neutral
Pain Point
Generic noise
Opportunity
Sharper targeting
2Consider
Touchpoint
Website
Emotion
🙂 Curious
Pain Point
Hard to compare
Opportunity
Clearer pricing
3Purchase
Touchpoint
Checkout
Emotion
😊 Hopeful
Pain Point
Cart drop-off
Opportunity
One-tap checkout
4Onboard — the dip
Touchpoint
Welcome Email
Emotion
😟 Frustrated
Pain Point
⚠️ Slow — manual welcome takes 48h
Opportunity
💡 Automate the welcome sequence
5Use
Touchpoint
App / Support
Emotion
🙂 Engaged
Pain Point
Help is a maze
Opportunity
Proactive in-app tips
6Advocate
Touchpoint
Referral
Emotion
😍 Delighted
Pain Point
No referral nudge
Opportunity
Reward program
The emotion dip at Onboarding reveals the critical opportunity zone
📋
Service Blueprinting
Operations-CX Bridge

Expands the journey map to include what happens backstage — connecting customer experience to the systems and people that enable it.

Customer Actions (Frontstage Visible)
LINE OF INTERACTION
Frontstage Employee Actions
LINE OF VISIBILITY
Backstage Processes
Support Systems & Tech
🖼️
CX Innovation Canvas
Strategy Alignment Tool

One-page strategic canvas that aligns segments, desired outcomes, touchpoints, enablers, and metrics into a coherent experience design.

Segment
Maya (Pro) David (Senior)
Outcomes
Confident · Fast · Trusted
Touchpoints
App · Branch · Phone · Email
Enablers
AI triage · Staff training
Metrics
NPS >70 · CES <2
Signature Moment
Instant onboarding in 3 min
♿
Inclusive Design
Microsoft / Kat Holmes

Design that recognises and removes barriers for excluded users — while creating better experiences for everyone. The curb-cut effect in CX form.

01 Recognise Exclusion — who is this designed against, unintentionally?
02 Learn from Diversity — edge-case users reveal invisible assumptions
03 Solve for One, Extend to Many — the curb-cut effect
Permanent Temporary Situational
👁️ Visual Blind Eye patch Sun on screen
🖐️ Motor One arm Broken wrist Holding baby
🧠 Cognitive Disability Concussion Distracted & late
Example: Designing for the customer with the highest barrier (low vision, motor impairment, cognitive load, low literacy) typically produces a better experience for every customer.
design feeds
↓
04
Phase Four
Prioritize & Plan

Not every idea can be built. Rigorous prioritization ensures teams invest effort where it creates the most customer value — and business impact.

📊
Kano Model
Experience Feature Classifier

Classifies CX features by their impact on satisfaction — helping teams identify what's table-stakes vs. what will genuinely delight.

⚠️ Basic
Must-have
Example: Site doesn't crash. Expected — absence causes rage.
📈 Perf.
More = Better
Example: Faster load times. Linear satisfaction improvement.
✨ Delight
Unexpected Joy 🎉
Example: Proactive issue fix before customer notices. Drives advocacy.
⚖️
Value-Effort Matrix
Prioritization Grid

Plots CX initiatives by customer value vs. implementation effort to sequence quick wins, strategic bets, and long-term investments.

↑ Customer Value
⚡ Quick Win
Low effort, high value. Do first.
🎯 Strategic Bet
High effort, high value. Plan carefully.
🗑️ Deprioritize
Low effort, low value.
⚠️ Thankless Task
High effort, low value. Avoid.
Effort → High
🔢
RICE Scoring
Quantified Prioritization

Turns subjective prioritization debates into an objective score — forcing teams to commit to estimates of reach, impact, confidence, and effort.

R
Reach
×
I
Impact
×
C
Confidence
÷
E
Effort
Onboarding Redesign
62.5
New Chatbot
18.0
Self-Service Portal
40.0
priorities drive
↓
05
Phase Five
Build, Test & Iterate

Agile, rapid-cycle experimentation. CX leaders don't perfect before launching — they test quickly, learn from real customers, and iterate toward excellence.

⚡
Design Sprint (5-Day)
Rapid Validation Method

Compress months of CX design work into 5 days — with real customer validation by Friday.

Day 1
Understand
Mon · Map problem & pick target
Day 2
Sketch
Tue · Individual solution sketches
Day 3
Decide
Wed · Vote & storyboard
Day 4
Prototype
Thu · Build realistic facade
Day 5
Test
Fri · 5 real customer interviews
🤝
Customer Co-Creation Labs
Participatory Design

Structured workshops where customers and employees co-design solutions together — eliminating assumption-based design in real time.

👥
Customers
+
💼
Employees
+
⚙️
Product Team
↓
🎯 Solutions designed with reality, not about it
🔁
Lean CX / MVP Approach
Experimentation Loop

Apply lean startup thinking to CX — build the minimum viable experience, expose it to real customers, measure response, and iterate fast.

🏗️
Build
Smallest viable version of the experience — one channel, one persona, one journey step.
→
📊
Measure
Behavioural data, not opinions. Completion rate, time-to-task, repeat usage.
→
💡
Learn
What did customers do that we didn’t predict? What hypothesis did we falsify?
↺
🔁
Iterate
Refine the hypothesis or pivot. Ship the next minimum increment within the week.
Smallest first. A working journey for one persona beats a polished journey for none.
Measure behaviour. What customers do reveals more than what they say in surveys.
Ship weekly. Long loops kill momentum. Tight cycles compound learning.
🗓️
Agile CX Roadmapping
Iterative Delivery Planning

Breaks the CX strategy into sprint-based releases with continuous feedback loops — avoiding big-bang transformation failures.

Sprint 1
✓ Onboarding flow MVP
Sprint 2
→ Self-service portal v1
Sprint 3
♻️ AI triage integration
📋
RACI Matrix
Responsibility Assignment · Cross-Functional Accountability

For every CX task or decision, name exactly who is Responsible (does the work), Accountable (owns the outcome — only one person), Consulted (provides input before decisions), and Informed (kept aware after decisions). Most CX initiatives fail not from bad strategy but from unclear ownership.

R
Responsible
Does the work. Multiple Rs allowed.
A
Accountable
Owns the outcome. Exactly one per row.
C
Consulted
Two-way: input before decision.
I
Informed
One-way: updated after decision.
CX Task / Decision CX Lead Product Owner Engineering Operations Executive
Define journey scopeACICI
Prioritise initiativesRRCCA
Build & ship featureCARII
Operate & measure outcomesCIIAI
Iterate on customer feedbackARRCI
⚠️ Two As is a red flag. Diffused accountability means no one truly owns the outcome.
👁 Too many Cs slow you down. If everyone is consulted, decisions stall. Be honest about who actually adds value.
✅ No A = governance gap. A row without an Accountable means that decision will quietly never happen.
delivery is shaped by
↓
3K
The Lean Layer
3K Innovation & Lean Thinking

While Design Sprints tell you how fast to move, the 3K framework tells you what kind of move to make. Borrowed from Japanese manufacturing and adapted for CX, the three Ks give teams a shared language for calibrating ambition — from daily micro-fixes to full reinvention. Paired with Lean CX principles, they form the operating rhythm for sustained experience excellence.

🟢
Kaizen · 改善
Continuous Improvement

Small, relentless, daily improvements owned by the frontline. Near-zero cost, near-zero risk, compounding returns. The operating rhythm that keeps CX moving every week.

CX Example: Baristas say each customer's name at handoff. +4 NPS in 14 days. Cost: zero.
Daily
cadence
$0
typical cost
Low
risk
🟡
Kaikaku · 改革
Radical Reform

Decisive, structural change. Tear down what can't be improved incrementally and rebuild it smarter. Higher risk, higher investment, but essential when Kaizen has reached its ceiling.

CX Example: Rebuild the entire POS system to integrate app orders with barista screens. Lost-order rate drops to 0.3%.
Quarterly
cadence
$$$
investment
Medium
risk
🔴
Kakushin · 革新
Disruptive Innovation

Invent what didn't exist before. Not better, not faster — fundamentally different. Requires a new mental model, not just new features. The category-redefining horizon.

CX Example: An ML "Your Usual" engine that pre-stages orders before you even decide. The brand acts on your behalf before you act.
18mo+
horizon
$$$$
investment
High
risk
🌀
The 3K Synthesis
Running All Three in Parallel
🟢 Kaizen keeps momentum — daily wins sustain belief
🟡 Kaikaku funds the vision — platform Kakushin needs
🔴 Kakushin earns loyalty — word-of-mouth no ad budget buys
🔧
5 Lean CX Principles
Womack & Jones, adapted

The thinking system behind the 3Ks. Five principles that apply across all three innovation types — from daily habits to disruptive reinvention.

1 · Specify value from the customer's viewpoint
2 · Map & eliminate Muda (waste: waiting, defects, motion, overprocessing)
3 · Create flow — remove interruptions between intent & fulfilment
4 · Establish pull — respond to signals, don't push schedules
5 · Pursue perfection — the loop never closes
現 場
Gemba Walk
Go & See for Yourself

Gemba (現場) means "the real place" — where value is actually created. No CX decision should be made from a conference room when you could make it standing where the work happens.

DESK ASSUMPTION: "Baristas prefer paper tickets."
→
GEMBA REALITY: "The screen is 2 metres from the bar. They physically can't read it while making drinks."
Every assumption from a conference room is a risk. Every Gemba walk is insurance.
5Y
5 Whys
Root Cause Analysis

Ask "Why?" five times to peel back from symptom to root cause. Most CX problems aren't app problems — they're organisational, systemic, or cultural problems hiding behind symptoms.

SYMPTOM: NPS dropped 14 points
Why? → Customers abandon app mid-order
Why? → New app has 14 screens for one order
Why? → Revenue team added upsell features
ROOT: No one owns end-to-end CX
♻️
PDCA Cycle
Plan · Do · Check · Act

The operational rhythm that gives the 3Ks their cadence. Kaizen runs PDCA in weeks. Kaikaku runs it over quarters. Kakushin runs it over years. Same cycle, different tempos.

P
PLAN
Write the hypothesis
D
DO
Smallest testable pilot
C
CHECK
Measure vs hypothesis
A
ACT
Standardise or pivot
📄
A3 Design Thinking
Toyota Lean ✕ Design Thinking

One-page visual problem-solving that fuses Toyota's A3 Lean format with Design Thinking's human-centred rigour. Forces clarity, empathy, and action onto a single sheet — making the invisible visible and the complex shareable.

1 Background
Why this matters — context, VoC, empathy
2 Current State
Journey map · data · pain points
3 Goal / Target
Specific + measurable CX outcome
4 Root Cause
5 Whys · Fishbone · JTBD insights
5 Countermeasures
Co-created solutions · owner · date
6 Effect Confirmation
NPS · CES · leading indicators
7 Follow-up Actions
PDCA next cycle · ownership · date
All on one A3-size page
A3 vs PDCA vs DMAIC
PDCA = fast iteration loop  |  DMAIC = rigorous statistical proof  |  A3 = one-page story that aligns all stakeholders
📊
DMAIC
Six Sigma · Data-Led Improvement

Define · Measure · Analyze · Improve · Control. Six Sigma's rigorous data-driven problem-solving cycle. Where PDCA is iterative and light, DMAIC is thorough and statistical — used when you need proof, not just improvement.

D
DEFINE
Problem & goal
M
MEASURE
Baseline data
A
ANALYZE
Root causes
I
IMPROVE
Pilot & test
C
CONTROL
Lock in gains
Example sequence: D: Define the customer outcome target (with baseline data). M: Establish current performance baseline. A: Identify the top contributing factors. I: Pilot in a controlled subset. C: Standardise winning practice and monitor leading indicators.
DMAIC vs PDCA: PDCA = fast, iterative, light. DMAIC = rigorous, statistical, used when decisions need evidence and sign-off.
delivery produces
↓
06
Phase Six
Measure & Grow

Great CX is never finished — it's continuously measured, optimized, and connected to business growth. Measurement closes the loop back to discovery.

🎯
CX Measurement System
NPS · CSAT · CES

A hierarchy of metrics — each measuring a different dimension of the customer relationship, from loyalty to effort to satisfaction.

72
NPS · Net Promoter Score
Measures loyalty & advocacy potential
4.6
CSAT · Customer Satisfaction
Measures satisfaction at a specific interaction
1.8
CES · Customer Effort Score
Low = effortless = better. Predicts churn.
📈
Leading & Lagging Indicators
Measurement Intelligence

Lagging indicators confirm what already happened. Leading indicators predict what’s about to happen. Most CX dashboards are 95% lagging — measuring crises after they’ve occurred.

📈 Leading
● 4-wk repeat visit rate
● App session completion
● Loyalty activation rate
● Support ticket topic trends
📉 Lagging
● NPS / CSAT / CES
● Churn rate
● Revenue per customer
● Lifetime value
💡 The pattern: The signals predicting most CX crises are usually in the data weeks or months before anyone notices — but only if someone is tracking leading indicators (completion rate, repeat-visit cadence, support topic trends) rather than just lagging scores.
📈
Experience-Led Growth
Business Outcome Framework

Links every CX innovation directly to a business outcome — making the case for CX investment visible to the C-suite.

💡
Better Experience Design
↓
❤️
Higher Loyalty & Retention
↓
💰
Increased Share of Wallet
↓
📣
Word-of-Mouth Advocacy
↓
🚀
Lifetime Value Growth
How They All Connect

Each framework feeds the next. The output of one phase is the input of the next — forming a continuous loop.

PROBLEM SPACE
SOLUTION SPACE
DISCOVER Ph 1 & 1½
DEFINE Phase 2
DESIGN
BRIEF
DEVELOP Ph 3 & 4
DELIVER Ph 5 & 6
Raw human insights, root causes & unmet need signals
→
Provocative truths & design directions
→
Clear vision, VPC fit & customer archetypes
→
Inclusive, orchestrated experience with blueprint
→
Sequenced backlog with clear business case
→ →
The Lean Layer
3K Innovation
Right-sized change at the right tempo
→
Leading & lagging signals restart discovery
The Continuous Loop
Measure → Discover → Repeat

CX measurement data is not the end — it's new VoC signal that flows back into the Discover phase, revealing new unmet needs, new priorities, and new design opportunities. The best CX organizations run this loop continuously.