Different moments in an IA project call for different deliverables. Usage scenarios and storyboards work well for conveying vision and building empathy, especially for stakeholders who aren't going to read detailed documentation. Topic maps and diagrams help explore what content a space should cover and how it interrelates, often used early during ideation. Site maps depict overall structure and navigation paths, informing labeling and navigation design, useful whether as a rough hierarchical list early on or a refined diagram later. Wireframes depict the logical structure of individual pages, informing content models and visual hierarchy without getting into visual design details, and are typically reserved for key pages, reusable templates, or pages that are unusually complex.
Choosing the right deliverable means matching it to the audience and the moment: a concise, business-case-oriented deliverable for executives deciding whether to fund the work is a very different artifact from the detailed structural guidance a development team needs to actually build it.
Showing a detailed wireframe to an executive deciding whether to fund a project, or a vague storyboard to a developer who needs to build the thing, both waste the same resource, everyone's limited attention, spent on the wrong level of detail at the wrong moment.
1: A usage scenario or storyboard is correct. Executives deciding whether to fund a redesign need to understand the business impact and the improved experience quickly, without wading through implementation detail, exactly what scenarios and storyboards are built to convey. A fully detailed wireframe of every template would bury the business case in structural detail executives don't need to make a funding decision, and an unlabeled sketch with no context wouldn't communicate anything at all.
3: Detailed, fully annotated wireframes and site maps are correct. A remote team without ongoing access to the IA team needs documentation that leaves minimal ambiguity, since there's no opportunity for a quick clarifying conversation once questions come up during implementation. A brief storyboard or a single verbal conversation would leave far too much open to interpretation for a team that can't easily follow up.
For the content team, a site map or topic map showing the full structure, including any new sections or categories the redesign introduces, is the more useful deliverable, since it lets them see exactly where new content needs to exist and how it relates to what already does. The executive-facing scenario or storyboard is insufficient for this purpose because it's deliberately high-level and illustrative rather than structurally complete: it's built to sell the vision, not to map out the actual content gaps the content team needs to fill.The underlying principle across all three cases is the same: match the deliverable's fidelity and focus to what that specific audience actually needs to do next, rather than defaulting to one format for every audience regardless of purpose.
Fill in your own details below; the prompt updates as you type. When it's ready, copy it into Claude or whatever AI tool you use.
Casts the AI as: You're a content strategist creating content model documentation.
Names 5 specific outputs to produce, so the response comes back structured rather than a general summary.
System, Purpose and Existing model tell the AI what your specific situation is, not a generic one.
Complete content model with all types and relationships
Fill in your own details below; the prompt updates as you type. When it's ready, copy it into Claude or whatever AI tool you use.
Create visual diagrams for faceted classification systems showing multiple dimensions (facets), their values, and how they combine. Uses Mermaid mindmap or flowchart syntax.
Fill in your own details below; the prompt updates as you type. When it's ready, copy it into Claude or whatever AI tool you use.
Create user flow diagrams in Mermaid syntax showing how users navigate through information architecture to accomplish specific goals, including decision points, success paths, and error handling.