User Journey Map Example: A Step-by-Step Walkthrough

A product manager I know once spent three weeks arguing with her team about why new users kept dropping off after sign-up. Engineering blamed the onboarding screens. Marketing blamed the ad copy. Support had a folder full of "how do I actually start?" emails. Everyone was right about their slice and nobody could see the whole thing.

Then she drew a user journey map on a whiteboard — every step a new user takes, from first tap to first real moment of value — and the problem became obvious in about ten minutes. There was a dead zone between "account created" and "first useful action" where the app asked for a payment method before showing anyone what it did. The drop-off wasn't a copy problem or a screen problem. It was a sequencing problem, and you could only see it once the steps sat side by side.

That's what a user journey map does. Below is a worked example you can copy, plus the small set of rules that keep these maps useful instead of decorative.

What a user journey map actually is

A user journey map is a horizontal timeline of one user's experience as they try to accomplish a goal. You read it left to right through stages (the phases of the journey), and top to bottom through lanes (what's happening at each stage).

People confuse this with a swimlane diagram, so let me be precise: a swimlane diagram shows who does what, when — it's about handoffs between departments or systems. A journey map shows what one person experiences — their actions, yes, but also their thoughts, their feelings, and the moments that frustrate them. Same left-to-right shape, completely different content. A swimlane answers "where's the bottleneck in our process?" A journey map answers "where does our user start to hate us?"

The lanes you'll almost always want:

• Stage — the phase name (Discover, Sign Up, First Use, Habit).
• Actions — what the user physically does.
• Thoughts — what's going through their head, ideally in their own words.
• Emotions — a simple up/down curve. This is the lane everyone skips and it's the most valuable one.
• Pain points — where it breaks, stalls, or confuses.
• Opportunities — the fix or the idea this pain point suggests.

You don't need all six every time. But you need at least actions, emotions, and pain points, because the whole point is to find the gap between what people do and how they feel while doing it.

A worked example: onboarding for a coffee-subscription app

Let's map a real-feeling scenario. The persona is Maya, 29, a commuter who saw an ad for a coffee-subscription app — beans delivered, skip or pause anytime. Her goal: get her first bag of coffee ordered without overthinking it.

Here's the journey, stage by stage.

Stage 1 — Discover. Actions: Maya sees an Instagram ad, taps through to the App Store, reads two reviews, downloads. Thoughts: "Okay, fresh beans, that's nice, but is this going to be expensive?" Emotion: curious, mildly positive. Pain point: the App Store screenshots show the product but not the price. Opportunity: put a "from $14/month" line in the first screenshot.

Stage 2 — Sign Up. Actions: opens the app, taps "Get Started," is asked for email, then immediately for a payment method. Thoughts: "Wait, I haven't even picked a coffee yet and you want my card?" Emotion: a sharp dip — this is the low point. Pain point: payment requested before any value is shown. Opportunity: move the paywall after the first coffee selection.

Stage 3 — First Use. Actions: picks a roast, chooses a delivery frequency, places the order. Thoughts: "Oh, this part's actually easy and the quiz was kind of fun." Emotion: recovering, back to positive. Pain point: the roast descriptions are jargon-heavy ("washed Ethiopian, floral, tea-like") for someone who just wants "smooth and not bitter." Opportunity: add a plain-language tag next to each roast.

Stage 4 — Habit. Actions: gets a shipping notification, receives the bag, brews it, gets a "rate your roast" prompt. Thoughts: "This is good. I'd skip next month though, I still have beans." Emotion: satisfied. Pain point: no obvious way to skip a delivery without hunting through settings. Opportunity: surface "skip next delivery" right in the rating prompt.

Now line up just the emotion lane: positive → sharp dip → recovering → satisfied. That dip in Stage 2 is what people call the valley of frustration, and it's the single most important thing the map tells you. Maya doesn't churn because the coffee is bad or the app is ugly. She churns — if she churns — because you asked for her credit card before you earned it. Everything else on the map is a nice-to-have. The valley is the fix.

How to read the map once you've built it

A finished journey map isn't the deliverable. The decision it forces is.

Find the lowest point on the emotion curve and ask one question: what's the cheapest change that raises it? In Maya's case it's reordering two screens — payment after coffee selection. That's a sequencing change, not a redesign. It probably moves the activation number more than a month of copy tweaks would.

Then look for flat stretches where nothing good happens. Between receiving the coffee and the next order there's a long quiet gap — no contact, no delight, no reason to feel anything. Flat isn't as urgent as a deep valley, but it's where retention quietly leaks. A flat emotion lane is a prompt to add a moment: a brewing tip, a "you've saved X trips to the café" note, something.

The mistake I see most often is mapping the journey you wish users had instead of the one they have. If every emotion in your map is "delighted," you didn't map a journey — you mapped a brochure. Go talk to five real users, or read your support tickets, and put their actual words in the thoughts lane. The grumpy quotes are the gold.

Building one without the whiteboard

You can absolutely draw this on paper, and for a first pass you should. But the moment you want to share it, revise it, or map a second persona alongside the first, a static drawing gets painful.

This is where describing it in plain language beats dragging boxes. In Ridvay, you type the journey the way you'd explain it to a coworker — "map a user journey for a coffee subscription app, four stages from Discover to Habit, with lanes for actions, emotions, and pain points" — and you get a structured, editable map back. Then you do the real work: tweak a stage name, fix an emotion, drop in the actual quote your user said. The generation gets you to a draft in seconds; the editing is where your judgment goes. If you've ever turned messy notes into a diagram, it's the same idea — start from words, refine the shape.

A journey map is worth making the moment your team is arguing about why users behave a certain way and everyone's holding a different piece of the elephant. Lay the steps side by side, draw the emotion curve honestly, and the valley shows you where to spend your next two weeks.

Map your own product's journey and find its valley: start with a coffee-app onboarding map in Ridvay and edit the stages to match yours.