Why navigation is not information architecture

Something has changed, it looks cleaner, maybe even more logical.

But very often, nothing underneath has actually improved.

Navigationglossary×NavigationHow users move around a website or product.Open glossary term→ is just the surface.

Information architectureservice×Information ArchitectureImprove navigation, content structure, and findability so users can understand where things are and how to move through them.Open service→ is everything underneath it.

You can usually spot when the two have been confused because the same problems keep coming back. Users still can’t find things, they still hesitate, they still take longer routes than expected, and the instinct is to go back and adjust the navigationglossary×NavigationHow users move around a website or product.Open glossary term→ again.

Rename something. Move it. Add another option.

It becomes a cycle.

I’ve seen teams go through multiple iterationsglossary×IterationIteration is the process of repeatedly improving a product through cycles of testing, feedback, and refinement.Open glossary term→ of navigationglossary×NavigationHow users move around a website or product.Open glossary term→ without ever addressing the actual issue.

Each versionglossary×VersionA version is a specific iteration of software or a product at a point in time.Open glossary term→ looks slightly different, sometimes even slightly better, but the experience doesn’t fundamentally change. The frictionglossary×FrictionFriction refers to anything that slows users down or makes it harder for them to complete a task. It can be caused by poor design, unnecessary steps, unclear messaging, or technical issues.Open glossary term→ is still there, just in a slightly different place.

That’s because navigationglossary×NavigationHow users move around a website or product.Open glossary term→ doesn’t define how a systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ works.

It only exposes it.

If the underlying structure is unclear, inconsistent, or built around the wrong logic, no amount of navigationglossary×NavigationHow users move around a website or product.Open glossary term→ refinementglossary×RefinementRefinement is the process of preparing and clarifying backlog items before development.Open glossary term→ is going to fix that. At best, you make it marginally easier to move around a broken systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→. At worst, you add more complexity in an attempt to compensate for it.

I’ve worked on platformsglossary×PlatformA platform is a system or environment that enables users, services, or applications to interact, build, or operate.Open glossary term→ where the navigationglossary×NavigationHow users move around a website or product.Open glossary term→ looked perfectly reasonable at first glance. The labels made sense, the hierarchyglossary×HierarchyHierarchy is the organisation of elements to show importance and guide user attention.Open glossary term→ wasn’t obviously flawed, and everything felt like it was where you’d expect it to be.

But when you followed a journeyglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ through the systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→, things started to break down.

Content wasn’t grouped in a way that supported the task.

Related information lived in completely separate areas.

The same concept appeared in different places with slightly different language.

The navigationglossary×NavigationHow users move around a website or product.Open glossary term→ wasn’t the problem.

It was just reflecting it.

That’s usually the turning point.

Once you stop looking at navigationglossary×NavigationHow users move around a website or product.Open glossary term→ as the solution and start looking at the structure underneath, the focus shifts completely.

Instead of asking how do we label this, you start asking:

What actually belongs together?

What are users trying to do here?

What needs to happen before something else makes sense?

Those are information architectureservice×Information ArchitectureImprove navigation, content structure, and findability so users can understand where things are and how to move through them.Open service→ questions.

And they’re much harder to answer.

Because they require you to step away from how the organisation is set up and focus entirely on how users approach the problem. Not how things are owned internally, not how teams are structured, but how someone arriving fresh would expect things to work.

That often means unpicking decisions that have been in place for a long time.

I saw this clearly working across the NHS.

There were multiple navigationglossary×NavigationHow users move around a website or product.Open glossary term→ systemsglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→, multiple ways of structuring similar content, and a constant effort to improve findabilityglossary×FindabilityFindability is how easily users can locate the information or content they are looking for within a product or system. It depends on clear structure, intuitive navigation, and effective search, ensuring users can get to what they need without friction.Open glossary term→ by adjusting menus. New labels, new groupings, new entry points.

But the underlying structure hadn’t changed.

So users were still having to work things out for themselves. Still moving between areas that didn’t quite connect, still trying to understand how one part related to another.

Once the focus shifted away from navigationglossary×NavigationHow users move around a website or product.Open glossary term→ and onto structure, things started to change.

Instead of trying to surface everything through menus, we looked at how the systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ was organised at its core. What the primary groupings should be, how content should relate to each other, how consistencyglossary×ConsistencyConsistency is the use of uniform patterns, behaviours, and visual elements across a product to create familiarity and predictability. It helps users learn once and apply that knowledge throughout the experience.Open glossary term→ could be introduced so that once something was understood in one place, it carried across the rest of the experience.

Navigationglossary×NavigationHow users move around a website or product.Open glossary term→ then became much simpler.

Because it was no longer trying to compensate for a broken structure.

That’s the difference.

Good navigationglossary×NavigationHow users move around a website or product.Open glossary term→ feels clear because the structure behind it makes sense.

Bad navigationglossary×NavigationHow users move around a website or product.Open glossary term→ feels confusing because it’s trying to make sense of something that doesn’t.

In my experience, when teams say we need to fix the navigationglossary×NavigationHow users move around a website or product.Open glossary term→, what they often mean is users can’t find things.

And when users can’t find things, the problem is rarely the menu itself.

It’s how everything has been organised in the first place.

Navigationglossary×NavigationHow users move around a website or product.Open glossary term→ can guide you.

But it can’t fix a systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ that doesn’t make sense underneath.