Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jpoindexter/information-architecture-and-navigation
Reference-grade guide to information architecture and navigation — organization/labeling/navigation/search systems, organization schemes, taxonomy and hierarchy depth-vs-breadth, every nav pattern per device, wayfinding, search UX, and the research methods (card sorting, tree testing, first-click) that prove findability.
Passed 20 of 22 test cases with the skill, and 21 of 22 without it.
0 fixed20 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
The instructions your model reads when the skill loads.
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.
| 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.
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.
Rule: the navigation should read like the user's to-do list, not your team's directory.
Rosenfeld/Morville split organization schemes into two families:
Exact (objective) — unambiguous, mutually exclusive buckets. Easy to maintain, great for known-item lookup, useless when the user doesn't know the exact term.
| Scheme | Use when | Example |
|---|---|---|
| Alphabetical | User knows the name | A–Z staff directory, glossary, country picker |
| Chronological | Time is the key axis | Changelog, news archive, order history |
| Geographical | Place is the key axis | Store locator, regional pricing |
Ambiguous (subjective) — group by meaning. Harder to design (judgment calls, overlap), but far more useful for exploratory browsing because users rarely know the exact term.
test cases passed, vs 21 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.