Information architecture
Articles and writing on information architecture
Foundations
Defining the user’s mental model
The user forms their mental model as they move through an experience. Once a user participates in an event, the user evaluates their expectations of the event with their realization of the event. This point, where the user tempers their expectations with their realizations, we call this point experience.
Information architecture as an alignment discipline
People want to understand the direct value information architecture provides to an organization. Inevitably, the worth of a thing comes down to the value it provides others, and it’s always easier to value the tangible over the intangible. For Information Architecture, people inevitably value the deliverables: our wireframes, site maps, etc.
Reframing information architecture
Talking about information architecture, a language for critique
Can you compare the information architecture of your favorite app to your favorite restaurant? How are they different? How are they the same? Is your IA better? In this presentation, I share a critical language for discussing and evaluating information architecture. This presentation discusses how to evaluate information architecture and identify specific areas of improvement.
Information architecture and the design process
On architecture as “rhetoric for spaces”
Information architecture defines what experiences are possible while design facilitates specific experiences. Understanding this distinction helps identify when you should or shouldn't persuade your project team that they need information architecture.
Information architecture in the design and development process
Not every project needs information architecture. Or design. How well you understand the problem and the solution, as well as how that understanding changes, determines whether or not you need architecture, design, development, or testing.
Information Architecture for Lean and Agile Projects
Information architecture helps avoid waste and capture maximum value early in the development and test process. Agile and lean teams should always begin projects with information architecture for any project eight weeks or longer.