Knowledge Concepts
Information architecture is the practice of organizing, structuring, and labeling content so people can find what they need. It determines the categories, navigation, and hierarchy of any information system — from websites to note collections.
Information architecture (IA) is the practice of organizing, structuring, and labeling information so people can find what they need efficiently. It defines the categories, hierarchy, navigation, and relationships in any information system — a website, an app, a knowledge base, or a personal note collection. Good information architecture is invisible: users find what they need without noticing the structure. Poor IA is painfully visible: users can't find things, give up, or take wrong paths.
Information architecture is the blueprint for any organized body of information. The categories you choose, the labels you apply, and the hierarchy you create are all IA decisions — even in a personal note-taking system.
The term "information architecture" was popularized by Richard Saul Wurman, an architect and designer, in the 1970s. Wurman used it to describe the design of information for human understanding — the application of architectural thinking (structure, organization, clarity) to information rather than physical space.
The discipline was formalized for digital contexts by Peter Morville and Louis Rosenfeld in "Information Architecture for the World Wide Web" (1998), which became the foundational text. The "polar bear book" (named for its cover illustration) articulated the core components of IA and established it as a professional discipline within user experience design.
The discipline has expanded beyond web design to encompass any context where information needs to be organized for findability: digital products, enterprise software, knowledge management systems, and personal information systems.
Peter Morville identifies eight components of IA. The four most practically relevant:
Organization systems: How information is categorized and structured. The hierarchy of categories and subcategories. Whether the structure is hierarchical (tree-like, parent-child), sequential (step-by-step), or network (linked nodes). Organization systems determine which "bucket" any piece of information belongs to.
Labeling systems: What you call things. The words used for categories, navigation items, and headings. Labeling affects findability dramatically: users search and navigate using their own vocabulary. If labels match user vocabulary, content is found; if not, it's invisible even when present.
Navigation systems: How users move through information — menus, breadcrumbs, search, links, filters, pagination. Navigation systems translate the underlying organization into user-facing pathways.
Search systems: When users know what they're looking for but can't find it through navigation, search is the fallback. Search system design includes what's indexed, how results are ranked, and what search operators are available.
A product team creates an internal knowledge base. Their initial structure reflects how they produce information rather than how people find it:
Knowledge Base/
├── 2023/
│ ├── Q1 Documents/
│ └── Q2 Documents/
├── Marketing Team/
│ ├── Campaigns/
│ └── Reports/
└── Product Team/
├── Specs/
└── Research/
The IA problem: New employees search "how to request a budget" — they don't know whether this is in Marketing Team/Campaigns or Product Team/Specs or somewhere else. Senior employees search for a Q2 2023 market analysis — they don't remember which team created it.
Better information architecture: Restructured around how users look for information, not how information is produced:
Knowledge Base/
├── Processes/
│ ├── Budget requests
│ ├── Hiring procedures
│ └── Client onboarding
├── Research & Analysis/
│ ├── Market research
│ ├── Competitive analysis
│ └── User research
├── Projects/
│ ├── Active
│ └── Archived
└── Policies/
├── HR policies
└── Finance policies
Now "budget requests" is findable under Processes. Market analyses are in Research & Analysis regardless of which team created them. The organizational structure is user-centric, not producer-centric.
Information architecture isn't only for websites and enterprise software. The same principles apply to personal note collections, research databases, and saved content:
Your folder structure is a hierarchy: Every folder is an IA decision. When you create a folder called "Research" inside a folder called "Work," you're making an IA choice about where that information lives and how you'll navigate to it.
Your tags and labels are a labeling system: The tags you apply to notes and saved content are an IA decision. Using both "AI" and "Artificial Intelligence" as separate tags creates fragmentation; choosing one consistently is IA discipline.
Your categories should reflect how you search: The most common IA mistake in personal systems: organizing by how information arrives rather than by how you'll need it. Organizing your notes by source (articles, books, meeting notes) vs. by topic (marketing strategy, product development, personal projects) are different IA choices — and "by topic" usually wins for findability.
Step 1 — Identify your most common retrieval needs. Before creating structure: ask "what are the 10 most common things I search for?" The answer dictates your categories. Your IA should optimize for these use cases.
Step 2 — Use user vocabulary for labels, not producer vocabulary. In a personal system, you're both producer and user. Future-you will search using terms that make sense to you then — not necessarily the terms you used when organizing. Label with clear, natural language; avoid jargon and abbreviations that might not come to mind later.
Step 3 — Create a flat hierarchy. Deep hierarchies (more than 3 levels of nesting) create navigation problems. If you need to click through 4 folders to find something: it's too deep. Shallow, broad structures + good search outperform deep hierarchies.
Step 4 — Use consistent tags across systems. If you save content to WebSnips with tags and also take notes in Obsidian: use the same tag vocabulary in both. Consistency across systems means cross-system search works better.
Step 5 — Maintain, don't just build. IA isn't a one-time decision. As information accumulates, categories become overloaded or outdated. Regular maintenance — reviewing whether your categories still reflect your actual use — keeps the architecture useful.
Organizing by source, not topic: "Articles," "Books," "Meeting Notes" as top-level categories means any given topic is split across multiple locations. "Marketing Strategy," "Product Development," "Operations" as categories keeps all information about a topic together.
Too many categories: A flat list of 50 categories is just as hard to navigate as no categories. Aim for 5-10 top-level categories that can be searched within.
Inconsistent labeling: Using "Research" in one place and "Studies" in another, or "client" and "customer" interchangeably, fragments search results and navigation.
Producer-centric hierarchy: Organizing by who created the information or when they created it, rather than what it's about and how you'll need it.
Taxonomy vs. folksonomy: Controlled vocabulary (taxonomy) vs. user-generated tags (folksonomy) — two approaches to the labeling component of information architecture.
Metadata: The structured descriptive information attached to content — the implementation mechanism for IA labels and categories.
Knowledge base: An information system where IA decisions directly determine whether the knowledge base is usable or not.
Is information architecture the same as UX design? IA is one component of UX design — the structural and organizational layer. UX design also includes visual design, interaction design, and usability. An IA can be done well while visual design is poor, and vice versa. In practice, IA and UX overlap heavily, particularly for content-heavy products.
How much structure does a personal note collection need? Enough to find things, not more. The right amount depends on your collection size and retrieval habits. A collection of 50 notes with minimal structure is fine; a collection of 5,000 notes with no structure creates real findability problems. As a rough guide: when you regularly can't find things you know exist, you need more IA.
Does good search make IA unnecessary? No. Search complements IA; it doesn't replace it. Search finds things you know exist; IA helps you discover things you didn't know were there. Search without good labels and metadata produces poor results. Search and IA work together.
Information architecture is the hidden determinant of whether an information system is useful or frustrating. The same information, organized differently, produces dramatically different findability. For personal knowledge systems, this means: think before you organize. Ask "how will future-me search for this?" before creating a folder or applying a tag. The categories and labels you choose at capture time determine whether your accumulated knowledge is accessible or buried.
More WebSnips articles that pair well with this topic.
Intermediate packets are small, discrete, reusable units of work — an outline, a research summary, a slide deck draft, a set of notes — that can be saved and reused across future projects rather than starting from scratch each time.
A bullet journal (BuJo) is an analog organization system created by Ryder Carroll using a dot-grid notebook: rapid logging with bullet symbols, collections (logs, trackers, lists), and migration (intentional task review). It combines daily planner, to-do list, diary, and habit tracker in one notebook.
A KWL chart is a three-column learning organizer: K (What I Know), W (What I Want to Know), L (What I Learned). It activates prior knowledge before learning, sets specific goals, and documents what you actually learned — making the learning process active and self-directed.