Yellow camper van driving along a desert road
Home / CRO & Experience Audits / Journey analysis & prioritised recommendations
CRO & Experience Audits · Journey analysis

Journey analysis: see the whole road, then fix what matters first

I map how people actually move through your product or site - across pages, sessions, devices and roles - find where friction builds up, and turn it into a ranked plan your team can start on immediately.

Journey mappingDrop-off analysisCumulative frictionImpact/effort prioritisation

Why journeys, not pages

Most analysis looks at pages: this page has a high exit rate, that form has a low completion rate. Useful, but incomplete. Users don't experience pages; they experience journeys - a sequence of steps across screens, sessions, devices, emails and sometimes other people. And friction in journeys is usually cumulative: a slightly unclear label here, a repeated field there, a wait with no explanation, an email that uses different words from the app. Each is tolerable. Together, they are enough to make someone give up.

Journey analysis looks at the whole road. It maps the path people actually take, identifies where friction accumulates, and explains why - so fixes target the causes rather than the most visible symptom.

Is this you?

When journey analysis helps

01

Drop-off you can't explain

Analytics shows where people leave, but not why.

02

Multi-step processes

Onboarding, applications, approvals and purchases that span several sessions.

03

Several user types

Different people take different routes through the same product.

04

Several surfaces

Web, mobile, email and portals all play a part.

05

Handoffs between people

Work passes between customers, staff and partners.

06

Too many possible fixes

You need a defensible order of work.

What gets mapped

A journey map lines up, step by step:

LayerWhat it captures
StepsWhat the user is trying to do at each stage
TouchpointsWhere it happens - page, screen, email, call, document
BehaviourWhat actually happens - from analytics, recordings and observation
FrictionWhere people hesitate, repeat, fail or wait
Thoughts and questionsWhat users are wondering, from interviews and testing
OpportunitiesWhat could remove or reduce the friction

For different user types, I map separate journeys and compare them. On a B2B hospitality equipment platform, three buyers - a decisive café owner, a first-time operator and a spec-comparing buyer - took completely different routes and struggled at different points; one generic journey served none of them. See persona-led UX for B2B buyers.

Evidence sources

Journey analysis is only as good as its evidence. I combine:

  • Analytics - entry points, paths, step-by-step drop-off, segmented by source, device and audience.
  • Session recordings and heatmaps - where permitted, to see hesitation and repeated actions.
  • Support and sales data - the questions people ask and when they ask them.
  • Interviews and usability sessions - the "why" behind the behaviour.
  • Heuristic review - principles such as visibility of system status and error prevention applied to every step.

Prioritised recommendations

The part most teams value most is the prioritisation. Every opportunity is scored so the team can start work immediately:

PriorityImpactEffortTypical examples
Do nowHighLowClearer status and next steps; removing redundant fields; fixing broken error messages
Plan nextHighHighRestructuring navigation; rebuilding a flow; adding save-and-resume
BatchLowLowCopy fixes, spacing and consistency tweaks grouped into one release
ReconsiderLowHighFeatures requested internally with little evidence of user need

Where relevant, a third factor is added - compliance risk in healthcare and finance, or revenue exposure in commerce - so a "quick" change to a sensitive step gets the care it needs.

The process

How I run journey analysis

  1. 01

    Choose journeys and users

    The journeys that matter most, for each distinct user type.

  2. 02

    Collect evidence

    Analytics, recordings, support data, interviews and heuristic review.

  3. 03

    Map current journeys

    Steps, touchpoints, behaviour, friction and questions.

  4. 04

    Find the causes

    Group friction by root cause rather than symptom.

  5. 05

    Generate and score opportunities

    Impact, effort and, where needed, risk.

  6. 06

    Deliver the plan

    A ranked backlog with owners, measures and a suggested sequence.

Measuring the result

Each recommended change comes with a measure, so the team knows whether it worked:

  • Completion rate and time for each journey.
  • Drop-off at the steps that changed.
  • Support contacts related to the journey.
  • Repeat actions and errors per session.
  • For B2B, progression signals such as return visits and document downloads.

What you get

01

Current-state journey maps

For each key journey and user type.

02

Friction inventory

Every issue located, evidenced and grouped by cause.

03

Opportunity backlog

Scored by impact, effort and risk.

04

Recommended sequence

What to do now, next and later.

05

Measurement plan

How to tell whether each change worked.

06

Future-state sketch

How the improved journey should flow.

Frequently asked questions

How is journey analysis different from a journey map workshop?

Workshops capture what a team believes. Journey analysis tests those beliefs against behavioural data, support evidence and users - and ends in a prioritised plan.

Can you analyse journeys that span offline steps?

Yes. Calls, documents and in-person steps are mapped alongside digital ones, based on interviews with the people involved.

Do we need session recording tools?

They help but aren't essential. Analytics, support data and a few moderated sessions provide most of what's needed.

How detailed is the prioritisation?

Each opportunity has an impact and effort rating agreed with your team where possible, plus a measure. The result is a backlog ready to plan into sprints.

What if the analysis shows a bigger structural problem?

Then the plan says so, with the evidence - and separates the quick wins you can do now from the structural work that needs design.

Sources

Every statistic in this page links to its original publisher. Figures were checked against these sources on September 29, 2026.

  1. 10 Usability Heuristics for User Interface Design - Jakob Nielsen, Nielsen Norman Group
Let's solve something

Know there's friction, but not where to start?

Let's map the journey and rank the fixes. Book a 30-minute call.

Book a 30-min call ↗