Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Role guide
Information Architect source-backed Guide
Defines source-backed information architecture and findability, evidence handling, and action boundaries.
Read the fileOverview
Information Architect overview
Use this bundle to prepare source-backed information architecture and findability analysis and a review-ready information architecture brief.
Read the fileWorkflow
Information Architect source-backed triage
1. State the requested decision or artifact. 2. Inventory evidence: users, tasks, research, content inventory, and supported channels; current taxonomy, labels, navigation, search, metadata.
Read the fileTemplate
information architecture brief
Review-ready artifact for information architecture and findability, evidence quality, verification, and controlled next actions.
Read the fileIs this bundle right for your task?
Who it is for
- People performing or supporting Information Architect work, plus teams reviewing its decisions and outputs
- Teams working in Product design, Digital services
When to use it
- An Information Architect task needs a structured plan, evidence checklist, or review-ready output.
- A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.
What you need to provide
- The task objective, intended audience, working context, constraints, source material, and decision owner.
- Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.
Tasks and expected outputs
Questions it helps answer
- Prepare an information architecture brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready recommendation with explicit verification and approval boundaries.
What it helps produce
- information architecture brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach Information Architect work by producing information architecture brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with European Commission ESCO — Classification / Occupation, then confirm that the reference is current and applicable. Inspect Information Architect source-backed Guide before drafting.
Context path: bundles/roles/information-architect
What the bundle includes
Frameworks
- source-evidence matrix
- information architecture and findability review matrix
- qualified-review gate
Evaluations
- Information Architect source verification check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.
Known limitations
- Use the cited official, originator, standards, or professional sources for general information architecture and findability context; local facts, records, values, states, and permissions require inspected evidence.
- Task-specific work requires current evidence for users, tasks, research, content inventory, and supported channels; current taxonomy, labels, navigation, search, metadata, and governance; analytics, search logs, card sorts, tree tests, and sampling limits; content ownership, lifecycle, permissions, localization, and accessibility; alternatives, prototypes, validation results, migration, and approval.
- Do not infer user mental model, label comprehension, findability, taxonomy completeness, test outcome, content ownership, or implementation state.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, and other sensitive data.
- Require explicit confirmation before publishing navigation, migrating content, changing permissions or metadata, or claiming usability or accessibility.
- Route legal, privacy, security, compliance, financial, employment, safety, and other qualified judgments to an evidenced accountable reviewer.