Industry
Information Architecture
Client
Content Strategy
Information Architecture Lens

Information Architecture in Practice: The 8 Lenses
📌 Mark,"Information Architecture Lenses" refers to just eight cards, but in reality, the set contains 51 lenses organized into eight categories. The Information Architecture Lenses card deck, created by Dan Brown, is a tool to "question" the structure of a website or system. Each card or lens offers a perspective that helps reveal strengths, weaknesses, or risks that might be overlooked. The cards are grouped according to the evaluation goals. This tool provides a systematic way to assess and critique information architecture by "viewing the structure from multiple angles" rather than judging based on a single feeling or perspective. The entire set is divided into 8 groups as follows: 1. How to classify - The aspect of content categorisation looks at how we group content into different categories and how well the concepts are translated into categories. Are similar contents grouped in the same way, and does each menu have a clear purpose? 2. How to engage - The aspect of drawing users in, looking at how the structure builds confidence, a sense of ownership, and a safe space for users to participate. 3. How to explain - The aspect of explaining the structure. Consider how we will describe and communicate the structure to our colleagues, how difficult it is to create the structure, and what the relationship between the content is like. 4. How to flex - The aspect of flexibility and scalability. Consider how much the structure can expand or contract, whether it sufficiently covers the domain's scope, and if it can handle content that changes over time or seasons. 5. How to guide - User navigation perspective: How does the structure help users reach their goals? Does it convey context well? Is there a way out when users get lost? Does it help users discover new things? 6. How to include - Inclusivity and ethics perspective: Does the structure have barriers that make it inaccessible to certain groups? Who benefits the most, and is there any hidden bias? 7. How to manage - Long-term maintenance perspective. Consider how the structure will be maintained and preserved over time. This is the group that this work has chosen to focus on, which includes Content Types, Metadata Feasibility, Precedence, Slow Change, and Stability. 8. How to present - The aspect of display on the screen, considering how the structure is transformed into a user interface. Is it easy for users to scan for information? How clear are the labels in conveying meaning?


