Home › The Garage › User journey mapping
Design Thinking

User Journey Mapping

A process map shows how the work flows. A journey map shows how it feels — stage by stage, from the only point of view that ultimately decides whether the process is any good: the person going through it.

By LeanBean · Updated November 2026 · 7 min read
What's in this guide
  1. What a journey map is
  2. Journey map vs process map
  3. The anatomy: stages and rows
  4. How to build one, step by step
  5. Reading the emotion curve
  6. Common mistakes
  7. Common questions
Discover Apply Wait Decision Onboard EMOTION "Have they forgotten me?" PAIN → OPPORTUNITY Silent wait,no status Proactive statusupdates
A journey map makes the low point obvious — here, a silent wait — and turns it into a specific opportunity.

What a journey map is

A user journey map (or customer journey map) is a visual of one person's end-to-end experience of a process or service, broken into stages. For each stage it records what the person does, what they think, how they feel, and the touchpoints they interact with. The point is to surface the experience — where it's smooth, where it hurts, and where a small change would matter most — from the perspective of the human going through it, not the organisation delivering it.

It's a core design-thinking artefact because it operationalises empathy: instead of asserting what customers feel, you chart it stage by stage and make it impossible to ignore.

Journey map vs process map

These two are often confused, and using the wrong one hides the real problem.

 Process map (swimlane)User journey map
Point of viewThe organisation delivering the workThe person experiencing it
ShowsSteps, lanes, handoffs, decisionsActions, thoughts, emotions, touchpoints
FindsOperational waste & reworkExperience pain & drop-off
Best question"Where is the work inefficient?""Where does this feel bad?"

They are complementary, not competing. A silent three-day wait might look perfectly efficient on a swimlane diagram — no rework, no obvious waste — while it is the single worst moment on the journey map. You need both lenses: the process map to fix the flow, the journey map to fix the felt experience.

The anatomy: stages and rows

A journey map is a grid. Columns are the stages, in order, from the person's first contact to their last. Rows are the layers of their experience:

The emotion curve earns its keep
A table of actions tells you what happens. The emotion curve tells you where it matters. A deep, sustained dip is where you focus — it's where you lose people, generate complaints, and create churn. Everything else is secondary.

How to build one, step by step

  1. Pick one persona and one scenario. "A first-time applicant filing a claim," not "all customers." One person, one path — the happy path first.
  2. Lay out the stages. Name the 4–7 stages of their journey, left to right, in the person's words (Discover → Apply → Wait → Decision → Onboard), not your internal process names.
  3. Fill actions and touchpoints from evidence. Use what you actually know — interviews, support tickets, session data — not what the policy says should happen. Map the current reality.
  4. Add thoughts, then emotions. For each stage, capture the question in their head, then rate the feeling. Join the ratings into the curve.
  5. Mark the pains, then turn each into an opportunity. A pain is a symptom; the opportunity is the specific move that removes it. "Silent wait" → "proactive status at 24h and 72h."
  6. Prioritise the deepest dip. Don't try to lift the whole curve at once. Fix the lowest, most-felt moment first — see Moments of Truth for why those specific moments carry disproportionate weight.

Reading the emotion curve

Three shapes tell you most of what you need:

Common mistakes

Map the flow and the feeling.

LeanBean turns a plain-language description of any process into a professional map, runs a design-thinking pass that builds the user journey, and sequences the fixes into a NOW / NEXT / LATER roadmap. Free to start.

Build your first map free →

Keep learning in the Garage

Short, practical lessons on Lean, process mapping and AI-ready operations — the same thinking that powers LeanBean, in two minutes or less. Follow along and build the habit.

Common questions

What is a user journey map?

A visual of a person's end-to-end experience of a process or service, broken into stages. For each stage it records what they do, what they think, how they feel, and which touchpoints they hit — so you can see where the experience breaks down, not just where the work is inefficient.

How is a journey map different from a process map?

A process map shows the organisation's workflow — the steps, lanes and handoffs. A journey map shows the same end-to-end flow from the customer's side — their actions, emotions and friction. The process map finds operational waste; the journey map finds experience pain. The strongest improvement work uses both.

What are the rows of a journey map?

Columns for each stage; rows for the user's actions, their thoughts or questions, their emotions (often drawn as a curve), the touchpoints involved, and the pain points and opportunities. The emotion curve is what makes the low points impossible to ignore.

When should I draw a journey map?

When the problem is about experience, not just throughput — complaints, churn, abandoned applications, low adoption — or before redesigning a service, so the redesign fixes the moments that actually matter to the person.

Related guides: What is design thinking? · Moments of Truth · Design thinking for process improvement