Capability node
Information Architecture
Structure content and navigation so users and agents can find what they need.
Why this capability exists
A site or workflow fails when its structure does not match how people actually think about the task. IA defines the skeleton that pages, menus, and links hang on.
Input
- Content inventory or list of pages
- User task list from requirement planning
Output
- Site map or page tree
- Navigation model and URL scheme
- Content grouping rules
Risks
- Organizing by tool brand instead of by user task
- Deep nesting that buries important pages
- Ignoring URL and redirect implications for SEO
Acceptance criteria
- A user can reach any primary page in three clicks or fewer
- URLs are stable, readable, and match the tree
- The structure survives adding new content without rework
Skills that execute this capability
No skills are mapped to this capability yet.