Information architecture
Organizes, labels and connects the content of a website, an app or a service so people find what they are looking for and understand where they are.
What problem it addresses
When there is a lot of content, existing isn’t enough: if it can’t be found, it might as well not be there.
Principles
Organize
Decide how content is grouped.
Label
Choose names that make sense to the person searching.
Navigate
Show where you are and where you can go.
Search
Find something specific without going through everything.
Applications in design
Use it like this
Test your menu labels with people before building it.
Avoid
Copying the company’s org chart into the menu.
Don’t fall for it
A search box doesn’t fix poor organization: people also browse.
Connections
Builds on
Authors and works
- 1996
Richard Saul Wurman
Coined the idea of the information architect, who organizes complex data so it can be understood.
- 1998
Louis Rosenfeld and Peter Morville
Described the organization, labeling, navigation and search systems of a website.
- 2011
Andrea Resmini and Luca Rosati
Extended it to services that cross several channels, such as the web, the app and the physical store.
- 2015
Louis Rosenfeld, Peter Morville and Jorge Arango
Updated the reference work for any information environment, not just the web.
Sources
Original sources
- Wurman, R. S. (Ed.). (1996). Information architects. Graphis.
- Rosenfeld, L., & Morville, P. (1998). Information architecture for the World Wide Web. O’Reilly.
- Resmini, A., & Rosati, L. (2011). Pervasive information architecture: Designing cross-channel user experiences. Morgan Kaufmann. View source: Resmini, A., & Rosati, L. (2011)
- Rosenfeld, L., Morville, P., & Arango, J. (2015). Information architecture: For the web and beyond (4th ed.). O’Reilly. View source: Rosenfeld, L., Morville, P., & Arango, J. (2015)
Last reviewed: