Customer experience is not limited to customer service, a digital interface, or an individual interaction. It is the experience customers build across the moments before, during, and after choosing a product or service.
A customer may discover a brand through one channel, evaluate it through another, make a purchase, encounter the product or service, ask for help, and decide whether to return. Every interaction shapes the journey, but the connections between those interactions often matter just as much as the interactions themselves.
My approach begins with the customer's goal. I look at what they are trying to accomplish, what they expect at each stage, where effort or uncertainty appears, and which moments reinforce or undermine the overall experience.
The goal is not to make every touchpoint look better in isolation. It is to improve the journey as a connected experience.
Define the journey
Fill in only what you know. Anything left empty stays “Unknown”.
The Customer Journey Map
Select a stage to open its working panel. Rename, add, remove or move stages to match the real journey.
Discover
How the customer first recognizes a need, problem, or relevant solution.
ACustomer goal
BCustomer actions
CTouchpoints
Where does the interaction occur?
DCustomer expectations
EActual experience
FEffort and emotion
GFriction and breakpoints
Ticked items appear on the Friction-to-Opportunity Board.
HEvidence and confidence
IImprovement opportunity
The Experience Curve
Drawn only from the ratings you enter in each stage.
No ratings yet. Open a stage and rate effort or sentiment — or mark it unknown. Nothing is drawn until you do.
Moments That Matter
Moments that disproportionately influence confidence, satisfaction, perceived value, or the willingness to continue. An intense moment is not automatically one that matters — say what makes it important and what supports that.
No moments added yet.
The Friction-to-Opportunity Board
No friction points yet. Tick friction in a stage panel above, or add one here.
Principles behind my approach
1. Start with the customer’s goal, not the organization’s structure.
Customers experience a journey, not an organization chart. Design around what they are trying to accomplish.
2. Experience is cumulative.
Individual interactions matter, but so do the gaps, transitions, and handoffs between them.
3. Effort is an important signal.
Unnecessary work, uncertainty, repetition, and waiting can undermine an otherwise good experience. Do not remove steps blindly; understand which steps provide necessary reassurance, control, or value.
4. Expectations shape experience.
A gap between what a customer expects and what actually happens can be as important as the quality of the interaction itself.
5. Moments matter in context.
Certain moments can influence trust, perceived value, confidence, or the decision to continue. Identify them from the actual journey rather than assuming they are the same for every customer.
6. Fix causes, not only symptoms.
A support complaint may originate in unclear communication, product design, operating procedures, training, or a broken handoff. Diagnose the cause before prescribing a fix.
7. Improve the connected system.
A change that helps one touchpoint may create friction elsewhere. Consider the impact on the whole journey.
8. Use evidence to guide priorities.
Customer feedback, observation, behaviour, and operational data help distinguish proven problems from internal assumptions.
Illustrative example — not a real client caseThe First-Use Experience
A customer purchases a digital subscription expecting to get started quickly.
- Discover
The customer sees a clear promise about ease of use.
- Evaluate
The customer compares plans and checks whether the service fits their needs.
- Commit
The customer subscribes.
- Onboard
Several verification steps appear, but the next action is unclear.
- First use
The customer is unsure whether setup is complete and cannot find the feature needed to obtain initial value.
- Get help
The customer contacts support to understand what to do next.
The issue
The problem is not necessarily that the product has too many features. The immediate issue may be a gap between the promise of easy onboarding and the uncertainty in the actual first-use experience.
Improvement hypothesis
Clarify the remaining setup steps, show the customer when onboarding is complete, and make the next recommended action clear.
What needs validation?
- Where exactly do users abandon or delay the setup?
- What questions do they ask support?
- How many steps are required, and which are genuinely necessary?
- Can users complete setup more successfully after the changes?
The Customer Experience Brief
Built only from your answers. Select an item to edit it where it lives.
- 01Brand, product, or service
Not answered yet
- 02Customer segment or persona
Not answered yet
- 03Customer goal
Not answered yet
- 04Business goal
Not answered yet
- 05Journey starting point and desired outcome
Not answered yet
- 06Journey stages and key actions
1. Discover 2. Explore and Evaluate 3. Decide and Commit 4. Onboard and Start 5. Use and Experience Value 6. Get Help and Resolve 7. Continue, Return, or Leave
- 07Touchpoints
Not answered yet
- 08Expectations and actual experiences
Not answered yet
- 09Effort and sentiment ratings
Not answered yet
- 10Friction points and breakpoints
Not answered yet
- 11Moments that matter
Not answered yet
- 12Supporting evidence and assumptions
Not answered yet
- 13Improvement opportunities
Not answered yet
- 14
- 15
About this framework
- What it helps solve
- Experience fixes chosen by opinion rather than by the moments customers actually remember.
- Who it's for
- Customer experience, service and marketing teams.
- Main components
- Journey stages, friction points, important moments, and improvement opportunities.
- What you leave with
- A journey map and a prioritised improvement report.
- Limits
- Best paired with real customer feedback; the map is only as good as its inputs.
See how this thinking was applied in real work · Read related Field Notes