Purpose: Customer Journey Mapping is a visual tool that helps teams understand how users experience a product or service across touchpoints over time.
Design Thinking Phase: Empathise
Time: 45â60 min session + 1â2 hours analysis
Difficulty: ââ
When to use:When aligning cross-functional teams on user pain points early in discoveryWhen optimising existing flows based on research insightsWhen designing new services with multiple touchpoints or channels
What it is
Customer Journey Mapping (also known as Experience Mapping) is a UX methodology that visualises the entire path a user takes when interacting with a product or service. It includes actions, thoughts, emotions, channels, and pain points at every step â enabling teams to design more coherent and meaningful experiences.
đş Video by NNgroup. Embedded for educational reference.
Why it matters
Designers often see moments in a flow â but users live through entire journeys. Without mapping those journeys, it's easy to miss key frustrations, drop-offs, or unmet needs that occur across silos or time. Journey maps help teams break out of internal structures and see the product through the userâs lens. When done well, they drive alignment, prioritise features more meaningfully, and enable consistent end-to-end experiences.
When to use
- When you have foundational research but want to synthesise insights at a service level
- When multiple teams touch different parts of the user experience and need to align
- When preparing for a Service Blueprint or UX redesign
Benefits
- Rich Insights: Helps uncover user needs that arenât visible in metrics.
- Flexibility: Works across various project types and timelines.
- User Empathy: Deepens understanding of behaviours and motivations.
How to use it
- Define the scope: Choose a specific persona and goal (e.g. âBooking a consult as a first-time home buyerâ).
- Map journey stages: Identify broad steps in the path (e.g. awareness, consideration, action).
- Add user actions, emotions, and touchpoints: Use research to fill in real behaviours and perceptions.
- Highlight pain points and drop-offs: Mark where users feel confusion, frustration, or blockers.
- Discuss with your team: Align on opportunities, moments of delight, and service gaps.
- Export, share, and link to strategic artefacts like blueprints or roadmaps.
Example Output
A simplified customer journey map for a fictional fintech product:
Stage | Action | Emotion | Touchpoint | Pain Point |
---|---|---|---|---|
Discovery | Searches for budgeting tools | Curious, cautious | Google, app store | Confused by inconsistent reviews |
Onboarding | Downloads and sets up profile | Hopeful, slightly overwhelmed | App interface | Too many options upfront |
Usage | Adds first few expenses | Energised | Mobile, email | Delayed sync with bank account |
Retention | Checks weekly emails | Informed, motivated | Push notifications, email | Lacks personalisation |
Common Pitfalls
- Skimming research: A map is only as good as the data behind it. Ground your work in real user quotes and observed behaviour.
- Too generic: Avoid mapping with âaverageâ users. Focus on one persona or situation per map to make it actionable.
- Not shared: Journey maps stuck in private decks wonât drive impact. Schedule a readout session and link maps to roadmap decisions.
10 Design-Ready AI Prompts for Customer Journey Mapping â UX/UI Edition
How These Prompts Work (C.S.I.R. Framework)
Each of the templates below follows the C.S.I.R. method â a proven structure for writing clear, effective prompts that get better results from ChatGPT, Claude, Copilot, or any other LLM.
C.S.I.R. stands for:
- Context: Who you are and the UX situation you're working in
- Specific Info: Key design inputs, tasks, or constraints the AI should consider
- Intent: What you want the AI to help you achieve
- Response Format: The structure or format you want the AI to return (e.g. checklist, table, journey map)
Level up your career with smarter AI prompts.Get templates used by UX leaders â no guesswork, just results.Design faster, research smarter, and ship with confidence.First oneâs free. Unlock all 10 by becoming a member.
Prompt Template 1: âMap a User Journey for a First-Time Feature Experienceâ
Map a User Journey for a First-Time Feature Experience
Context: You are a UX designer exploring how new users interact with a recently launched feature in a productivity app.
Specific Info: The feature includes a multi-step setup, optional integrations, and shows varying completion rates across use cases.
Intent: Identify key friction points and emotional touchpoints to inform design improvements.
Response Format: Structure the output as a table with columns: Step, Action, Thought, Emotion, Barrier, Suggestion.
If any flow step or use context is unclear, ask clarifying questions.
Then, suggest one idea to validate assumptions with real users.
Prompt Template 2: âTurn Interview Notes into Journey Stagesâ
Turn Interview Notes into Journey Stages
Context: You are a UX researcher synthesising user interviews for a B2B onboarding experience.
Specific Info: You have notes from 8 calls, with timestamps and emotional cues, but no pre-set framework.
Intent: Convert qualitative notes into a structured customer journey with key phases marked.
Response Format: Summarise interview observations into journey stages with headings, quotes, and inferred pain points.
Ask for a sample transcript segment if you'd like more context before mapping.
Then, suggest a way to visualise this for cross-team alignment.
Prompt Template 3: âGenerate Pain Point Hypotheses Across the Journeyâ
Generate Pain Point Hypotheses Across the Journey
Context: You are a senior designer preparing to audit the sign-up to trial conversion experience in a SaaS product.
Specific Info: Behavioural analytics show a major drop-off after the pricing page; no qualitative insight yet.
Intent: Forecast likely user pain points across the journey, to prioritise further research.
Response Format: Propose 3â5 distinct hypotheses with associated journey stages and suggested validation methods.
If the business goal or audience segment is unclear, ask that first.
Then, suggest which team member should be involved next.
Prompt Template 4: âIdentify Journey Moments with Emotional Impactâ
Identify Journey Moments with Emotional Impact
Context: You are designing for a wellness platform where motivation and habit formation are key to retention.
Specific Info: Usage data shows most churn happens between days 3â7.
Intent: Spot emotionally significant moments in the early journey where design can reinforce positive behaviour.
Response Format: Table with columns for Event, Likely Emotion, Design Opportunity, and Risk.
Ask clarifying questions if emotional intent isnât clear.
Then, recommend a motivational trigger to test.
Prompt Template 5: âWorkshop Prep: Frame Journey Questions for a Cross-Functional Sprintâ
Workshop Prep: Frame Journey Questions for a Cross-Functional Sprint
Context: You are running a sprint involving PMs, designers, CS, and marketing.
Specific Info: The team is focused on reducing NPS complaints about the onboarding experience.
Intent: Prepare 5 thoughtful open-ended questions to explore customer journey gaps.
Response Format: List the questions, each with a note on how it reveals opportunity.
Ask for context if the NPS themes or user quotes are vague.
Then, suggest one question to ask leadership before kickoff.
Prompt Template 6: âCreate Journey-Based Personas from Support Ticketsâ
Create Journey-Based Personas from Support Tickets
Context: You are analysing customer support data looking for patterns to inform new personas.
Specific Info: You've clustered 300+ support tickets by themes (e.g. account access, billing).
Intent: Build personas grounded in real journey issues, not just demographics.
Response Format: For each persona, include their pain points, goals, tool usage, and emotional tone.
Let me know if youâd like a ticket sample to test.
Then, suggest one way to validate these personas with product teams.
Prompt Template 7: âTranslate Journey Insights into Feature Ideasâ
Translate Journey Insights into Feature Ideas
Context: You are reviewing a journey map for an e-commerce returns process.
Specific Info: The map shows high anxiety post-return, with uncertainty around refund timelines.
Intent: Ideate ways to improve this journey stage with helpful features or comms.
Response Format: List 3â5 feature ideas with purpose, impact, and blockers.
Ask clarifying questions if the journey map lacks key events.
Then, propose a low-risk experiment to test one idea.
Prompt Template 8: âSummarise Cross-Channel Fragmentation in a Journeyâ
Summarise Cross-Channel Fragmentation in a Journey
Context: Youâre working on an omni-channel service for a healthcare provider.
Specific Info: Patients move between a mobile app, web login, and phone support.
Intent: Highlight where users experience disruption when switching channels.
Response Format: Table with Journey Step, Channel, Friction, and Suggested Unification Ideas.
Ask for a touchpoint list if channels are unclear.
Then, propose one next step to align engineering and CX.
Prompt Template 9: âEnrich Journey Maps with User Quotesâ
Enrich Journey Maps with User Quotes
Context: You are finalising a journey map from usability test sessions.
Specific Info: You have transcripts tagged by task and timestamp, but the map lacks empathy elements.
Intent: Pull compelling user quotes that clarify emotional experience per journey stage.
Response Format: Return quotes grouped by stage, with emotion tags and quote attribution.
Ask for quote length preferences or sentiment focus if needed.
Then, suggest a visual cue to present these quotes effectively on the map.
Prompt Template 10: âAudit Journey Maps for Bias or Assumptionsâ
Audit Journey Maps for Bias or Assumptions
Context: You joined mid-project and received a high-level journey map from another vendor team.
Specific Info: The map lacks data sources and shows overly happy-path flows.
Intent: Spot where assumptions may be hiding and reduce bias in interpretation.
Response Format: Annotate the map stages with potential assumptions or gaps, plus data types to validate.
Ask for project goals if context is missing.
Then, suggest how to reframe one journey stage to increase inclusivity.
Recommended Tools
- UXPressia â Visual journey mapping and persona builder
- Miro â Real-time collaboration for mapping workshops
- Dovetail â Repository for tagging interviews and linking quotes to maps
- Lucidchart â Diagrams with stakeholder-friendly outputs
- JourneyMap.ai â AI-powered journey visualisation and synthesis

Learn More

