What is information architecture?
Information architecture (IA) is the practice of organizing and labeling content so that people can find what they're looking for and complete their tasks.
Think of a supermarket. You've never seen a map of your local store, yet you can walk in and find pasta within a minute. The store is organized into predictable aisles, each aisle has a clear sign, and related products sit next to each other. Milk lives with dairy, not with cleaning supplies.
Digital products work the same way. When the structure of a product matches the way users think about its content, people navigate without conscious effort. When it doesn't, they get lost and leave. A banking app where "transfer money" hides under "settings" is a supermarket shelving bread in the pharmacy aisle.
Information architecture happens whether you design it or not. Every product has a structure. The only question is whether it reflects the mental model of your users, or the org chart of your company.
-
keywords
- #Structure
- #Findability
- #MentalModels
The three pillars of IA
Information architecture rests on three systems: how you organize content, how you label it, and how users move through it. Get one wrong, and the other two can't save you.
Organization: how content is grouped
Organization is about deciding which structural model fits your content. There are three classic structures:
Hierarchy. A tree structure with broad categories at the top and specific items underneath: Home leads to Shop, Shop leads to Shoes, Shoes leads to Running Shoes. Hierarchies work because they match how people naturally categorize the world.
Sequence. A step-by-step path where users move in a fixed order. Checkout flows, onboarding wizards, and booking funnels are sequential. Use a sequence when the order of steps matters and skipping ahead would cause errors.
Matrix. Content users can slice in multiple ways at once. An e-commerce catalog is a matrix: the same sneaker can be found by brand, price, color, or sport. Filters and facets are the interface of a matrix.
Real products mix all three: a hierarchy for main navigation, a matrix for browsing products, a sequence for checkout.
Labeling: what things are called
A perfect structure fails if users don't understand the words on it. Labels are the signs above the aisles, and they must speak the user's language, not yours.
Clear labels always beat clever ones. "Pricing" beats "Investment options." "Help" beats "Concierge." Jargon and marketing wordplay force users to decode your navigation before they can use it. If a first-time visitor can't predict what's behind a menu item from its label alone, the label has failed.
Consistency matters too. If a screen is called "Orders" in the menu, don't call it "Purchase history" in its page title. Every synonym is a small doubt planted in the user's mind.
-
keywords
- #Organization
- #Labeling
- #Navigation
- #Hierarchy
Sitemaps: the IA deliverable
A sitemap is a diagram that shows every screen or page of a product and how they connect, like a floor plan for your information.
The sitemap is the primary deliverable of IA work: a simple box-and-line diagram where each box is a page or screen and the lines show the parent-child relationships between them.
Creating a sitemap forces decisions that are easy to postpone. How many top-level categories do we really need? Does "Gift cards" belong under "Shop"? How deep must a user dig to reach a product page? A sitemap makes the invisible structure of a product visible, so the whole team can debate it before anyone draws a single screen.
Keep sitemaps shallow where you can. Every extra level of depth is another click, another decision, and another chance to get lost.
-
keywords
- #Sitemap
- #Deliverable
- #PageHierarchy
Card sorting
How do you know your categories match your users' mental models? You don't guess. You run a card sort: write each piece of content on a card (physical or digital) and ask users to group the cards in a way that makes sense to them. The patterns across participants reveal how your audience naturally categorizes your content.
Open card sorting lets users create and name their own groups. Use it early, when you're still discovering how people think about your content.
Closed card sorting gives users predefined categories and asks them to place cards into them. Use it later, to validate a structure you've already drafted.
Card sorting replaces the loudest opinion in the room with evidence of how users actually organize information. Even five to ten participants will expose groupings you never considered and labels that confuse everyone but your team.
-
keywords
- #CardSorting
- #OpenSort
- #ClosedSort
- #UserResearch
Timeless IA principles
Dan Brown's IA principles have aged remarkably well. Four are worth internalizing:
Treat content as objects. Content is a living thing with a lifecycle, not static text you pour into pages. A product listing has a price that changes, stock that runs out, and reviews that accumulate. Structure should account for that life.
Offer fewer choices. More options don't help users; they paralyze them. A menu with six clear items outperforms a menu with sixteen.
Disclose progressively. Show just enough information for the user to decide their next step, and reveal detail as they go deeper. A search result shows a title and snippet, not the entire article.
Assume many front doors. Users don't always enter through your homepage; search engines, shared links, and ads drop people onto deep pages. Every page must orient a first-time visitor, because for many users, that page is the front door.
-
keywords
- #DanBrown
- #FewerChoices
- #Disclosure
- #FrontDoors
Signs of broken IA
Broken information architecture rarely announces itself. It shows up as symptoms:
Orphan pages. Screens that can't be reached through normal navigation. If the only way to find a page is a bookmark or an old email link, it's an orphan.
Junk-drawer menus. Categories like "More," "Other," or "Resources" that collect everything the team couldn't place. Users know things are in there, but nobody can find anything specific.
Search as a crutch. When analytics show users searching for things that sit in your main navigation, the navigation has failed them. If users rely on search for everything, they're not power users. They're lost.
These symptoms point to the same disease: a structure built around the organization instead of the user. The cure is research, not a fresh coat of visual design.
-
keywords
- #OrphanPages
- #JunkDrawer
- #SearchCrutch
Takeaways
Information architecture is the skeleton of your product. Every screen you design later hangs on it.
IA directly shapes your wireframes. The sitemap tells you which screens need to exist, the organization scheme tells you what content belongs on each screen, and the navigation system tells you which menus and links every layout must accommodate. Skip the IA work, and you'll design beautiful screens that don't connect into a usable product.
Organize content around user mental models, label things in plain language, validate with card sorting, and diagram it all in a sitemap before you open a design tool. Structure first, screens second.