Marcus Andrey Study
Ler em português Library

UX Foundations · Step 4 · 7 min read

Information architecture

Before people can use something, they have to find it. What information architecture is, its four parts (organising, labelling, navigation and search), how it differs from navigation design, and why it should follow people's mental models instead of the org chart.

A filing cabinet with four drawers, the four jobs of information architecture: organise, label, navigate and search. Point at a drawer and it slides out. Illustration: Marcus Andrey, drawn with Hairline (MIT, Lucas Marques).

People have to find things before they can use them. A beautiful screen is useless if nobody can reach it, and a great feature is invisible if it hides under the wrong name. Information architecture is the quiet work behind that: deciding what goes together, what each thing is called, and how people get from one place to another. Users never see it directly, but they feel it every time they find something on the first try, or give up.

What you'll be able to do after reading:

  • Explain what information architecture is, in one sentence
  • Name its four parts: organising, labelling, navigation and search
  • Tell information architecture from navigation design
  • Spot a structure built around the org chart instead of people's mental models

1. What information architecture is

The Information Architecture Institute put it simply: "Information architecture is the practice of deciding how to arrange the parts of something to be understandable" (IA Institute, What is Information Architecture?, archived page). Abby Covert's book says almost the same: IA is "the way we arrange the parts of something to make it understandable as a whole" (Covert, How to Make Sense of Any Mess, 2014).

Notice that neither definition mentions websites. A supermarket, a bus map, a recipe book and a phone's settings all have an information architecture. Somebody decided what goes where and what it's called, well or badly.


2. The four parts

1Organise

Which things belong together?

Groups, order, hierarchy
2Label

What do we call each group?

Words people already use
3Navigate

How do people move between them?

Menus, links, breadcrumbs
4Search

How do people ask for one thing?

A box, results, filters
The four parts of an information architecture, after Rosenfeld, Morville and Arango. Diagram: Marcus Andrey, CC BY 4.0.

The standard textbook, Rosenfeld, Morville and Arango's Information Architecture (4th edition, 2015), describes IA through its components: "organization, labeling, navigation, search, and metadata" (O'Reilly, Information Architecture, 4th Edition). Metadata (tags and descriptions behind the scenes) is more advanced; the first four are where beginners start.

Here they are for a fictional online plant shop:

Part The question it answers In the plant shop
Organising Which things belong together, and in what order? Group plants by where they live: indoor, outdoor, balcony
Labelling What do we call each group and link? "Easy-care plants", not "Low-maintenance SKUs"
Navigation How do people move around? A top menu with the main groups; breadcrumbs on product pages
Search How do people ask for one specific thing? A search box that understands "snake plant" and "Sansevieria"

There are only a few basic ways to organise anything. NN/g's video on the LATCH framework lists them: location, alphabet, time, category and hierarchy (NN/g, Wang, Organize Information with "LATCH", 2024). The idea comes from Richard Saul Wurman's book Information Anxiety (1989). A shop of plants by category, a list of stores by location and a news feed by time are all LATCH at work.


3. Information architecture is not navigation

IAThe structure

What exists, how it is grouped and what it is called.

Lives in lists and diagrams
NavThe way in

The menus, links and tabs people see on screen.

Lives in the interface
Information architecture is the skeleton; navigation is the part of it people can see and touch. Diagram: Marcus Andrey, CC BY 4.0.

The two get mixed up all the time. NN/g's short version: "IA is the information backbone of the site; navigation refers to those elements in the UI that allow users to reach specific information on the site" (NN/g, Cardello, The Difference Between Information Architecture (IA) and Navigation, 2014). The same article says that IA "is documented in spreadsheets and diagrams, not in wireframes", and that "IA informs UI".

In practice:

  • IA is the list of everything you have, the groups, the hierarchy and the names. You can write it on paper with no design at all.
  • Navigation design is choosing the menus, tabs, links and breadcrumbs that show that structure on a screen. See Navigation patterns.

NN/g's advice is to do a first pass at the IA before choosing navigation, because a menu picked for its looks may not fit the content you discover later.


4. Follow mental models, not the org chart

In How people think you met mental models: what people believe about how something works. A good structure matches them. A classic mistake, as Jakob Nielsen put it, is "to structure the information space based on how you view the content", which "often results in different subsites for each of your company's departments" (NN/g, Nielsen, Card Sorting: How Many Users to Test, 2004).

Customers don't know (or care) that "Returns" belongs to the logistics team and "Refunds" to finance. To them, it's one problem: "I want my money back for this pot."

Two more structural choices matter:

How do you find out people's mental model? You ask them to sort things. That's Card sorting and tree testing.


5. Common mistakes

  • Copying the company's departments into the menu.
  • Choosing the navigation style first, then squeezing the content into it.
  • Inventing clever or branded names that nobody searches for.
  • A "Miscellaneous" or "Other" group that grows every month.
  • Mixing organising rules in one list (some groups by type, some by audience, some by price).
  • Assuming search will fix a messy structure.

6. Vocabulary

Term Meaning
Information architecture (IA) How the parts of something are arranged so people can understand and find them
Organisation scheme The rule used to group things: by category, place, time, alphabet or rank
Label The word or phrase that names a group, page or link
Hierarchy Groups inside groups, like folders inside folders
Site map A diagram of the hierarchy, from the home page down
Polyhierarchy One item listed under more than one group
Findability How easily people can locate something they're looking for

7. Try it (no tools needed)

  1. Pick an app you use often (a bank, a supermarket, a streaming service).
  2. On paper, draw its main structure: the home screen at the top, the main sections below, two or three levels deep.
  3. Circle every label you didn't understand the first time, and every place where you once looked for something and it wasn't there.
  4. Write one change: a group you'd merge, split or rename, and why.

Reflection questions: Does the structure follow how you think about the task, or how the company is organised? Which organising rule (LATCH) does each section use?


8. If you already practise

  • Before a redesign, draw the current site map and the content inventory, even roughly. Most navigation debates get shorter once everyone sees the real structure.
  • Write a short list of controlled terms (one name per concept) and share it with writers and developers; inconsistent names are an IA problem, not a copy problem.
  • Watch your search logs: what people type is a free list of the words they expect in your labels.

Checklist

Learn more

Books, courses and videos to go deeper

Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Navigation patterns · Card sorting and tree testing · Content first · How people think · Users, tasks and context

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close