Customer Journey Map
Trace every step a customer takes, from first discovering a need to using the product afterwards.
12 min · Service design practice, widely adopted in product and venture development
What is this framework?
A customer journey map lays out the stages a customer moves through — discovering, considering, buying, using and following up — and records their actions, touchpoints, thoughts, emotions and pain points at each stage. It exposes exactly where the experience breaks down or delights, stage by stage.
Founders often focus intensely on the moment of purchase and neglect everything before and after it. A customer journey map corrects this by walking through the full experience end to end, from the moment a need first arises through to what happens after the purchase is complete.
For each stage, the map records what the customer does, where they interact with the venture (the touchpoint), what they are thinking, how they feel emotionally, what frustrates them, and what opportunity exists to improve that step. Mapping emotion alongside action is what distinguishes this tool from a simple process flowchart: a step can be functionally fine but emotionally frustrating, and that combination is exactly where competitors can win customers away.
The map is most useful when built from real customer observation or interviews rather than assumption, and when it is revisited as the product and market evolve.
What problem does it help solve?
- Reveals moments of friction or delight you would otherwise miss
- Aligns product, marketing and operations around the same view of the customer experience
- Highlights where a small fix could remove a major point of frustration
- Helps prioritise improvements by showing which stage most affects the overall experience
The framework
Read left to right to follow the customer from discovery through to after purchase.
Every part explained
Stage
The broad phase of the journey the customer is in.
Ask: Where is the customer in their overall journey?
Example: Discovering that a food delivery option exists near campus.
Action
What the customer physically does at this stage.
Ask: What does the customer actually do here?
Example: Searches app store for food delivery apps.
Touchpoint
The specific point of contact between the customer and the venture.
Ask: Where does this interaction happen?
Example: App store listing and reviews.
Thought
What is going through the customer's mind at this stage.
Ask: What are they thinking right now?
Example: "Is this actually available near my campus?"
Emotion
The customer's emotional state during this stage.
Ask: How do they feel at this moment?
Example: Cautiously curious, slightly sceptical.
Pain
Friction or frustration experienced at this stage.
Ask: What is frustrating or slowing them down here?
Example: Unclear whether the app covers their specific faculty building.
Opportunity
A concrete improvement that could remove the pain or deepen the delight.
Ask: What could be improved at this exact step?
Example: Show a coverage map on the app store listing itself.
Worked example — CampusEats
The team mapped a typical student's full journey with the app, from first hearing about it to eating their food.
Discover
Hears about CampusEats from a friend's social media post; feels intrigued but unsure if it covers her faculty.
Browse
Opens the app, scrolls stalls; frustrated that menu photos are missing for some vendors.
Order
Selects a meal and customises it; relieved the process is quick, only three taps.
Pay
Pays via e-wallet; briefly anxious the payment might fail with poor campus wifi.
Collect
Walks to the pickup point; annoyed when the order is not ready exactly on time.
After purchase
Eats the meal between classes; feels satisfied but forgets to leave a review afterwards.
Key opportunity
Add live order-status updates to reduce anxiety during payment and collection.
Mapping the full journey revealed that the biggest source of dissatisfaction was not the food itself but uncertainty during the wait, which led the team to prioritise real-time order tracking.
How to use it
- 1Define the persona whose journey you are mapping.
- 2List the major stages of their experience, from first need to after purchase.
- 3For each stage, note the customer's action and the specific touchpoint involved.
- 4Record their likely thoughts and emotions at each stage, based on real observation where possible.
- 5Identify the pain point at each stage and a concrete opportunity to address it.
- 6Look across the whole map for the single stage causing the most friction and prioritise fixing it.
Try it yourself
Map out the journey stages for your own customer, from discovery to after purchase.
Discover
Purchase & after
Your work stays on this device. Nothing is uploaded, so use the same browser to come back to it.
When to use it
- When redesigning or auditing an existing customer experience
- Before launch, to anticipate friction points across the full journey
- When customer complaints cluster around a vague area and need pinpointing
When not to rely on it
This framework does not prove:
- • It reflects one persona's journey at a time and may not generalise to all customer segments.
- • It can become guesswork if not grounded in real observation or interviews.
- • It captures a snapshot; journeys shift as products, competitors and expectations change.
Common mistakes
- Mapping the journey from the company's perspective instead of the customer's
- Skipping the emotional and thought columns and only recording actions
- Focusing only on the purchase stage and ignoring discovery and after-purchase stages
- Never acting on the pain points identified, so the map becomes a one-off exercise
Connections
Related concepts
Related frameworks
Quick check
Why does a customer journey map include emotion alongside action at each stage?
Remember this
The customer experience is more than the moment of purchase — map the full journey to find where friction quietly costs you customers.