practiceExperience & interface

Information Architecture

Information architecture organizes and connects content so people can understand what exists, where to find it, and what to do next.

Download Markdown (.md)

01What it means

Information architecture (IA) is the deliberate design of structures for information-rich products and services. It coordinates organization, labeling, navigation, search, and relationships between content so that users can build a workable mental model of the system. IA is not merely a sitemap: it includes the rules and concepts that make the sitemap, menus, search results, and cross-links coherent.[1][2][3]

Coherent information system Findability emerges from structures working together
Information architecture
Organization
How information is grouped
Labels
How concepts are named
Navigation
How people move
Search
How people retrieve
Relationships
How objects connect
Governance
How structure evolves

A sitemap shows only part of the system.

02Why it matters

Good IA lowers the effort required to locate, interpret, and act on information. It also gives product teams a shared model for adding content without inventing a new structure each time. When IA is weak, polished screens still feel confusing because categories overlap, labels hide meaning, and users cannot predict where a path will lead.

03When to use it

Use IA when creating or redesigning a content-heavy website, application, intranet, documentation set, marketplace, or service. Revisit it when content has grown organically, search logs reveal repeated failures, navigation no longer scales, or teams disagree about where new material belongs.

04How it works

  1. Define the audiences, priority tasks, content scope, and business constraints before drawing a hierarchy.
  2. Inventory representative content and identify important objects, attributes, relationships, and lifecycle states.
  3. Develop organization, labeling, navigation, and search models together rather than treating each as an isolated layer.
  4. Test findability and comprehension with users through methods such as card sorting, tree testing, and task-based usability sessions.
  5. Establish governance rules and measures so the structure can evolve without losing coherence.

05A practical example

Example

A public health portal groups information around user needs such as preventing illness, getting care, and managing a condition. Condition pages use consistent labels, expose related services, and feed structured terms into search. A user can browse by need or search by familiar language without needing to understand the agency chart.

06Where it breaks

IA cannot compensate for missing, inaccurate, or poorly written content, and no single hierarchy will match every user’s mental model. Research samples can overrepresent confident participants, while organizational politics may distort categories. Treat the architecture as a tested hypothesis and maintain it as content, users, and services change.

Common mistakes

  • Equating IA with a sitemap or navigation menu.
  • Mirroring internal departments instead of user goals and concepts.
  • Finalizing categories and labels without testing realistic retrieval tasks.

07Sources

  1. What Is Information Architecture?Information Architecture Institute · Institutional overviewWhat Is Information Architecture?
  2. Information Architecture: Study GuideNielsen Norman Group · Research-based guidanceInformation Architecture: Study Guide
  3. The Difference Between Information Architecture and NavigationNielsen Norman Group · Research-based guidanceThe Difference Between Information Architecture and Navigation
View saved topics

Start typing to search titles, definitions, categories, and frameworks.