What it is
A diagram of the pages/screens of a product and their hierarchical relationships, used to plan and communicate information architecture.
When to use it
During Synthesize and Prototype, when planning or auditing the structure of a multi-page product.
Why (value)
Reveals the overall structure, exposes orphan pages and redundancy, and aligns the team on navigation and hierarchy.
How to run it
- Inventory the pages/screens (from a content audit if it exists).
- Group them into logical sections.
- Arrange into a hierarchy.
- Check for orphans, redundancy, and depth issues.
- Validate structure with card sorting or tree testing.
Inputs and outputs
- Inputs: A content/page inventory and IA understanding.
- Outputs: A sitemap of pages and their hierarchy.
Time and effort
Low. Hours depending on size.
Evidence and limitations
A structural artifact; whether the structure matches user mental models needs validation (card sorting, tree testing). See Evidence and limitations.
Tips and pitfalls
- Base it on a real content inventory.
- Watch depth, too many levels hurts findability.
- Validate the structure with users.
Variations
Hierarchical sitemaps, flow-based sitemaps.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
- 18F Methods (US government, public domain).
Explore related methods
- Taxonomy design — Design the categories and labels that organize content so people can find things.
- User flow diagramming — Diagram the paths a user takes through a product to reach a goal.
- Content audit — Inventory and assess existing content to see what you have, what works, and what must change.
