Why navigation is not information architecture

Navigationglossary×NavigationNavigation is the system of menus, links, and cues that lets people move through a product and reach what they need. It exposes the underlying structure, and is how most users experience that structure.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×NavigationNavigation is the system of menus, links, and cues that lets people move through a product and reach what they need. It exposes the underlying structure, and is how most users experience that structure.Open glossary term→ again. Rename something. Move it. Add another option. It becomes a cycle. 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 navigation 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 friction is still there, just in a slightly different place.

The cycle is self-reinforcing because each round produces something visible. A new menu can be shown, discussed and approved, which registers as progress. The structural work behind it produces a decision about what belongs together, which is harder to demonstrate and easier to postpone.

Navigationglossary×NavigationNavigation is the system of menus, links, and cues that lets people move through a product and reach what they need. It exposes the underlying structure, and is how most users experience that structure.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 navigation refinementglossary×RefinementRefinement is the ongoing work of clarifying, breaking down, and sizing backlog items before they enter development. It is where ambiguity gets resolved while resolving it is still cheap.Open glossary term→ will fix that. At best, you make it marginally easier to move around a broken system. 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×NavigationNavigation is the system of menus, links, and cues that lets people move through a product and reach what they need. It exposes the underlying structure, and is how most users experience that structure.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 journey through the system, 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 navigation wasn't the problem. It was just reflecting it.

The clearest tell is a menu that has grown to cover for the structure. Extra entry points, duplicated links, and a section called something like other are all attempts to route around a grouping that does not match how people think about the content.

Searchglossary×SearchSearch is the functionality that allows users to find content or information by entering queries. It relies on indexing, metadata, and relevance algorithms to return useful results.Open glossary term→ logs usually confirm it. When people are searching for terms that already exist as navigationglossary×NavigationNavigation is the system of menus, links, and cues that lets people move through a product and reach what they need. It exposes the underlying structure, and is how most users experience that structure.Open glossary term→ labels, they are not failing to see the menu. They have looked in the place the label suggested and not found what they expected to be there.

Once you stop looking at navigationglossary×NavigationNavigation is the system of menus, links, and cues that lets people move through a product and reach what they need. It exposes the underlying structure, and is how most users experience that structure.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.

On the NHS work, there were multiple navigationglossary×NavigationNavigation is the system of menus, links, and cues that lets people move through a product and reach what they need. It exposes the underlying structure, and is how most users experience that structure.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→ 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. Once the focus shifted away from navigation and onto structure, things started to change. Good navigation feels clear because the structure behind it makes sense. Bad navigation feels confusing because it's trying to make sense of something that doesn't.

Card sortingguide×Card SortingOpen, closed and hybrid card sorting compared: how to learn the way users group and label content, and when each variant is the right one.Open guide→ is the cheapest way to get at those questions, and its value is mostly in the disagreements. Where participants group things identically, the structure is uncontroversial. Where they split, you have found a genuine ambiguity that no amount of labellingglossary×LabellingLabelling is the practice of naming content, categories, and interface elements in a way that is clear and meaningful to users. It directly affects how users understand and navigate a product.Open glossary term→ will resolve on its own.