Download the Resource here

A user journey map can look impressive.

Colourful stages.
Sticky notes.
Emotions.
Pain points.
Touchpoints.

But a beautiful journey map isn't automatically useful.

The real question is:

Does it help the team understand what users need and decide what to improve next?

What is a user journey map?

A journey map represents an experience from the user's perspective.

It helps us understand:

• What the user is trying to accomplish
• What they actually do
• What they think
• How they feel
• Where they struggle
• Where opportunities exist

A journey map connects:

User Goal → Actions → Touchpoints → Thoughts → Emotions → Pain Points → Opportunities

Notice what's missing?

A list of screens.

Because users don't experience your product as a collection of screens.

They experience a journey.

Start with one specific journey

One common mistake is trying to map the entire customer experience at once.

Instead, choose one specific scenario.

For example:

• Ordering food
• Booking a flight
• Booking a doctor's appointment
• Applying for a job
• Returning an online purchase
• Opening a bank account
• Signing up for an app

Then define:

When ______, the user wants to ______ so that ______.

This gives the journey a clear scope.

Map what users actually do

There's an important distinction between observation and interpretation.

Instead of writing:

“User gets confused.”

Write something observable:

“User opens the FAQ after failing to understand the pricing.”

The second statement gives you something you can investigate.

The workbook also emphasises using real research evidence rather than inventing user quotes to make the journey map feel realistic.

Don't forget the experience outside the product

Users may move between:

Website → Email → App → Customer Support → Physical Location

Those transitions matter.

Look for:

• Channel switches
• Repeated information
• Handoffs
• Waiting
• Offline interactions

A journey map should capture the experience, not just the digital interface.

Find the friction

Now look for moments where users:

• Hesitate
• Repeat work
• Get confused
• Make errors
• Wait
• Abandon
• Ask for help
• Switch channels
• Create workarounds
• Lose confidence

Then ask:

What happened?

What was the user trying to do?

Why was it difficult?

What evidence do we have?

What was the impact?

Don't turn every pain point into a feature

This is where journey mapping becomes strategic.

Suppose:

Pain point:
Users don't know the final price until checkout.

The immediate reaction might be:

“Let's add another pricing component.”

But pause.

The underlying need might be:

Users need confidence that they understand the total cost before committing.

Now the opportunity becomes:

How might we help users understand the total cost earlier in the journey?

The sequence becomes:

Pain Point → Need → Opportunity → Ideas

That's a much better starting point for design.

Prioritize instead of fixing everything

Not every opportunity deserves the same amount of attention.

The workbook suggests considering:

Impact + Frequency + Evidence Confidence + Effort

It's a decision aid, not a mathematical truth. Context still matters.

The goal isn't to solve everything.

It's to identify what matters most.

The 60-second journey mapping formula

When you're stuck, remember:

USER → GOAL → STAGES → ACTIONS → FRICTION → WHY → OPPORTUNITY → NEXT

Then ask:

What should we investigate or test next?

Because that's where the map becomes useful.

The real purpose of journey mapping

A journey map isn't the outcome.

Better decisions are the outcome.

Don't just map the journey.

Map the experience.
Find the friction.
Design what matters.

That is where journey mapping becomes more than a workshop exercise.