Information architecture is the structural design of information spaces—how content is organized, categorized, and navigated to serve user goals and mental models. Strong IA anticipates how users will search for and understand information by organizing it intuitively. Poor IA forces users to guess where information lives and how it relates to other content.
Create card sorts with users to understand their mental models of categories. Sketch multiple organizational schemes and evaluate how each supports different user tasks.
That information architecture is only relevant to websites. It applies to any system that must organize and present information—apps, documents, physical spaces.
Think about the last time you walked into an unfamiliar grocery store looking for cinnamon. You probably navigated to the spice aisle by reading overhead signs, scanned alphabetically or by category, and found it within a minute. Now imagine a store where spices were shelved by country of origin, mixed in with sauces and oils from the same region, with no overhead signs. You would wander. That difference — between a structure that matches how people think and one that matches how the organizer thinks — is the core problem information architecture (IA) solves.
From your study of information hierarchy and wayfinding, you understand that content needs clear levels of importance and navigational cues. IA extends this by asking: what is the organizational structure itself? There are several fundamental schemes. Alphabetical organization works when users know the exact name of what they are looking for (a dictionary, a contacts list). Chronological organization suits content that unfolds over time (a news feed, a timeline). Topical organization groups content by subject (an encyclopedia, a university course catalog). Task-based organization arranges content around what users want to accomplish (a banking app with "Transfer," "Pay bills," "Check balance"). Most real systems combine multiple schemes — a recipe website might offer topical browsing (by cuisine) alongside search (by ingredient) and task flow (meal planning).
The most important concept in IA is the distinction between the organizer's model and the user's mental model. Organizations naturally want to structure information around their internal departments, product lines, or technical categories. Users do not care about your org chart — they want to find information using the categories that make sense to *them*. The classic IA research method, the card sort, reveals this gap directly: you give users cards with content labels and ask them to group and name the categories. The results are often surprising — users create groupings that cut across internal boundaries in ways that feel obvious once you see them but that no insider would have proposed.
Good information architecture is invisible. When users find what they need without thinking about the structure, IA is doing its job. When users get lost, cannot find content they know exists, or repeatedly end up in the wrong section, the IA has failed. The practical output of IA work is a site map (the hierarchical structure of content), a taxonomy (the labeling and categorization system), and navigation patterns (how users move between sections). Each of these artifacts should be tested with real users, not just reviewed by stakeholders, because the only measure of good IA is whether the people who use the system can find what they need.
Topics in reflective domains aren't scored by quiz answers. Read, reflect, and mark when you've thought it through.