What is a User Journey?

Table of content

A user journey is a representation of the broader experience a person has while trying to achieve a goal, including stages, touchpoints, context, actions, and perceptions over time.

TL;DR

A user journey describes the broader experience around achieving a goal over time.
It can include touchpoints inside and outside the product.
Journeys often capture stages, actions, questions, emotions, and pain points.
A user flow is usually narrower and more interface-specific.
Journey mapping helps teams see where experience problems cross product boundaries.

What does a user journey look like?

Take a traveler booking a flight. The journey can begin before they open the product: deciding dates, comparing destinations, checking budget, asking friends, searching flights, booking, receiving updates, traveling, and handling a disruption.

The product experience sits inside that larger journey.

What does a user journey map include?

the user goal
stages over time
actions and touchpoints
questions or information needs
emotions and confidence
pain points
opportunities

User journey vs. user flow

A user flow maps the product steps used to complete a specific task. A user journey zooms out to include context around the task and can span several channels.

User journey vs. customer journey

The terms overlap. A customer journey often includes the wider commercial relationship such as discovery, purchase, billing, support, and renewal. “User journey” is commonly focused on use of the product or service.

How do you create a user journey map?

Choose one user segment and goal.
Define the beginning and end of the journey.
Collect evidence from research and product data.
Map the major stages.
Add actions, touchpoints, questions, and pain points.
Identify moments of high friction or uncertainty.
Prioritize opportunities rather than trying to fix every moment.

Common journey-mapping mistakes

Inventing emotions without research

A journey map should not become fiction with sticky notes.

Making one generic journey for everyone

Different roles and contexts can produce very different experiences.

Mapping only product screens

Then you have created a flow, not a broader journey.

The bottom line

A user journey asks: what is the person experiencing before, during, and after the part of the product we can see?

Relevant Figr resource

Read What Is a User Journey Map? for a deeper guide.

Definition