What is a user journey: a practical guide

michaelbell | 7 August 2026

A user journey is a visual representation of the steps a person takes to achieve a specific goal while interacting with a product or service, capturing their actions, touchpoints, thoughts, emotions, and pain points across time. According to Nielsen Norman Group (NN/g), the standard authority on UX research, a well-constructed map integrates all of these elements into a single shared artefact that teams can act on.

TL;DR — what a user journey map contains:

Actor/persona: who is taking the steps
Scenario and goal: the specific situation being mapped
Stages: the phases of the experience (e.g. Awareness, Consideration, Purchase, Support)
Actions and touchpoints: what the user does and where they interact
Thoughts and emotions: what they are thinking and feeling at each stage
Pain points: where friction or failure occurs
Opportunities: where the experience can be improved

NN/g and Salesforce both treat journey mapping as a core UX practice, not an optional extra. If you work on websites, digital products, or any customer-facing service, understanding user journeys is one of the most practical skills you can develop.

Key takeaways

A user journey map is most valuable when it is built from real evidence, kept visible, and connected directly to the product backlog or development priorities.

Point	Details
Start with one scenario	Map a single persona and goal; broad maps serve no one and get ignored.
Ground the map in data	Use analytics, support tickets, and user interviews before drawing anything.
Capture the emotion curve	The dips in the curve show where to act; that is the map’s most actionable output.
Connect maps to delivery	Link opportunities to user stories or backlog items so the map drives real change.
MB Web applies this process	MB Web runs journey-mapping discovery workshops that feed directly into web design and development projects.

What does a user journey actually capture?

A user journey goes well beyond a simple list of clicks. It captures the full human experience of trying to get something done, including the moments of confusion, delight, and frustration that analytics alone cannot explain.

The map is always anchored to a specific actor and scenario. You are not mapping “all users” in the abstract. You are mapping one persona, such as a first-time donor to a charity website, in one situation, such as making a gift on a mobile device after seeing a social media post. That specificity is what makes the map useful rather than decorative.

Standard fields on a journey map include:

Actions: the concrete steps the user takes (clicks, form submissions, phone calls)
Touchpoints: the specific interfaces or moments where they interact with your product or organisation
Channels: the medium (website, email, app, in-person)
Thoughts: what the user is thinking or asking themselves at each stage
Emotion curve: a visual line showing how their emotional state rises and falls across the journey
Pain points: moments where the experience breaks down or causes frustration
Opportunities: where a design or content change could meaningfully improve the experience

Maps also vary by elevation. A high-level current-state map shows what is happening today across the whole experience. A future-state map shows what the ideal experience could look like. The GitLab Handbook’s guidance on user journeys makes the point clearly: there is no single correct format, and the right elevation depends on the business question you are trying to answer.

How does a user journey differ from a user flow and a customer journey?

These three terms get used interchangeably, but they describe different tools with different purposes. Choosing the wrong one wastes time and produces an artefact nobody uses.

A user journey is macro. It spans the full arc of an experience, often covering days, weeks, or months, and crosses multiple channels. It answers the question: what is the person going through, emotionally and practically, from first awareness to long-term use?

A user flow is micro. It maps the specific sequence of screens or steps a user follows to complete a discrete task inside a product, typically in minutes or hours. It answers the question: what is the exact path through the interface? NN/g’s comparison of user journeys and user flows is the clearest published treatment of this distinction: journeys are cross-channel and long-term; flows are product-centred and short-term.

A customer journey is similar in scope to a user journey but tends to be used in marketing and CRM contexts, focusing on commercial stages (Awareness, Consideration, Purchase, Retention) rather than the granular UX of a specific task.

The tools are complementary. A journey map shows where the experience is failing; a user flow provides the tactical blueprint for how to fix it at the screen level. NN/g puts it plainly: using both balances strategic vision with tactical implementation.

Dimension	User journey	User flow	Customer journey
Scope	Cross-channel, end-to-end	Single task or screen sequence	Commercial lifecycle
Timeframe	Days, weeks, or months	Minutes to hours	Weeks to years
Primary output	Emotion curve, pain points, opportunities	Screen-by-screen task logic	Funnel stages, conversion data
Typical users	UX researchers, product managers, web teams	UX designers, developers	Marketing, CRM, sales teams

What are the key components of a user journey map?

A map that is missing critical components tends to sit on a wall looking impressive but never feeding into any real decision. These are the components that make a map genuinely useful.

Persona and scenario header. Every map needs a named actor and a clearly stated scenario at the top. Without this, the map tries to represent everyone and ends up representing no one.

Phases or stages. These are the high-level chapters of the experience: Discover, Evaluate, Sign Up, Use, Seek Help, for example. Phases give the map its horizontal structure.

Actions and touchpoints. Under each phase, list what the user actually does and where they do it. A touchpoint might be a Google search, a landing page, a confirmation email, or a live chat window.

Thoughts and emotion curve. This is where journey maps earn their keep. Capturing what the user is thinking (“Is this site trustworthy?”) and plotting their emotional state as a curve across the phases reveals the moments that matter most. A sharp dip in the emotion curve is a signal that something needs fixing.

Pain points and opportunities. Pain points are the specific moments of friction. Opportunities are the design or content changes that could resolve them. Listing both in the same map means the team leaves the workshop with a prioritised action list, not just a diagnosis.

Internal ownership. For each opportunity, note which team or individual owns it. A map without ownership is a map that never gets acted on.

When should you use a journey map, and what are the benefits?

Journey maps are most valuable at specific moments in a product or website project. Using them at the wrong time, or for the wrong question, produces a polished document that nobody references.

Map types and when each fits:

Current-state map: use when you need to understand and align on what is happening today before making changes. Ideal at the start of a redesign or audit.
Future-state map: use when you are designing a new experience or a significant improvement. Shows the target state the team is building towards.
Day-in-the-life map: use when the product is one small part of a much larger daily context. Useful for understanding where your service fits in the user’s broader life.
Service blueprint: use when you need to align front-stage (user-facing) and back-stage (internal process) activities. Particularly useful for organisations with complex operations behind the scenes.

The concrete benefits of mapping are well documented. Salesforce’s overview of user journey mapping highlights three that consistently show up: cross-functional alignment (everyone sees the same picture), prioritisation (pain points become a ranked backlog), and reduced churn (fixing friction at key stages keeps users from dropping off).

Pro Tip: Run a current-state mapping workshop before any significant website redesign. The shared understanding it creates cuts the number of scope-creep arguments later in the project.

How do you create a user journey map, step by step?

1. Define scope and pick one scenario

Start with a single persona and a single goal. Trying to map everything at once produces a map too vague to act on. Write the scenario as a sentence: “A small charity trustee visits the website for the first time and tries to make a recurring monthly donation on a mobile device.”

2. Gather research before you draw anything

NN/g is clear on this: maps built from internal assumptions become hypothetical exercises, not strategies. Collect:

Analytics data to see where users drop off (see MB Web’s guide to web analytics for business owners)
Support tickets and live chat logs to find recurring pain points
User interviews or usability sessions to capture thoughts and emotions
Session recordings (tools like Hotjar or Microsoft Clarity) to observe real behaviour

3. Facilitate a cross-functional workshop

Bring in people from design, development, marketing, and customer support. Each team sees a different slice of the experience. A 90-minute workshop with the right people in the room typically produces a draft map and a prioritised list of opportunities. Timebox each phase to keep momentum.

4. Build the map

Plot the stages across the top. Under each stage, fill in actions, touchpoints, channels, thoughts, and emotions. Draw the emotion curve last, once the team has agreed on the emotional texture of each phase. Use sticky notes on a whiteboard or a digital board for the first draft.

5. Prioritise opportunities using impact vs effort

Once pain points are listed, score each opportunity on two axes: how much it would improve the experience (impact) and how much work it requires (effort). High-impact, low-effort items go first. JPatton Associates’ work on story mapping shows how to connect these opportunities directly to a product backlog, turning map insights into prioritised epics and stories.

6. Validate with data and iterate

A map is a hypothesis until the data confirms it. After implementing changes, track the relevant analytics events or conversion rates to see whether the emotion curve actually improved. Treat the map as a living document: assign an owner, version it, and update it when the product or user behaviour changes.

Pro Tip: Use the role of analytics in your web strategy to set up event tracking before the workshop. Having real drop-off data on the table changes the conversation.

Two examples that show what a journey map captures

Example 1: new user signing up for an account

Scenario: A freelance designer discovers a project management tool via a LinkedIn post and tries to sign up and complete their first project.

Stages: Discover, Evaluate, Sign Up, First Use, Return Visit
Key emotion dip: during Sign Up, when the user hits an unexpected email verification step and a mandatory credit card field for a “free” trial
Pain points: unclear pricing, friction in the verification flow, no onboarding checklist after sign-up
Opportunities:
1. Remove the credit card requirement from the free trial sign-up
2. Add a three-step onboarding checklist visible on first login

Example 2: donor on a charity website

Scenario: A supporter sees a social media appeal and visits the charity’s website to make a first-time monthly donation on a smartphone.

Clicks a social post and lands on a generic homepage (not a campaign-specific landing page)
Searches for a “Donate” button, finds it buried in the navigation
Starts the donation form, which is not mobile-optimised
Abandons the form at the payment step because the page does not display a security badge

Cross-channel touchpoints: social media, website, email confirmation, direct debit letter

Service blueprint note: the back-stage fulfilment (direct debit setup, gift aid processing) is invisible to the donor but directly affects their trust. A service blueprint would map these internal steps alongside the donor-facing experience.

For charity-specific web projects, MB Web’s charity website design service is built around exactly these kinds of journey-led improvements.

Figma and Miro both offer free journey map templates that you can copy and adapt for either scenario above. Start with a low-fidelity version in a shared Miro board for the workshop, then move to a polished Figma version for stakeholder presentations.

Which tools and resources help you map user journeys?

The tool matters less than the process, but the right tool for the moment makes the work faster and the output more useful.

For collaborative workshops (low-fidelity):

Miro: the most widely used digital whiteboard for live mapping sessions. Its sticky-note format mirrors a physical workshop and works well for remote teams.
FigJam: Figma’s whiteboard tool, ideal if your team already lives in Figma. Keeps the map close to the design files.
Paper and sticky notes: still the fastest way to run an in-person session. Photograph the output and digitise it afterwards.

For polished stakeholder deliverables (high-fidelity):

Figma: the standard for UX teams producing presentation-ready maps. Community templates are available for free and cover most standard formats.
Miro: also works at higher fidelity with its built-in journey map template.

ProductSchool’s comparison of user flows and user journeys recommends starting low-fidelity for alignment workshops and iterating towards high-fidelity artefacts for stakeholder communications. That is good practical advice: a polished map produced before the team has agreed on the content is a waste of design time.

For further reading:

NN/g Journey Mapping 101 — the definitive reference for map components and best practice
NN/g User Journeys vs. User Flows — essential for understanding when to use each tool
Userflow’s guide to journey map types — practical examples and SaaS-focused templates

Pro Tip: If your team is new to mapping, start with Miro’s free journey map template and a 90-minute session. You do not need a perfect tool to produce a useful map.

How MB Web uses journey mapping in web projects

At MB Web, journey mapping sits at the start of every significant web design and development project. Before a single wireframe is drawn, we work with clients to define the primary persona, the scenario that matters most to the business, and the current-state experience as the user actually lives it.

The process typically runs like this: discovery workshop with the client’s cross-functional team, followed by a review of available analytics and support data, then a draft map that the whole team can see and challenge. That map feeds directly into the site architecture, the content hierarchy, and the development backlog. In Agile projects, we connect journey opportunities to user stories using the approach described by JPatton Associates, so every sprint has a clear line back to a real user need.

We keep the map as a living document throughout the project. When analytics data comes in after launch, we revisit the emotion curve and update the opportunities list. Ownership is assigned: one person on the client side is responsible for the map, and we review it together at each quarterly check-in.

Pro Tip: Assign a named owner for the journey map on day one. A map without an owner gets updated once and then forgotten.

The business case for investing in UX design is well established, and journey mapping is one of the most cost-effective ways to make that investment count. It surfaces the right problems before development begins, which is always cheaper than fixing them after launch.

Why journey mapping matters more than most small businesses realise

Most small businesses and charities we work with have never drawn a journey map. They know their customers, they have built their website with care, and they are genuinely puzzled when the analytics show people dropping off at the payment page or the contact form.

The gap is almost always the same: the site was built from the inside out, reflecting how the organisation thinks about itself rather than how a visitor experiences it. A journey map forces the outside-in view. It makes the friction visible, names it, and gives the team a shared language for fixing it.

What we find, consistently, is that the most impactful changes are rarely the expensive ones. A clearer call to action, a mobile-optimised form, a trust signal in the right place. These are the things a journey map surfaces. And they are the things that move conversion rates.

MB Web can help you map and improve your users’ experience

If you have read this far and are thinking “we should do this for our website,” you are probably right. MB Web runs discovery workshops that take a client from zero to a validated current-state journey map in a single day. We combine that with an analytics audit to ground the map in real behavioural data, not guesswork.

From there, we move into web design and website development that is built around the map’s findings: the right page structure, the right content hierarchy, and the right touchpoints to reduce friction and improve conversions. We work with local businesses across Sussex, Surrey, Kent, and the South East, as well as national brands and charities. If you would like to talk through what a discovery workshop looks like for your project, get in touch with the MB Web team and we will take it from there.

Sources

The sources below are the most useful references for anyone wanting to go deeper on user journey mapping.

FAQ

What is a user journey in simple terms?

A user journey is a map of the steps, thoughts, and emotions a person experiences while trying to achieve a goal with a product or service. It captures the full arc of the experience, from first awareness to task completion, across every touchpoint and channel.

What is the difference between a user journey and a user flow?

A user journey is macro: it spans multiple channels and a long timeframe, focusing on emotions and pain points. A user flow is micro: it maps the specific screen-by-screen sequence a user follows to complete a single task, typically in minutes.

How does a user journey differ from a customer journey?

A user journey focuses on the lived UX of a specific task or scenario, including thoughts and emotions. A customer journey tends to be used in marketing contexts, mapping commercial stages such as Awareness, Consideration, and Purchase, with less emphasis on granular interaction detail.

What is a user journey in Agile?

In Agile teams, a user journey map provides the high-level narrative that feeds story mapping and backlog prioritisation. Opportunities identified on the map are converted into epics and user stories, ensuring development work connects directly to real user needs.

What are the main components of a journey map?

The core components are: a named persona and scenario, phases or stages, actions and touchpoints, channels, thoughts, an emotion curve, pain points, and opportunities. Each opportunity should have a named owner to ensure it gets acted on.