Skip to content
NewTemplates & toolkits are on the way — join the waitlist
Hecham Gazhi

UX Design · Lesson 07 / 13

Information architecture

How to organise, label and connect content so people can find what they need: organisation schemes, navigation systems, labelling, sitemaps, card sorting and tree testing.

5 min read · 5 quiz questions

What is information architecture?

Information architecture (IA) is the practice of organising, structuring and labelling content so people can understand where they are, find what they need and know what to do next.

Every product has an IA, whether it was designed or not. A website's menu, an app's tab bar, a settings screen and a help centre's categories are all IA. When IA is poor, people get lost, use search for everything, or give up and contact support.

Good IA matches the mental model of users — how they expect information to be organised — rather than the company's internal structure or database tables.

Common mistake: Organising navigation by the company's org chart: "Retail Division", "Corporate Services", "Digital Solutions". Customers don't know or care how your company is structured.

The building blocks of IA

Louis Rosenfeld and Peter Morville, in the classic book on the subject, describe four main systems:

SystemWhat it doesExamples
OrganisationHow content is grouped and categorisedProducts grouped by category, articles by topic
LabellingHow things are named"Pricing", "My orders", "Help"
NavigationHow people move through the contentMain menu, tabs, breadcrumbs, footer links
SearchHow people look for content directlySearch bar, filters, autocomplete

Organisation schemes

Exact schemes

Clear, objective divisions: alphabetical (a glossary), chronological (news, order history), geographical (store locator). Easy to use when people know exactly what they're looking for.

Ambiguous schemes

Subjective divisions that require judgment: by topic (Design, Marketing), by task (Send money, Pay bills), by audience (Students, Teachers). Harder to design but often more useful, because people usually browse with a goal rather than an exact name.

Hybrid schemes

Most real products mix schemes — for example, an e-commerce site organised by category, with filters by price and brand. Mix carefully so each level of the hierarchy uses one clear logic.

Hierarchy: broad vs deep

A broad (flat) hierarchy has many options at each level and few levels. A deep hierarchy has fewer options but more levels. Neither is always right.

  • Too deep: people must click through many levels and lose track of where they are.
  • Too broad: people are overwhelmed by choice at each level.
  • In general, moderately broad and shallow structures with clear groups perform well, especially when the options are well-labelled.

Labelling

Labels are the words on navigation, buttons and headings. They're small but decisive: a perfect structure with confusing labels still fails.

Do

  • Use the words your users use (learn them from research and search logs).
  • Be specific: "Shipping & returns" beats "Information".
  • Keep labels consistent across navigation, pages and buttons.
  • Front-load the important word: "Billing settings", not "Settings for billing".

Don't

  • Use internal jargon or product code names.
  • Use clever or vague labels: "Explore", "Solutions", "Discover more".
  • Use different words for the same thing in different places.
  • Create overlapping categories ("Resources" and "Learning").

Navigation systems

TypePurposeExamples
Global navigationPresent on every page; the main sectionsTop menu bar, app tab bar
Local navigationMoves within a sectionSidebar with sub-pages
Contextual navigationLinks related to the current content"Related articles", links in text
Utility navigationTools not part of the content hierarchyAccount, language switcher, cart
BreadcrumbsShows where you are in the hierarchyHome › Shoes › Running
Footer navigationSecondary links and legal pagesAbout, Careers, Privacy

Give people more than one way to find things: browse through navigation, search directly, and follow contextual links. Different people — and the same person on different days — prefer different paths.

Card sorting

Card sorting reveals how people group and label content. You give participants cards with content items ("Change password", "Download invoice", "Delivery times") and ask them to sort them.

Open card sort

Participants create their own groups and name them. Use it early, to discover users' mental models and the words they use.

Closed card sort

You provide the categories; participants place cards into them. Use it to check whether an existing or proposed structure makes sense.

Hybrid card sort

Participants use your categories but can create new ones if nothing fits.

  • Use 30–60 cards that represent real content.
  • Aim for roughly 15–30 participants for useful patterns in an online study.
  • Analyse which cards are often grouped together (a similarity matrix) and which labels people use.

Tree testing

Tree testing (sometimes called reverse card sorting) checks whether people can find things in a proposed structure. Participants see only a text version of the navigation — the "tree" — and are given tasks like "Where would you go to change your delivery address?"

Because there is no visual design, the test isolates the structure and labels. Key metrics are success rate (did they end in the right place?), directness (did they get there without backtracking?) and time.

Exampletext
Account
├── Profile
├── Orders
│   ├── Track an order
│   └── Returns
├── Addresses        ← correct answer for "change delivery address"
└── Payment methods
Help
├── Shipping
└── Contact us

Task: "You've moved house. Where would you update where your orders are sent?"

Sitemaps

A sitemap (for UX, not the XML file for search engines) is a diagram of all the pages or screens and how they are grouped and connected. It is the blueprint of the IA, created before wireframes, and it helps the team agree on scope.

  1. 1Do a content inventory: list all existing content and its purpose.
  2. 2Remove, merge or rewrite outdated and duplicate content.
  3. 3Run a card sort to learn how users group the remaining content.
  4. 4Draft the sitemap with clear labels.
  5. 5Validate it with a tree test, then iterate.

Key takeaways

  • IA is how content is organised, labelled, navigated and searched.
  • Match users' mental models, not the company's org chart.
  • Labels should use the users' words, be specific and stay consistent.
  • Provide several ways to find content: navigation, search and contextual links.
  • Use card sorting to discover structure and tree testing to validate it.

Exercise

Restructure a navigation

  1. Pick a website with a confusing menu (a government service, a university, a large company).
  2. List 30 pieces of content from it on cards.
  3. Ask two friends to do an open card sort and name their groups.
  4. Draft a new sitemap based on their groups and labels.
  5. Write three tree-testing tasks to check your new structure.

Test yourself

Information architecture quiz

5 questions. Score 70% or more to complete the lesson.

  1. 1.Good information architecture should follow…
  2. 2.In an open card sort, who names the categories?
  3. 3.What does tree testing evaluate?
  4. 4.Which is the best navigation label?
  5. 5.Breadcrumbs mainly help people…