Journey Map Examples: 6 User & Customer Journey Maps (2026)
Real journey map examples — user, customer, and UX journeys for SaaS onboarding, e-commerce, mobile apps, healthcare, fintech, and support resolution.
Journey Map Examples: 6 Real User & Customer Journey Maps
A journey map is a visual story of how one user moves through every phase of an experience — what they do, what they think, what they feel, and where they get stuck. This guide walks through six concrete journey map examples across the most common contexts UX teams work in: SaaS onboarding, e-commerce purchase, mobile app first-week, customer support resolution, healthcare patient flow, and fintech account opening.
Each example uses the same six-column format so you can copy the structure and swap in your own research data.
What's in a Journey Map Example
Every good journey map example contains the same building blocks, repeated across phases:
| Column | What it captures | Example |
|---|---|---|
| Phase | Where the user is in their experience | "Awareness," "Onboarding" |
| Touchpoints | Where they interact with you | Marketing site, signup form, support chat |
| Actions | What they actually do | "Searches Google for 'card sort tool'" |
| Thoughts | What runs through their head | "Will this be free or some trial trap?" |
| Emotions | How they feel (high → low) | 😊 → 😐 → 😣 → 😊 |
| Pain points / opportunities | Where they hit friction; where you can help | Confusing pricing page; clearer free-tier copy |
The phases vary by context — a B2B SaaS journey looks different from an emergency-room patient journey. But the columns stay the same.
Example 1: B2B SaaS Onboarding — UX Researcher Tries a Card Sorting Tool
Persona: Maya, senior UX researcher at a 50-person SaaS company. Tasked with restructuring product navigation. Has used Optimal Workshop before but the team's budget was cut.
Scenario: Maya needs to run a card sort study in the next two weeks. Searching for a free or cheap tool.
| Phase | Touchpoints | Actions | Thoughts | Emotion | Pain points → opportunities |
|---|---|---|---|---|---|
| Awareness | Google search, Reddit r/userexperience | Searches "free card sorting tool" → finds 4 results | "Probably another fake-free trial" | 😐 Cautious | SERP filled with paid tools → cleaner "free forever" signaling |
| Consideration | Comparison page, landing page | Reads "Free Card Sort vs OptimalSort" comparison; opens product features page | "Unlimited responses on free? Need to verify this." | 😊 Curious | Skeptical of "unlimited" claims → show stats: "X studies created, Y responses collected" |
| Decision | Signup page | Signs up with Google SSO; lands in dashboard | "Hope I don't have to enter a credit card later" | 😊 Optimistic | First-time experience needs to confirm free-tier scope explicitly |
| Onboarding | Empty dashboard, "Create study" wizard | Creates first study; uploads 35 cards | "Why does it default to open sort? What's hybrid?" | 😣 Confused | Sort-type picker lacks decision help → tooltip with "Use open when you don't have categories yet" |
| First use | Study link, participant view | Sends link to 8 colleagues; refreshes results page | "When will responses start showing up?" | 😟 Anxious | Empty-state results page → show "Waiting for responses" with estimated time |
| Retention | Results dashboard, email | Returns 3 days later; sees similarity matrix | "Wait, this is gated to Starter $19?" | 😞 Frustrated | Surprise paywall on a key feature → preview the locked view, explain what unlocking gets |
| Advocacy | Slack, conference talk | Recommends to colleague; mentions in team retrospective | "Worth the $19 — way cheaper than OptimalSort" | 😊 Happy | Encourage referral with double-credit incentive |
Biggest opportunity: the "Onboarding → First use" transition. Two emotional dips back-to-back (confusion + anxiety) before any value delivery. A 60-second guided tour during study setup + an empty-state with social proof during the wait would smooth both.
Example 2: E-Commerce Purchase — Mobile Shoe Shopper
Persona: Jordan, marketing manager in Brooklyn. Wants new running shoes before a half-marathon in 5 weeks. Shops on phone during commute.
Scenario: Jordan needs to find, try, and own a pair of running shoes — all from a phone.
| Phase | Touchpoints | Actions | Thoughts | Emotion | Pain points → opportunities |
|---|---|---|---|---|---|
| Awareness | Instagram ad, friend's recommendation | Saves Instagram post; asks friend "which shoe?" | "These look good but the brand seems new" | 😊 Curious | Use UGC + athlete endorsements to reduce uncertainty |
| Research | Brand site, Reddit reviews, YouTube | Reads 3 reviews; watches a fit video | "Sizing runs small per Reddit. What about wide feet?" | 😟 Worried | Add "fit feedback from real buyers" widget on PDP |
| Decision | Product page, size guide | Adds to cart in size 10.5 wide | "What's the return policy if these don't fit?" | 😐 Hesitant | Surface 365-day free return policy at cart confirmation |
| Purchase | Checkout, Apple Pay | Uses Apple Pay; selects 2-day shipping | "Free shipping over $75 — I just barely qualified" | 😊 Relieved | Show free-shipping progress bar in cart |
| Delivery | Email tracking, doorbell camera | Tracks package; gets delivery notification | "Two days exactly — solid" | 😊 Pleased | Optional SMS delivery alerts |
| First wear | Shoebox, running app | Unboxes; runs 5 miles | "Surprisingly comfortable. Sizing was right." | 😊 Satisfied | Auto-prompt for review after 1 week |
| Advocacy | Instagram story, friend chat | Posts photo; recommends to 2 friends | "I'm telling everyone about this brand" | 😊 Loyal | Referral program — both parties get $15 |
Biggest opportunity: the "Research → Decision" transition. Sizing uncertainty is the conversion-killer for first-time buyers of any new shoe brand. A fit-feedback widget pulling quotes from real reviews ("runs small per Jordan, M, wide feet") + a try-on-at-home program would crush this objection.
Example 3: Mobile App First-Week — Fitness Tracker
Persona: Sam, 34, returning to fitness after a knee injury. Wants to track running progress without a Strava commitment.
Scenario: Sam downloads a new fitness app and needs to decide within 7 days whether it's worth keeping.
| Phase | Touchpoints | Actions | Thoughts | Emotion | Pain points → opportunities |
|---|---|---|---|---|---|
| Discovery | App Store search, podcast ad | Searches "running tracker"; reads top reviews | "Why is everything subscription now?" | 😐 Resigned | Lead with one-line value-vs-Strava positioning |
| Install | App Store install, app open | Installs; opens app | "Hope this isn't another bloated experience" | 😐 Cautious | Skip splash screen; jump straight to value |
| First open | Onboarding flow | Completes 6-screen onboarding | "Way too many screens before I can see anything" | 😞 Annoyed | Trim to 3 screens max — name, goal, first run |
| First run | Run tracking screen | Records a 3-mile run | "Map looks accurate. Good." | 😊 Pleased | Show a personal-best callout if applicable |
| Day 3 | Notification, recap email | Returns after a rest day | "Decent dashboard. Where's the social part?" | 😐 Neutral | Add an optional "share with a friend" CTA after second run |
| Day 7 (decision moment) | Trial-ending modal, paywall | Sees "7-day trial ending tomorrow" | "Has this been worth $9.99/mo for two more runs?" | 😞 Doubtful | Pre-empt with "your week in numbers" summary email day 6 |
| Retention | App home, weekly recap | Subscribes annual; uses weekly | "Glad I kept it — the recap emails sealed it" | 😊 Committed | Identify the moment of conversion → double down |
Biggest opportunity: the day-6 → day-7 transition. The trial-ending decision is binary and emotionally driven. A "your week in numbers" recap email arriving the day before the paywall hits, with a personal-best stat or progress visual, would dramatically shift the decision context.
Example 4: Customer Support Resolution — Frustrated SaaS Subscriber
Persona: Priya, finance ops manager. Software subscription billing failed during a busy week.
Scenario: Priya needs to resolve a billing issue without it blocking her team's tooling access.
| Phase | Touchpoints | Actions | Thoughts | Emotion | Pain points → opportunities |
|---|---|---|---|---|---|
| Problem | Failed-payment email, Slack DM from teammate | Gets "your subscription is paused" email | "Why didn't they warn me before pausing?" | 😡 Angry | Send proactive 3-day-warning email before pausing |
| Search for help | Help center, status page | Searches "billing failed"; finds outdated article | "Article says 2024 — is this still right?" | 😡 Frustrated | Surface "last updated" date on every article; flag stale content |
| Contact | Support chat, contact form | Opens chat; sees "we'll respond in 4 hours" | "Four hours? I need this today" | 😞 Despairing | Show queue position + estimated response time live |
| First response | Email reply, chat reply | Gets reply 3 hours later asking for billing details | "Why are they asking — they have my account" | 😞 Annoyed | Pre-fill account context in first reply |
| Resolution | Updated card flow, restored access | Updates card; access restored 10 min later | "Faster than expected once they replied" | 😊 Relieved | Send a "we're sorry" credit automatically |
| Follow-up | Survey email | Gets CSAT survey 2 days later | "5/10. The fix was fine, the wait wasn't" | 😐 Neutral | Cohort the response — investigate the wait |
| Future state | All channels | Future billing issue → notified before paused | "They learned. Better." | 😊 Calmed | Memorialize fixes; publish a public changelog |
Biggest opportunity: the gap between "Problem" and "First response." A frustrated customer's emotion drops by 3 levels in this window. Proactive warnings before pause, live queue position during the wait, and pre-filled context in the first reply could collapse that whole emotional dip.
Example 5: Healthcare — First Appointment with a New Specialist
Persona: Carlos, 58, referred to a cardiologist for routine evaluation. Lives in Atlanta.
Scenario: Carlos needs to book, attend, and follow up on his first specialist appointment.
| Phase | Touchpoints | Actions | Thoughts | Emotion | Pain points → opportunities |
|---|---|---|---|---|---|
| Referral | PCP letter, phone | PCP refers; gives a paper note | "Why a paper note in 2026?" | 😐 Confused | Digital referral handoff into a portal |
| Scheduling | Phone, scheduler portal | Calls; waits 14 minutes on hold | "Why isn't there an online slot picker?" | 😞 Impatient | Self-serve online scheduling |
| Pre-visit | Paper forms, parking instructions | Fills 6 forms in waiting room | "Most of this is in their other system already" | 😞 Tired | Send forms 48 hours before; pre-populate from referral data |
| Arrival | Front desk, waiting room | Checks in; waits 35 minutes | "I came early for what" | 😞 Frustrated | Notify when running 15+ min behind |
| Visit | Exam room, specialist | 15-minute consultation | "Doctor was helpful but rushed" | 😐 Neutral | Block longer slots for first-time visits |
| Post-visit | Patient portal, lab follow-up | Logs in; tries to find results | "Portal has 6 menus. Where are my results?" | 😞 Lost | Top-line "Latest results" card on dashboard |
| Follow-up | Email, phone | Gets results call 5 days later | "Should have been a portal message + call" | 😐 Mixed | Multi-channel follow-up with channel preference |
Biggest opportunity: the pre-visit phase. Filling forms in the waiting room is the worst-experience moment in 80% of healthcare journey maps. Pre-populating from referral data and sending forms 48 hours early would also reduce front-desk workload by ~30%.
Example 6: Fintech — Opening a New Business Bank Account
Persona: Lina, founder of a 3-person startup. Just incorporated and needs business banking.
Scenario: Lina needs to open an account, make her first deposit, and connect payroll within 2 weeks.
| Phase | Touchpoints | Actions | Thoughts | Emotion | Pain points → opportunities |
|---|---|---|---|---|---|
| Awareness | Founder Slack, Twitter | Sees "Brex vs Mercury" thread | "Both look fine. Which is faster to open?" | 😐 Comparing | Lead with time-to-open as a marketing claim |
| Application | Application form | Fills 15-minute application | "Why so many EIN-related questions?" | 😐 Cautious | Inline help text for tax-form questions |
| Verification | Email, ID upload | Uploads docs; waits for approval | "Will this take 1 day or 10?" | 😟 Anxious | Show specific ETA, not "1-5 business days" |
| Approval | Welcome email | Gets approved in 4 hours | "Faster than expected. Great." | 😊 Delighted | Lead with that ETA in marketing |
| First login | Web app | Logs in; lands on empty dashboard | "Where do I send wire instructions to my client?" | 😐 Looking | Surface "send wire" + "request transfer" on day-1 dashboard |
| First deposit | ACH transfer setup | Sets up ACH from old bank | "Plaid worked. Money moves in 3 days." | 😊 Satisfied | Express transfer for first deposit |
| Payroll integration | Gusto connect | Connects payroll | "Took 5 minutes. Clean." | 😊 Confident | Highlight payroll integrations on signup |
Biggest opportunity: the verification → approval window. Anxiety peaks when the user doesn't know if it'll be hours or weeks. Showing a specific ETA based on application completeness (and meeting it) creates a "delighted" emotion spike that's the seed of advocacy.
How to Build Your Own Journey Map
- Pick one persona — not "all users." Specificity is what makes the map useful.
- Pick one scenario — "first-week onboarding," not "the whole product." A focused map produces actionable findings; a comprehensive one produces a poster.
- Walk the phases in chronological order — awareness → consideration → decision → onboarding → use → retention → advocacy is a common skeleton. Adapt to your context.
- Fill each phase column-by-column — touchpoints, actions, thoughts, emotions, pain points, opportunities. Six columns × six phases = a 36-cell grid.
- Validate before sharing — 5-8 user interviews. Maps based on team assumptions are 73% less accurate than research-driven maps. The whole point of the artifact is to align people on what's real.
Validate the Map with Real Research
Journey maps surface hypotheses about where users get stuck. Validation requires evidence. The fastest research methods to confirm a journey-map opportunity:
- Card sorting — for confusion around navigation, labels, or category mental models
- Tree testing — for findability of a specific touchpoint
- First-click testing — for whether your design actually surfaces the intended next step
- Surveys — to quantify pain-point severity across a wider sample
All four methods run in the same workspace — pick whichever validates the specific hypothesis your map exposed.
Run a study free, no credit card →
Further Reading
- User Journey Map: Definition & Components
- User Journey (UX Glossary)
- User Persona (UX Glossary)
- Jobs to Be Done (JTBD) Framework
- Mental Model (UX Glossary)
- Heuristic Evaluation: Nielsen Method
Frequently Asked Questions
What is a journey map example? A journey map example is a worked-out visualization showing one user persona moving through every phase of an experience — discovery, consideration, purchase, onboarding, ongoing use, and advocacy — with each phase broken down by what the user is doing, thinking, feeling, where they get stuck (pain points), and where the team can intervene (opportunities). The best examples include 4-7 phases, 8-15 touchpoints per phase, and an emotion curve showing highs and lows. The six worked examples above cover SaaS onboarding, e-commerce, mobile app, customer support, healthcare, and fintech.
What's the difference between a user journey map and a customer journey map? A user journey map documents the complete experience of someone interacting with a product, including non-paying users (free tier, trial, prospect researching). A customer journey map focuses specifically on the commercial relationship from prospect → buyer → renewing customer, weighted toward purchase decisions and lifetime-value moments. The two overlap heavily — most teams build one combined map and label the post-purchase phases as the customer-relationship portion.
How do I make a journey map? Build a journey map in five steps. (1) Pick one persona — don't try to map every user at once. (2) Pick one scenario — "first-time onboarding" or "renewal decision," not the whole product. (3) List the phases the user moves through in chronological order. (4) For each phase, document touchpoints (where the user interacts with your product), actions (what they do), thoughts, emotions, pain points, and opportunities. (5) Validate with 5-8 user interviews before sharing — assumption-based maps are 73% less accurate than research-driven ones.
How many phases should a journey map have? Most effective journey maps have 4-7 phases. Fewer than 4 misses critical transition moments. More than 7 makes the map hard to read at a glance and dilutes the strategic signal. Common phase frameworks: awareness → consideration → decision → onboarding → ongoing use → renewal/advocacy (6 phases) or pre-purchase → purchase → post-purchase (3 phases collapsed for simpler cases).
What tools do I need to make a journey map? You can build a journey map in any tool that lets you draw a table: Figma, FigJam, Miro, Mural, Whimsical, or even a Google Sheet. The tool matters less than the research feeding it. Pair the visual map with real user research — interviews, surveys, card sorts, and tree tests — to validate that the phases, touchpoints, and pain points reflect actual user experience rather than internal assumptions.