Information Architecture (IA) is 'the design of the four systems of organization, labeling, navigation, and search to help people find and manage information more smoothly' — from *Information Architecture* by Rosenfeld, Morville, and Arango (known in the industry as the 'polar bear book,' first published in 1998 and a foundational work).

In one line: IA decides 'how content is grouped, what each piece is called, how people move around, and how they search' —

- Organization system: how content is categorized;
- Labeling system: what each piece of content is called;
- Navigation system: how users move through the structure;
- Search system: how users query directly for what they want.

IA is usually an invisible underlying skeleton — when it's done well you don't notice it; when it's done badly, you constantly 'can't find things and don't know where to click.' Note: IA is not what the interface looks like (that's visual/interaction design) — it is structure and meaning.

Hold onto this yardstick: even the most useful feature, buried four menu levels deep with a mislabeled name, might as well not exist to users.

The most practical standard for judging IA isn't how it looks, but: can users find what they need within a reasonable number of steps — measured with tree testing and task success rates, not gut feeling.