information-architecture-and-navigation
Information Architecture & Navigation
Information architecture (IA) is the art and science of organizing, labeling, and structuring content so people can find what they need and understand where they are. Rosenfeld, Morville & Arango (Information Architecture for the Web and Beyond, the "polar bear book") frame IA as four interlocking systems: organization, labeling, navigation, and search. Navigation is the visible surface of the IA; the structure underneath is what makes navigation possible. A beautiful nav bar over a broken taxonomy is lipstick on a maze.
Findability is the goal. As Morville puts it: "What you can't find, you can't use." If users can't locate a feature, it does not functionally exist. IA is upstream of UI — fix the structure before you style the menu.
1. The four IA systems
| System | Question it answers | Artifacts |
|---|---|---|
| Organization | How is content grouped and structured? | Sitemap, taxonomy, content model, hierarchy |
| Labeling | What do we call things? | Label set, controlled vocabulary, nav labels, microcopy |
| Navigation | How do users move through the structure? | Global/local/contextual nav, breadcrumbs, filters |
| Search | How do users find by query, not browse? | Search box, autocomplete, results page, facets, scoping |
These are not independent. A category that's hard to label is usually a sign the organization is wrong. Search that returns junk is usually a labeling/metadata problem, not a search-algorithm problem.
2. Mental models — match the user's vocabulary, not your org chart
A mental model is the user's internal map of how your domain works. IA succeeds when your structure matches that map and fails when it mirrors your internal team boundaries, database tables, or executive reporting lines.