openskills.info
Course catalog
Open Course

Information Architecture

Information architecture is the design of structures, labels, navigation, and search that make an information environment understandable. It helps people know where they are, what is available, and how to find what they need.

itEnterprise architecture and integration

Don't Panic — Information Architecture

Information architecture is the structural plan that makes an information environment comprehensible. It is what stops a website, application, or help center from becoming a very polite pile of documents. Without that plan, information tends to follow department names, publishing history, or whichever menu item had spare room. Those are organizational facts, not necessarily useful routes for a person trying to complete a task.

The first surprise is that a menu is not the whole job. Navigation exposes routes, but the architecture also decides what belongs together, what each thing is called, which metadata supports filtering, and how search interprets a stated need. A sitemap is useful too. It is still only a picture of some relationships. It cannot carry every category boundary, synonym, redirect, or governance decision without becoming a diagram with ambitions above its station.

The durable model has three inputs: users, content, and context. Users bring goals and vocabulary. Content brings formats, volume, relationships, and a lifecycle. Context brings business rules, technology, and the people who must keep the arrangement working. These inputs shape four connected systems: organization, labeling, navigation, and search. Labels matter because they give information scent: they let a person make a reasonable guess about what a route leads to before spending a click on it.

Structure is not found by holding a sufficiently intense meeting about menus. Card sorting shows possible groupings and participant language, but it does not manufacture a finished hierarchy. The next step is to define category scope, draft a text tree, and test whether people can find targets without visual design helping them. A wrong first branch or a backtrack is useful evidence. It means the structure made a plausible promise and then failed to keep it, which is considerably more specific than saying that the navigation feels off.

Read the Intro for the full model and its limits. The Slides compress the relationships and tradeoffs into a map. The Cheatsheet keeps the working definitions, research methods, and diagnostic signals close at hand. Then use the Practice Reference and exercise to turn a small fictional content set into an architecture you can test, revise, and explain without requiring a rescue committee.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources