People notice colors and typography. What decides whether they find what they came for is the structure underneath. That is information architecture.
Most people will never notice the information architecture of a product. That is exactly the point.
They will notice the colors. The typography. The photography. But the thing that decides whether they find what they came for is hidden underneath, in the structure, the labels, and the paths between them.
When I started moving from graphic design into user experience, this was one of the hardest shifts for me. I was used to designing what people could see. Information architecture asked me to design what they could not.
Louis Rosenfeld and Peter Morville, in Information Architecture for the World Wide Web, offer several definitions of the discipline. The first is the one I return to most often. “The structural design of shared information environments.”
Structural. Shared. Environments. Each word matters.
It is structural because it is about the skeleton, not the skin. It is shared because many different people need to understand it, not just the team that built it. And it is an environment because people move through it, much like they move through a building.
Rosenfeld and Morville also describe information architecture as the combination of organization, labeling, search, and navigation systems. That breakdown has become a practical checklist for me.
First, organize around how users think, not how your company is structured. Internal departments rarely match the way customers look for things.
Second, label with the words people actually use. Clever names may feel creative, but familiar names get clicked. If users have to guess what a label means, it is not doing its job.
Third, design navigation that answers three questions. Where am I. Where can I go. How do I get back.
Fourth, treat search as a safety net, not a substitute. Good search helps people who know exactly what they want. It should never be the only way to find content because the structure is unclear.
The best way to test all of this is with real people. Card sorting and tree testing reveal how users group and find information before a single screen is designed.
When the structure is right, the interface feels obvious.
Edward Tufte made the same point in Envisioning Information. “Clutter and confusion are failures of design, not attributes of information.”
Information is rarely the problem. How we organize it is. Invest in the structure first, and everything you build on top of it becomes easier to use.
