Skip to content
UX Atlas
Plate RES·015 · Research methodGrid G2 · Rev. 2026-08-14

Information Architecture

Organising, labelling and structuring content so people can find it, which determines navigation rather than following from it.

Research methodCraft conventionAdvanced

Definition

Information architecture is the structural design of shared information environments. It covers organisation schemes, labelling systems, navigation and search, and it is the layer beneath every findability problem.

Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.

On this plate
  1. 1Definition
  2. 2Organisation schemes
  3. 3Principles that hold up
  4. 4Working through a structure
  5. 5In practice
  6. 6Commonly confused with
  7. 7Local chart
  8. 8Sources
  9. 9Continue from here

Reach for this when

  • Structuring a product or content set.
  • Users cannot find things.
  • Planning for a growing content library.
  • Search is carrying traffic that navigation should be carrying.

Common mistakes

  • Structure mirroring internal teams.
  • Deep hierarchies.
  • Labels agreed in a workshop rather than tested.
  • Mirroring the internal team structure, which is invisible to the reader and changes twice a year.

Organisation schemes

SchemeGood forWeakness
AlphabeticalKnown-item lookup, glossariesUseless if the user does not know the name.
ChronologicalNews, activity, versionsOnly works when time is the relevant dimension.
TopicalMost content sitesBoundaries between topics are contested.
Task-basedApplications and servicesRequires knowing the tasks, which requires research.
Audience-basedMulti-segment productsUsers often do not know which audience they are.
FacetedLarge cataloguesRequires clean, complete structured metadata.

Principles that hold up

  • Structure from user vocabulary and tasks, not from the organisation chart.
  • Breadth generally beats depth. Every additional level is another decision and another chance to go wrong.
  • One item can legitimately live in several places, provided the URL is canonical and consistent.
  • Labels are the interface to the structure. Test them separately from the design.
  • Plan for growth. A structure that only fits today's content will be violated within a year.

Working through a structure

  1. 1

    Inventory what exists

    Every page, document and setting, with an owner and a last-touched date. Most structural problems are partly a volume problem nobody has measured.

  2. 2

    Settle the vocabulary

    One name per concept, chosen from the reader's language, written down where the team and the content both use it.

  3. 3

    Group with users, not in a workshop

    Card sorting for the proposal. Internal grouping produces the organisation chart with different labels.

  4. 4

    Test the structure before it is designed

    Tree testing on text alone, so a good layout cannot cover for a bad hierarchy.

  5. 5

    Plan the redirects

    A structure change that breaks existing links and search results has moved the problem rather than fixed it.

In practice

  1. i.

    The same thing, three names

    Vocabulary

    Account, profile and settings each appeared in the navigation, and each led somewhere a reasonable person would have expected the other two to go. No amount of menu design would have resolved that, because the problem was that nobody had decided what the three words meant.

Commonly confused with

Close neighbours that get substituted for each other. The difference is stated first, then the condition that picks one over the other.

vs.

Navigation

Pattern

The controls that expose a structure: menus, tabs, breadcrumbs, search.

Key difference

Information architecture is the structure: what exists, how it is grouped and what it is called. Navigation is one view onto that structure. A good menu cannot rescue a bad structure.

Use Information Architecture when

  • Things are in the wrong place, not merely hard to reach.
  • The same concept is called three names in three areas.
  • The fix changes what exists, not how it is displayed.

Use Navigation when

  • The structure is sound but people cannot move through it.
  • The question is which pattern suits the depth and the device.
  • The fix is presentation, hierarchy or persistence of the controls.

Learn about Navigation

Local chart

RES·015 · Region IV · Grid G2

This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.

Match Between System and the Real WorldHEUR·002 · PRINCIPLES BEHIND THISMiller's LawLAW·004 · PRINCIPLES BEHIND THISSerial Position EffectLAW·008 · PRINCIPLES BEHIND THISMental ModelsMOD·001 · PRINCIPLES BEHIND THISPareto PrinciplePRIN·002 · PRINCIPLES BEHIND THISCognitive LoadPSY·001 · PRINCIPLES BEHIND THISConfluenceTOOL·045 · OFTEN USED WITHOptimal WorkshopTOOL·021 · OFTEN USED WITHNavigationPAT·001 · COMMONLY CONFUSED WITHFixing a Search That Returned NothingCASE·006 · PRACTICAL EXAMPLECanonical URLTERM·130 · SHORT DEFINITIONFindabilityTERM·014 · SHORT DEFINITION

Sources

Where a source establishes something narrower than the popular reading of it, the note says so.

  1. [1]

    Information Architecture for the World Wide Web

    L. Rosenfeld, P. Morville and J. Arango, O'Reilly, 1998, fourth edition 2015

Continue from here

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Applies when you are designing

A Search ExperienceNavigation

Principles behind this

The reasoning this solution is an application of.

Often used with

These usually appear in the same screen or the same decision.

Practical example

A worked decision where this was the deciding factor.

Short definition

The one-paragraph version, for when that is all you need.

Related concept

Connected closely enough to change how you apply this.