Information Architecture Reviews
Information architecture is the structure and organisation of content in a product. How categories group items, where information sits in hierarchy, which concepts connect together–these choices shape how easily users find what they need. A well-organised site with clear category structure helps users browse intuitively; a poorly organised site forces users to search for everything. Information architecture review evaluates whether structure matches user mental models and supports primary tasks. Unlike visual design, poor IA is invisible to stakeholders until users get lost. Reviews prevent such friction. They work best early, before extensive content creation, though they can reveal problems in existing products worthy of remediation.
a template for briefing a design audit properly
Audit and Classification
Start by inventorying existing content and structure. Identify every major content type and category. Map current hierarchy. Spot redundancy–when the same content appears in multiple places–and orphans–pages nobody links to. Note whether page titles, labels, and category names are consistent and clear. Are they jargon-heavy or accessible? Document navigational patterns–how do users move between related content? Can they easily backtrack? Look for mental model mismatches: labelling a feature “Settings” when users call it “Preferences” creates confusion. Category labels should match language users employ. Audit reveals current state; it does not judge. A site with extensive archives naturally has deeper hierarchy than a small blog.
User Testing of Structure
Card sort exercises reveal how users naturally group related content. Participants sort cards representing content into categories and name those categories. Open sorts (participants create their own categories) reveal natural mental models. Closed sorts (participants assign content to predefined categories) test whether designed structure matches expected groupings. Tree testing presents a proposed structure and asks participants to locate items. A participant should find “return policy” in fewer than three clicks. If participants struggle, the structure does not reflect their expectations. Five to eight participants typically reveal whether structure works. Testing is quick and inexpensive but powerful for validating approach before investment.
a realistic look at what a screen inventory actually contains
Redesign and Implementation
Structure redesigns often feel disruptive but are usually worth the effort if current structure is genuinely confusing. Gradual transitions help–running old and new navigation alongside each other, using search to bridge gaps during transition, clear communication about changes. Navigation design is separate from IA but intertwined–clear IA becomes unusable if navigation is hidden or confusing. Documentation of structure helps future teams understand why categories exist, preventing degradation over time. IA reviews work best as ongoing practice. As products grow and add features, structure that once worked becomes strained. Annual reviews catch creep before it requires major remediation. Content changes outpace design; structure review keeps the two aligned.