IA
Why navigation is not information architecture
Navigation is the surface. Information architecture is the structure underneath that actually determines whether users can find what they need.
Why reworking menus rarely fixes findability on its own, and why the real problem usually sits in how the system is organised underneath.
In short
Why reworking menus rarely fixes findability on its own, and why the real problem usually sits in how the system is organised underneath.
Why the structure underneath matters more
glossaryNavigationHow users move around a website or product.Open glossary term doesn't define how a glossarySystemA 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 glossaryRefinementRefinement is the process of preparing and clarifying backlog items before development.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 glossaryPlatformA platform is a system or environment that enables users, services, or applications to interact, build, or operate.Open glossary term where the glossaryNavigationHow users move around a website or product.Open glossary term looked perfectly reasonable at first glance. The labels made sense, the glossaryHierarchyHierarchy 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.
Key takeaway
If users cannot find things, the issue is often not the menu itself. It is how the system has been organised underneath.
What changes when you focus on architecture instead
Once you stop looking at glossaryNavigationHow 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 serviceInformation 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 glossaryNavigationHow users move around a website or product.Open glossary term glossarySystemA 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 glossaryFindabilityFindability 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.