ia-strategy-and-deliverables
Turn architecture work into actionable strategy and deliverables: test candidate structures before
SKILL.mdsubagents/ux-design-advisor/skills/ia-strategy-and-deliverables/SKILL.md
GitHubIA Strategy and Deliverables
Turn architecture work into actionable strategy and deliverables: test candidate structures before commitment, pair strategy with a plan, and tailor sitemaps, wireframes, diagrams, and guidance to audience and purpose over polish.
When this applies
- Communicating IA strategy to stakeholders, clients, colleagues, or implementation teams (P022).
- Cross-functional teams are resolving interface, navigation, architecture, and implementation questions (P035).
- Preparing architecture documentation for designers, developers, editors, or production staff (P036).
- Moving from strategy into design or implementation (P049).
- Creating or presenting IA diagrams or nonvisual equivalents (P050).
- Exploring or communicating broad architecture and navigation concepts (P051).
- Creating multiple wireframes or a wireframe set for clients or production teams (P052).
- writing a practitioner-facing design guide (P053).
- synthesizing evidence for a practice (P066).
- Designing important, complex, unique, confusing, or template-setting pages and screens (P071).
Procedure
Apply these principles to the situation under review; for each, name the user need at stake and the trade-off the choice carries.
- Use scenarios, stories, case studies, diagrams, sitemaps, wireframes, and reports to make abstract IA strategy understandable and actionable for different audiences. (P022)
- Use sketches, wireframes, and prototypes to integrate IA with visual design, technical feasibility, and team vocabulary before committing to code or finished graphics. (P035)
- Make implementation-stage sitemaps simple, modular, traceable, and production-ready with condensed notation, unique IDs, hierarchy coverage, labels, and navigation specifications. (P036)
- Pair IA strategy with a project plan and presentations so recommendations become feasible, sequenced, integrated with other teams, and understood by stakeholders. (P049)
- Treat IA diagrams as partial communication views; tailor each view to audience and need, present it live when possible, and value usefulness over polish. (P050)
- Use high-level sitemaps as purpose-specific, selective discussion tools for exploring organization, navigation, ownership, management, and access paths. (P051)
- Choose wireframe fidelity and production practices deliberately, maintaining consistency, reusable templates, callouts, revision metadata, and team stewardship. (P052)
- Deliver guidance in simple, objective, and clear language with short explanations, concrete per-practice examples, extended before-and-after examples, and references to supporting studies; state the objective and scope or limitations early and do not present it as exhaustive or as a full technical or process manual. (P053)
- Base conversational guidance on primary, full research studies that measure user-centered outcomes such as satisfaction and trust, excluding studies that report no user impact or only algorithmic or technical performance, and passing each study through a quality checklist. (P066)
- Use wireframes to connect IA with interaction design by clarifying page structure, visible components, grouping, priority, responsive behavior, and navigation overload. (P071)
Principles applied
- P022 (medium) — grounded in claims/evidence and chunk anchors in
sources/. - P035 (medium) — grounded in claims/evidence and chunk anchors in
sources/. - P036 (medium) — grounded in claims/evidence and chunk anchors in
sources/. - P049 (medium) — grounded in claims/evidence and chunk anchors in
sources/. - P050 (medium) — grounded in claims/evidence and chunk anchors in
sources/. - P051 (medium) — grounded in claims/evidence and chunk anchors in
sources/. - P052 (medium) — grounded in claims/evidence and chunk anchors in
sources/. - P053 (medium) — grounded in claims/evidence and chunk anchors in
sources/. - P066 (high) — grounded in claims/evidence and chunk anchors in
sources/. - P071 (medium) — grounded in claims/evidence and chunk anchors in
sources/.
Provenance
Grounded in principles P022, P035, P036, P049, P050, P051, P052, P053, P066, P071, their backing
claims and evidence records, and paragraph-level source anchors under sources/anchors/. Every
cited id resolves into this package's distilled spine; see provenance-ledger.md and
reports/faithfulness-report.yaml.