Skip to content
InsideUX Design

UX glossary

Information Architecture

Information architecture describes how the content of a website or app is structured and labeled. It helps people find what they’re looking for and understand where they are.

Imagine you’re on your city council’s website trying to find out how to renew your passport. The menu offers “Directorate II”, “Citizen Services Division” and “Council News”. You click around, end up on the library’s opening hours and eventually give up. All the information is there. It’s just organized the way the administration thinks internally, not the way people search.

Explained simply

Information architecture (IA for short) describes how the content of a website or app is structured and labeled so people can find what they’re looking for and understand where they are. Think of a supermarket: someone decides that pasta sits next to the tomato sauce, which aisles exist and what the signs above them say. That invisible order is the information architecture. The signs themselves are closer to what navigation is.

The term was coined by architect and designer Richard Saul Wurman, who says he introduced it in 1976 at the national convention of the American Institute of Architects. The field became widely known on the web mainly through the book by Louis Rosenfeld and Peter Morville, first published in 1998 and now available as “Information Architecture: For the Web and Beyond” (with Jorge Arango).

What information architecture is made of

Rosenfeld and Morville distinguish four systems that work together: the organization system (what logic is used for grouping, such as topic, audience or task?), the labeling system (which words appear on menu items and links?), the navigation system (how do people move through the structure?) and the search system (how do they find content by searching?).

It’s important to tell IA apart from navigation. The Nielsen Norman Group describes IA as a foundation that isn’t visible in the interface at all. It’s documented in spreadsheets and diagrams. Menus, breadcrumbs or filters are the visible elements built on top of that structure. So the rule is: define the IA first, then design the navigation. You can read more in An Introduction to Information Architecture.

An example

Back to the city council. Before, the website mirrors the org chart: departments, directorates, divisions. The team runs a card sort with local residents. Almost everyone groups content by life events such as “Moving house”, “ID and passport” or “Family”. Afterwards, the website is organized around these needs, and the departments only appear as the responsible office on the relevant pages. A follow-up tree test confirms that participants now find the passport information much faster.

Why it matters

Good visual design can hardly rescue a weak IA. When labels are unclear or content sits in unexpected places, people search longer, give up or call support. Good IA follows the user’s mental model, meaning their idea of where something ought to be.

In practice

  • Think in tasks, not departments. For every menu item, ask what someone wants to get done with it. Internal names rarely belong in the menu.
  • Collect first, then organize. Make a content inventory of all pages and features before you create categories. Otherwise you only organize what happens to come to mind.
  • Test the structure without design. Card sorting gives you ideas for the structure, tree testing checks it. Both are quick and save you from costly rework later.

Related terms

Card Sorting, Tree Testing, Mental Model, Progressive Disclosure

Sources

More terms

Full glossary