Information Architecture
Create a structure that makes location, meaning, and movement predictable. Do not use visual hierarchy to conceal an unresolved taxonomy.
Inputs
Collect representative content and objects, top user tasks, entry points, current navigation, search behavior, terminology, permissions, scale expectations, and analytics or research evidence. Sample real long-tail content, not only ideal examples.
Workflow
- Inventory the domain. List content types, objects, attributes, relationships, owners, lifecycle, and access rules. Flag duplicates and orphaned material.
- Prioritize retrieval tasks. Identify what users need to find, compare, understand, or act on, including frequency and consequence.
- Elicit mental models. Use interviews, search queries, support language, card sorting, and observed behavior. Separate internal organization language from user language.
- Define the taxonomy. Create mutually understandable categories and facets. State inclusion rules, exclusions, synonyms, and governance ownership.
- Choose navigation patterns. Match global, local, contextual, utility, and sequential navigation to task relationships. Avoid using nesting as the default solution.
- Design labels. Prefer specific, familiar, parallel labels. Test ambiguous terms in context and provide disambiguation where categories overlap.
- Design retrieval. Decide when browsing, search, filtering, sorting, saved views, or recommendations are appropriate. Define searchable fields and useful zero-result recovery.
- Model growth and permissions. Test deep content, large counts, role differences, localization, archived states, and future object types.
- Validate. Use tree testing for findability, card sorting for grouping, first-click tests for orientation, and task-based usability tests for the complete experience.
Output contract
Return:
- domain inventory and object relationships;
- prioritized retrieval tasks;
- taxonomy with category rules and synonyms;
- navigation map;
- search, filter, and sorting model;
- labeling decisions;
- validation plan and governance owner.
Verification
Test whether a new user can predict where an item belongs, whether one item has an intentional home, whether labels remain meaningful out of context, and whether permissions or scale create dead ends. Record contested classifications instead of forcing false consensus.
Use content-design for terminology systems and interaction-design for the behavior of navigation, filtering, and search controls.
1---2name: information-architecture3description: Organize product content, objects, navigation, search, filters, labels, and hierarchy around user mental models and retrieval tasks. Use when people cannot find, understand, or predict where information and actions belong.4---56# Information Architecture78Create a structure that makes location, meaning, and movement predictable. Do not use visual hierarchy to conceal an unresolved taxonomy.910## Inputs1112Collect representative content and objects, top user tasks, entry points, current navigation, search behavior, terminology, permissions, scale expectations, and analytics or research evidence. Sample real long-tail content, not only ideal examples.1314## Workflow15161. **Inventory the domain.** List content types, objects, attributes, relationships, owners, lifecycle, and access rules. Flag duplicates and orphaned material.172. **Prioritize retrieval tasks.** Identify what users need to find, compare, understand, or act on, including frequency and consequence.183. **Elicit mental models.** Use interviews, search queries, support language, card sorting, and observed behavior. Separate internal organization language from user language.194. **Define the taxonomy.** Create mutually understandable categories and facets. State inclusion rules, exclusions, synonyms, and governance ownership.205. **Choose navigation patterns.** Match global, local, contextual, utility, and sequential navigation to task relationships. Avoid using nesting as the default solution.216. **Design labels.** Prefer specific, familiar, parallel labels. Test ambiguous terms in context and provide disambiguation where categories overlap.227. **Design retrieval.** Decide when browsing, search, filtering, sorting, saved views, or recommendations are appropriate. Define searchable fields and useful zero-result recovery.238. **Model growth and permissions.** Test deep content, large counts, role differences, localization, archived states, and future object types.249. **Validate.** Use tree testing for findability, card sorting for grouping, first-click tests for orientation, and task-based usability tests for the complete experience.2526## Output contract2728Return:2930- domain inventory and object relationships;31- prioritized retrieval tasks;32- taxonomy with category rules and synonyms;33- navigation map;34- search, filter, and sorting model;35- labeling decisions;36- validation plan and governance owner.3738## Verification3940Test whether a new user can predict where an item belongs, whether one item has an intentional home, whether labels remain meaningful out of context, and whether permissions or scale create dead ends. Record contested classifications instead of forcing false consensus.4142Use `content-design` for terminology systems and `interaction-design` for the behavior of navigation, filtering, and search controls.
memi-design