Information Architecture
How do you structure concepts so people find what they need without thinking about structure?
Information architecture (IA) is the discipline of organizing, labeling, and connecting content so that users can find information and complete tasks. It's the invisible structure that makes navigation feel effortless—or frustrating.
"Making sense of any mess requires understanding the mess from the perspective of those who live in it." — Abby Covert
The Core Insight
IA is not about where YOU put things—it's about where READERS look for them.
Structure should mirror how people think about a domain, not how organizations are built. The test isn't "does this make sense to me?" but "can someone new find what they need in 3 clicks?"
The Tight Five IA Loop
Apply the Tight Five lens to every content area:
| Step | IA Question | Tight Five Position |
|---|---|---|
| 1. BOUNDARIES | What's in scope? What's out? | Problem-Purpose: Why does this section exist? |
| 2. INTENT | Who is this for? What do they need? | Principles: What truths guide organization? |
| 3. STRUCTURE | How do concepts relate hierarchically? | Platform: What do we control? |
| 4. CONNECTIONS | What cross-links reveal relationships? | Perspective: What do we see others don't? |
| 5. VALIDATE | Does structure serve reader goals? | Performance: How do we know it's working? |
The Hierarchy
Content organizes into three levels maximum:
PILLAR (Hub)
├── CLUSTER (Category)
│ └── DETAIL (Specific concept)
Rules:
- 3-7 items at each level (cognitive load limits)
- No more than 3 levels deep (2-3 clicks to anywhere)
- Each page should be understandable independently
- Names should signal what's inside (information scent)
Progressive Disclosure
Structure content for different reader types:
| Level | Purpose | Audience |
|---|---|---|
| Level 1 | Core concept (above fold) | Everyone — "What is this?" |
| Level 2 | Practical application (mid-page) | Practitioners — "How do I use this?" |
| Level 3 | Deep theory (expandable/linked) | Experts — "Why does this work?" |
| Level 4 | Edge cases (separate page) | Specialists — "What about X?" |
Novices read Level 1-2. Experts jump to Level 3-4. Both get what they need.
The Three Link Types
Every page needs explicit connections:
| Type | Direction | Purpose |
|---|---|---|
| Hierarchical | Parent ↔ Child | Navigation structure |
| Sibling | Peer ↔ Peer | Related concepts |
| Bridge | Cross-cutting | Unexpected connections |
Validation: Every page should have ≥1 inbound and ≥1 outbound link. Orphan pages are bugs.
Quality Gates
Before shipping new structure, verify:
- 3-Click Test: Can users reach any concept in 3 clicks from index?
- Reverse Test: Starting from any page, can users understand where they are?
- Search Test: Are key terms findable via site search?
- Link Audit: Does every page have ≥1 inbound and ≥1 outbound link?
- Mental Model Test: Does structure match how practitioners think about domain?
Anti-Patterns
| Anti-Pattern | Problem | Fix |
|---|---|---|
| Org-Chart Navigation | Structure mirrors teams, not user goals | Reorganize around user tasks |
| Orphan Pages | Pages with no inbound links | Add to relevant index |
| Dead Ends | Pages with no outbound links | Add "Context" section |
| Taxonomy Confusion | Same concept, different names | Enforce Naming Standards |
| False Hierarchy | > 3 levels deep | Flatten or elevate |
| Kitchen Sink Index | Lists everything without guidance | Curate 3-7 primary paths |
Hub Page Pattern
When creating a central hub (homepage, section index):
# [System Name]
[One sentence: What is this + Why it matters]
## Start Here
[Orientation by goal — where to begin based on what you want]
| If you want to... | Start with... |
|-------------------|---------------|
| [Goal 1] | [Path 1] |
| [Goal 2] | [Path 2] |
## The Framework
[Visual or conceptual map of how pieces fit]
## Deep Dives
[Curated list of 3-7 primary concepts]
## Context
[Bridge links to related sections]
Frameworks Referenced
Abby Covert's Process
- Identify the mess — What's confusing?
- State your intent — What's the goal?
- Face reality — What exists now?
- Choose a direction — What structure?
- Measure the distance — How far to go?
- Play with structure — Test options
- Prepare to adjust — Iterate
Dan Klyn's BASIC
- Boundaries — What's in scope?
- Attributes — What distinguishes parts?
- Structures — How do parts connect?
- Invariants — What doesn't change?
- Cycles — What patterns repeat?
Context
- Naming Standards — Canonical terminology
- Unixification — Composability principle
- Matrix Thinking — Visual organization
- Process Optimisation — Improvement loop
- Thought Audit — Self-assessment
Mantras
Structure mirrors how readers think, not how organizations are built.
If users have to search, navigation has failed.
Every orphan page is a bug.
3 clicks or less to anywhere.