Version: 1.0.0
Purpose
The Information Architecture defines how information is organized, structured, categorized, and presented throughout the product.
Its purpose is to ensure users can easily locate, understand, and interact with information while supporting efficient navigation, scalability, and a consistent user experience.
The Information Architecture establishes the logical organization of the product independently of visual design or implementation.
When This Artifact Is Created
The Information Architecture is created during the Governance phase following approval of the Product Requirements.
It is refined throughout the Architecture and Planning phases as additional product details become available.
Dependencies
Requires:
- Discovery Summary
- Source of Truth
- Product Bible
- Product Requirements
- Product Vocabulary
- Data Dictionary
- Decision Log
Referenced By:
- UI/UX Bible
- Database Architecture
- Build Master Plan
- Architecture
- Planning
- Implementation
- Validation
- Evolution
AI Generation Instructions
The Information Architecture should organize information from the user's perspective rather than the underlying technical implementation.
Group related information logically.
Keep navigation intuitive.
Minimize unnecessary complexity.
Support future product growth without requiring major restructuring.
Every major section should support one or more documented business objectives.
Required Sections
Executive Summary
Provide a high-level overview of the product's organizational structure.
Site / Application Structure
Define the major areas of the product.
Describe how they relate to one another.
Navigation Model
Describe the primary navigation approach.
Identify:
Primary Navigation
Secondary Navigation
Contextual Navigation
Administrative Navigation
Screen Hierarchy
Identify major application screens or pages.
Describe parent-child relationships.
Document major navigation paths.
Content Organization
Define how information is grouped and categorized.
Identify major content collections and organizational structures.
User Flows
Document the primary user journeys through the application.
Identify:
Starting Point
Decision Points
Alternate Paths
Completion Criteria
Search Strategy
Document how users locate information.
Include search, filtering, sorting, and browsing strategies where appropriate.
Taxonomy
Define categories, classifications, labels, and organizational structures used throughout the product.
Permissions and Visibility
Document how information visibility changes based on user roles or permissions.
Reference the Product Vocabulary where appropriate.
Future Expansion
Identify areas intentionally designed to support future product growth.
Validation Criteria
The Information Architecture is complete when:
Major application areas have been identified.
Navigation is logical and consistent.
User flows support documented business objectives.
Information organization is intuitive.
Content classifications are consistent.
Future expansion has been considered.
The human approves the completed artifact.
Maintenance
The Information Architecture should be reviewed whenever:
Major features are added.
Navigation changes.
User roles change.
Business processes change.
Product Requirements change.
Validation identifies usability issues.
The Information Architecture should remain synchronized with all governance artifacts throughout the lifecycle of the project.