Menu

IA

Wayfinding Review

A practical information architecture method for reviewing whether a product gives users enough orientation and context to move confidently.

How to use a wayfinding review to assess orientation cues, improve flow, and reduce the moments where users feel lost or uncertain.

4 min read

What it is

A review is a UX evaluation method used to assess how easily users can orient themselves, understand where they are, and move through a product or .

It focuses on the that help users navigate, such as page titles, breadcrumbs, , , and contextual cues.

Unlike , which looks at how users move, a review looks at how well the experience supports orientation and decision-making.

It is typically an expert-led review that identifies where users may feel lost, uncertain, or disconnected.

The goal is to ensure users always know where they are, where they can go, and how to get back.

Wayfinding reviews are useful when navigation technically exists, but users still do not feel oriented or in control.

When to use it

Use this method when users struggle with orientation or flow.

It is most useful when:

Users feel lost or confused in the product
Journeys are complex or multi-step
Navigation exists but lacks clarity
You are reviewing large or content-heavy systems
You want to improve overall user confidence

It is less useful when:

The product is simple or linear
You need behavioural data from users
Structure is not yet defined
Wayfinding reviews are often used alongside navigation testing, heuristic evaluation, and UX audits.

Key takeaway

Use a wayfinding review when users can technically move through the product, but the experience still leaves them unsure where they are or what to do next.

How to run it

Set up properly

Be clear on which journeys or areas you are reviewing, what people are trying to do, and which are meant to support them.

Define the key paths and scenarios in advance. Wandering the product looking for problems finds the ones you already suspected.

Run the method

A review is observational and analytical. You are assessing whether somebody always knows where they are, how they got there, and what their options are.

  1. Walk each journey as a user would, without your knowledge of the structure. Starting from a result or a deep link, not the homepage, is closer to reality.
  2. Assess the orientation cues at every step: breadcrumbs, headings, page titles, active states, and whether they agree with each other.
  3. Identify where somebody could lose their place, particularly after a , an error, or a cross-link into another section.
  4. Evaluate whether communicates as well as options. Knowing what is available matters less than knowing where you currently are.
  5. Capture issues and opportunities together, since most fixes are additions rather than corrections.

Focus on the user's perspective, not the 's logic. The structure can be entirely coherent to whoever built it and still leave people stranded.

Capture and make sense of it

The value comes from finding the moments of disorientation. Look across the review to identify:

  • Steps where location is unclear or contradicted
  • Journeys that break when entered from outside the homepage
  • Places offering no obvious way back or onward
  • Cues that exist but are too quiet to be noticed

Use this to improve flow and orientation. problems rarely stop a task outright, which is why they persist and quietly cost you completion.

What to look for

Focus on:

Orientation: do users know where they are
Direction: do users know where to go next
Context: is information relevant and clear
Recovery: can users easily go back or change direction
Consistency: are patterns predictable

Where it goes wrong

Most issues come from:

If users feel lost, they will leave.

Starting every walkthrough from the homepage, which almost nobody does
Reviewing with your knowledge of the structure intact
Checking that navigation offers options without checking it says where you are
Adding more signals rather than making the existing ones louder
Treating disorientation as a minor issue because it rarely stops a task outright

What you get from it

Done properly, this method gives you:

The moments where somebody loses their place
Journeys that break when entered from search rather than the front door
Orientation cues that exist but are too quiet to notice
Fixes for a problem that quietly costs completion rather than blocking it

Key takeaway

It helps users feel in control at every step.

Get in touch

If this sounds like something you need, we can help you make your product easier to navigate and feel intuitive from start to finish.

No guesswork. No assumptions. Just flow that makes sense.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is wayfinding in UX?

Wayfinding refers to how users understand where they are and how to move through a system.

What is a wayfinding review?

It is a method used to evaluate how well a product supports navigation and orientation.

When should you use a wayfinding review?

Use it when users feel lost or confused in journeys.

How is it different from navigation testing?

Navigation testing focuses on behaviour, while wayfinding review focuses on clarity and signals.

Does a wayfinding review improve UX?

Yes. It helps users move confidently through your product.

Quick take

If users feel lost in your product, run a wayfinding review to fix the flow.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer