Information Architecture

The grocery store that nobody could navigate

In 2012, a major US grocery chain remodeled 1,500 stores. They reorganized products by brand instead of by category. All Kraft products together. All Nestle products together. All General Mills products together. The executives loved it — clean, organized, partnership-friendly.

Customers hated it. Sales dropped 25% in the first quarter. People wandered the aisles looking for peanut butter, which was no longer in a "spreads" aisle — it was scattered across four different brand sections. Shoppers left with half-filled carts, frustrated and confused.

The company reversed the changes within six months. The problem was not the products. The problem was the information architecture — how things were organized did not match how people think.

This is what Information Architecture (IA) does for digital products. It determines where things go so people can find them. Get it wrong, and your beautifully designed app becomes a grocery store nobody can navigate.

What is Information Architecture?

Information Architecture is the practice of organizing, structuring, and labeling content so that people can find and understand it. Think of it as the blueprint of a building — you never see it directly, but it determines whether you can find the bathroom.

IA answers three fundamental questions:

1. Where am I? — Can the user tell where they are in the product at any moment?
2. What is here? — Can the user understand what content and options are available on the current page?
3. Where can I go? — Can the user figure out how to get to what they need from here?

Mental models — how users think things should work

Before you organize anything, you need to understand how your users expect things to be organized. This expectation is called a mental model.

A mental model is a user's internal map of how something works. When someone uses your product for the first time, they do not start with a blank slate. They carry expectations from every other product they have used.

Example: When you visit a new e-commerce site, you expect:

• A search bar at the top
• Products organized by categories on the left
• A shopping cart icon in the top right
• A checkout process that goes: cart, shipping, payment, confirmation

If a site puts the search bar at the bottom, categories on the right, and the cart icon in the footer, it might be logically valid — but it violates your mental model. You will feel lost.

There Are No Dumb Questions

"What if our product is genuinely new? Users have no mental model for it."

Even novel products borrow from familiar patterns. When the iPhone launched, it used a grid of app icons — borrowing the mental model of a desktop with folders. When Slack launched, it looked like a chat app because people already understood chat. If your product is truly novel, lean on the closest existing mental model and introduce new concepts gradually.

"Should I always follow conventions? What about innovation?"

Follow conventions for foundational IA (navigation, settings, search). Innovate on the unique value of your product. Nobody ever won a design award for putting the search bar in a creative location — but plenty of products have failed because of it.

Card sorting — let users organize for you

Card sorting is the most important IA research technique. Instead of guessing how to organize your content, you let users do it.

How it works

1. Write each piece of content or feature on a separate card (physical or digital)
2. Give users the cards and ask them to sort them into groups that make sense to them
3. Ask them to name each group
4. Look for patterns across multiple participants

Two types of card sorting

Example: A team building a project management tool did an open card sort with 20 features. They expected users to group features by function: "Planning," "Tracking," "Reporting." Instead, users grouped them by workflow stage: "Before the project starts," "While the project is running," "After the project ends." This completely changed the navigation structure.

Site maps — the blueprint of your product

A site map is a visual diagram that shows every page in your product and how they relate to each other. It is the deliverable that comes after card sorting and before wireframing.

Rules for good site maps

• Three-click rule: Users should reach any content within 3 clicks from the homepage. This is not a hard law, but it is a useful constraint.
• 7 plus or minus 2: People can hold 5-9 items in working memory. Keep top-level navigation to 5-7 items.
• Breadth over depth: A flat structure (many items, few levels) is easier to navigate than a deep structure (few items, many levels). Users prefer scanning a list of 7 options to clicking through 4 levels of 2 options each.

Navigation patterns

Navigation is how users move through your site map. The right pattern depends on your content type.

There Are No Dumb Questions

"My stakeholder wants 12 items in the top navigation. What do I do?"

Show them the research. Miller's Law (7 plus or minus 2) applies to navigation. When users see 12 top-level items, they cannot scan them quickly, so they fall back to search — which means your navigation has failed. Group related items under 5-7 parent categories using dropdowns, and put the remaining items in the footer or secondary navigation.

Labeling — the words matter more than the structure

The best site map in the world fails if the labels are confusing. IA labeling follows one rule: use the user's words, not your company's words.

Key takeaways

• If users cannot find it, it does not exist — information architecture determines whether people can navigate your product
• Mental models are the expectations users bring from other products — your IA must match how users think, not how your org chart looks
• Card sorting lets users organize your content for you — open sorts reveal natural categories, closed sorts validate existing ones
• Site maps visualize page hierarchy — aim for breadth over depth, 5-7 top-level items, and 3 clicks to any content
• Navigation patterns (top bar, sidebar, tabs, hamburger, bottom bar, breadcrumbs) each suit different content types
• Labels must use user language — test with tree testing to verify people can find what they need