Information Architecture
Structure content and navigation so users find what they need without thinking - using card sorting, tree testing, and hierarchy principles.
skill: Information Architecture category: Design tags: [Information Architecture, Navigation, Sitemap, Card Sorting, UX] readingTime: 5
Good IA is invisible - users find what they need without thinking about the structure. Bad IA is the cause of 'I can never find anything in this app'. IA work comes before wireframes; trying to retrofit navigation onto existing content leads to compromise. Structure follows content, not the reverse.
Workflow
- Inventory and audit existing contentYou can't organize what you haven't catalogued. A content inventory surfaces duplicates, outdated pages, and gaps in coverage.
- Run card sorting to understand user mental modelsCard sorting reveals how users naturally group and label content - building the IA around user mental models reduces the need for search.
- Design the hierarchyA 3-level hierarchy (global nav → section → page) covers most products. Deeper hierarchies lose users; shallower hierarchies produce overcrowded menus.
- Validate with tree testingTree testing shows whether users can find items in your proposed hierarchy - without visual design biasing the results.
- Create a sitemap and navigation specA sitemap documents the agreed structure for designers, developers, and content teams - the single source of truth for navigation.
Output Format
IA deliverable: content inventory, card sorting insights, validated hierarchy, sitemap, and navigation spec.
IA Package:
├── Content inventory (spreadsheet)
├── Card sort results (similarity matrix + themes)
├── Proposed hierarchy (sitemap diagram)
├── Tree test results (success rates per task)
└── Navigation spec (global, section, utility nav patterns)Examples
Input
Output
Edge Cases & Gotchas
- Search as a crutch for bad IA - Adding search doesn't fix bad navigation - users use search when navigation fails. Fix the IA; add search as a supplement for power users.
- Overcrowded global navigation - > 7 items in global nav overwhelms users and dilutes each item's visibility. Promote only the top-level destinations; use sub-navigation for depth.
- Mobile navigation collapse - Desktop 7-item nav becomes a hamburger menu on mobile - losing all wayfinding. Design mobile navigation patterns (bottom nav bar, progressive disclosure) separately.
- Cross-linking between sections - Items that belong in multiple categories (product + support documentation) are common. Use content aliases, tags, or 'related content' links rather than duplicating pages.
When to Break These Rules
- Use full-text search as the primary navigation for knowledge bases and documentation - users arrive with a specific question, not a browsing mindset.
- Don't run card sorting if content is extremely novel (users have no mental model) - use competitive analysis and domain expert interviews instead.
Reference Files
https://www.optimalworkshop.com/learn/https://www.nngroup.com/articles/ia-vs-navigation/