Skip to content
Tutorials Center
My learning

Topics

Lesson 14 of 36 Β· User Research

Journey Maps and User Flows

Learn how journey maps show a person's whole experience over time and how user flows show the screens and decisions in a task, with diagrams and a runnable flow checker.

Two diagrams appear on almost every UX wall: the journey map and the user flow. They look similar (boxes and arrows, steps from left to right) but answer different questions. A journey map shows how a person experiences a goal over time, including feelings. A user flow shows how a person moves through a product to complete a task, including decisions and screens.

Journey maps

A journey map follows one persona through a scenario from start to finish. Typical layers:

  • Phases: large stages, such as Discover, Choose, Buy, Receive, Get help.
  • Actions: what the person does in each phase.
  • Touchpoints: where they interact: website, email, shop, phone call.
  • Thoughts and feelings: often drawn as an emotion line that rises and falls.
  • Pain points and opportunities: the moments to fix or improve.

Build it from research, not from guesses, and cover the whole experience, including steps outside your product (comparing prices, asking a friend, waiting for delivery). The low points show where to focus.

Phase Action Feeling Opportunity
Discover Searches "waterproof jacket" Curious Clear comparison pages
Buy Enters delivery address Annoyed (re-types it) Remember address
Wait Checks tracking Anxious Proactive status emails
Return Prints a label Frustrated Label in the app

A service blueprint extends a journey map with what happens behind the scenes (staff actions, systems), helpful when the experience crosses many teams.

User flows

A user flow is a diagram of the path a user takes to complete a task in a product. Standard shapes: a rounded rectangle for start and end, rectangles for screens or steps, diamonds for decisions, and arrows for the direction. Flows help you:

  • Check that every path leads somewhere (no dead ends).
  • Find unnecessary steps.
  • Plan error and edge cases (wrong password, empty cart, no network).
  • Agree with developers on the logic before screens are drawn.
flowchart TD
  S(["Start: tap Log in"]) --> A["Enter email and password"]
  A --> B{"Correct?"}
  B -- "yes" --> C["Home screen"]
  B -- "no" --> D["Show error with hint"]
  D --> E{"Try again or reset?"}
  E -- "try again" --> A
  E -- "reset" --> F["Reset password email"]
  F --> G(["End: back to login"])
  C --> H(["End"])

Note both the happy path and the error path.

Draw the happy path (everything goes well) first, then add errors and edge cases. A good question for every step: "What if this fails?"

Journey map or user flow?

  • Use a journey map to understand feelings, motivations and the bigger context, usually early.
  • Use a user flow to design and check the logic of a specific task, usually later.

Two diagrams, two questions

Journey map How does it feel over time?
1 / 2

A stand-in: checking a flow for dead ends

A flow can be stored as a graph. This stand-in lists screens and the screens they lead to, then looks for dead ends (a step with no way forward that is not an end) and unreachable screens. It teaches why flows are checked, not how a real design tool works.

JS Flow dead-end checker (stand-in)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Note that stuck is reported as unreachable here (nothing links to it); a dead end would appear if a reachable screen had no exits.

Tips

  • Name steps with verbs and nouns ("Enter address"), not tool jargon.
  • Keep one diagram per goal; avoid a spaghetti chart of the whole product.
  • Show decisions and system responses, not only user actions.
  • Review the flow with developers and support staff; they know the edge cases.
  • Measure real flows with analytics later and compare with your design (see the process).

Check your understanding

Quick check Β· 4 questions

of 4 answered You scored / 4 Β· perfect!

  1. 1. What is the main difference between a journey map and a user flow?

    Different questions: experience across time versus the logic of moving through a product.
  2. 2. What is the happy path?

    Design the happy path first, then add errors and edge cases.
  3. 3. Which diamond shape in a user flow represents?

    Diamonds are decisions with different outgoing paths.
  4. 4. Why include steps outside your product in a journey map?

    Important pain points often occur before or after the product.

Summary

  • Journey maps follow a persona's experience, feelings and touchpoints over time.
  • User flows chart the screens, decisions and paths of a specific task.
  • Draw the happy path, then errors and edge cases; check for dead ends.
  • Build both from research and review them with teammates.

Next: Content Inventory and Audit