Prompts for Information Architecture

7 ready-to-use ChatGPT prompts for information architecture. Fill in the bracketed fields, paste into ChatGPT, and go.

Product & UX · 7 prompts

01

Design Information Architecture for a Product Area

Design a clearer information architecture for a product area with better grouping and findability.

You’ll needproduct areauser taskscurrent structureknown confusion pointsconstraints
Prompt
You are an information architecture strategist.

Design a better IA for the product area below.

Context:
- Product area: [product area]
- Primary user tasks: [tasks]
- Current structure: [current structure]
- Known confusion points: [confusion]
- Constraints: [constraints]

Instructions:
1. Identify the main jobs users are trying to complete.
2. Recommend a clearer grouping and labeling structure.
3. Explain how the structure supports findability and task flow.
4. Call out tradeoffs or places where the current mental model may differ from the team's.
5. Keep the structure practical for the product context.

Output format:
- IA assessment
- Recommended structure
- Grouping and labeling logic
- Risks and tradeoffs

Missing information policy:
Proceed with assumptions unless the user tasks or current structure are unclear.

Quality bar:
- User-task driven.
- Clear grouping logic.
- Avoid abstract IA jargon.
02

Review Navigation for Clarity and Findability

Review a product's navigation for confusing labels, weak hierarchy, and poor findability.

You’ll neednavigation structureuser tasksknown complaintsdevice context
Prompt
You are reviewing a product's navigation system.

Evaluate the navigation using the context below.

Context:
- Current navigation structure: [navigation]
- Main user tasks: [tasks]
- Known complaints or confusion: [complaints]
- Device context: [device]

Instructions:
1. Identify where the navigation structure or labels are likely causing confusion.
2. Evaluate hierarchy, labeling, and route-to-task clarity.
3. Explain how users may misinterpret the current setup.
4. Recommend the highest-value changes.
5. Keep the review grounded in findability and task completion.

Output format:
- Navigation assessment
- Main clarity issues
- Recommended changes
- Priority order

Missing information policy:
Proceed with assumptions unless the navigation or user tasks are unclear.

Quality bar:
- Findability-focused.
- Specific.
- No vague “make it simpler” advice.
03

Plan a Card Sort or Tree Test

Plan a card sort or tree test that helps validate labels, grouping, and findability.

You’ll needproduct areauser taskscurrent IA questionstimelinetooling
Prompt
You are a UX researcher planning an IA validation study.

Plan a card sort or tree test for the context below.

Context:
- Product area: [product area]
- Main user tasks: [tasks]
- Current IA questions: [questions]
- Timeline: [timeline]
- Tooling or constraints: [tooling]

Instructions:
1. Recommend whether card sorting, tree testing, or both are most useful here.
2. Define what the study should validate.
3. Suggest tasks, prompts, and success criteria.
4. Keep the plan realistic for the stated timeline.
5. Explain how the outputs should inform IA decisions.

Output format:
- Recommended method
- Study objective
- Task or prompt design
- Success criteria
- How to use the results

Missing information policy:
Proceed with assumptions unless the IA question or user tasks are unclear.

Quality bar:
- Method fit matters.
- Keep it lean.
- Tie the study to a decision.
04

Design the Information Architecture for an Executive Dashboard

Design the information architecture for an executive dashboard with hierarchy, drill paths, and decision-oriented grouping.

You’ll needdashboard purposeleadership audiencemetrics availablereview cadencekey decisionsknown pain points
Prompt
You are designing the information architecture for an executive dashboard.

Use the context below.

Context:
- Dashboard purpose: [purpose]
- Leadership audience: [audience]
- Metrics or signals available: [metrics]
- Review cadence: [cadence]
- Key decisions the dashboard should support: [decisions]
- Known pain points with current reporting: [pain points]

Instructions:
1. Organize the dashboard around how leaders scan and interpret business health.
2. Establish the right hierarchy between headline metrics, context, and drill-down detail.
3. Group information by decision usefulness rather than data source.
4. Flag where the dashboard risks becoming dense, misleading, or too shallow.
5. Keep the IA realistic for an actual product or reporting build.

Output format:
- IA overview
- Primary sections and hierarchy
- Drill-down logic
- Risks or clutter warnings
- Recommended next design moves

Missing information policy:
Proceed with assumptions unless the dashboard purpose or audience is unclear.

Quality bar:
- Decision-oriented grouping.
- Strong signal hierarchy.
- Realistic dashboard structure.
05

Design the Information Architecture for an Internal Knowledge Surface

Design the information architecture for an internal knowledge surface with hierarchy, findability, and workflow relevance.

You’ll needknowledge surface purposeuser groupscontent typescurrent findability issuesworkflow contextmaintenance constraints
Prompt
You are designing the information architecture for an internal knowledge surface.

Use the context below.

Context:
- Knowledge surface purpose: [purpose]
- User groups: [users]
- Content types or information to organize: [content types]
- Current findability or clutter issues: [issues]
- Workflow context where the surface is used: [workflow]
- Maintenance constraints: [constraints]

Instructions:
1. Organize the surface so users can find the right level of signal quickly.
2. Clarify hierarchy, navigation logic, and content grouping.
3. Distinguish reference material from decision-support and action-oriented information.
4. Avoid structures that look neat but become impossible to maintain.
5. Keep the IA grounded in real workflow usage.

Output format:
- IA overview
- Primary sections and hierarchy
- Navigation and findability logic
- Maintenance cautions
- Recommended next design moves

Missing information policy:
Proceed with assumptions unless the surface purpose or user groups are unclear.

Quality bar:
- Workflow-grounded IA.
- Strong findability logic.
- Maintainable structure.
06

Design a UX Brief for an Internal Search Surface

Design a UX brief for an internal search surface with user jobs, failure risks, and quality expectations.

You’ll needsearch use caseuser groupscontent being searchedcurrent failure modestrust needsconstraints
Prompt
You are designing a UX brief for an internal search surface.

Use the context below.

Context:
- Search use case or purpose: [use case]
- User groups: [users]
- Content or sources being searched: [content]
- Current failure modes or frustrations: [failures]
- Trust or quality expectations: [trust]
- Constraints: [constraints]

Instructions:
1. Clarify the main jobs users need the search surface to support.
2. Identify what makes search feel useful, trustworthy, or broken in this context.
3. Distinguish retrieval accuracy from interaction design problems.
4. Define the UX expectations the product should meet.
5. Keep the brief practical for design and product teams.

Output format:
- UX brief summary
- Main user jobs
- Current failure risks
- Quality and trust expectations
- Priority design considerations

Missing information policy:
Proceed with assumptions unless the search use case or user groups are unclear.

Quality bar:
- Job-focused brief.
- Trust-aware framing.
- Design-team usefulness.
07

Review Search Results UX for Relevance and Findability

Review search results UX for relevance, grouping, labeling, and next-step clarity from a findability perspective.

You’ll needsearch results experiencemain user jobscontent typesknown search complaintsranking or filtering behaviorconstraints
Prompt
You are reviewing a search results experience for relevance and findability.

Use the context below.

Context:
- Search results experience or screenshots described in words: [search results]
- Main user jobs: [jobs]
- Content or result types: [content types]
- Known search complaints: [complaints]
- Ranking, filtering, or grouping behavior: [behavior]
- Constraints: [constraints]

Instructions:
1. Evaluate whether the results help users recognize the right item quickly.
2. Review relevance cues, labeling, grouping, filtering, and result hierarchy.
3. Flag where the experience creates uncertainty, false confidence, or excess scanning cost.
4. Recommend the highest-value UX improvements.
5. Keep the critique grounded in task completion and findability.

Output format:
- Search-results UX summary
- Main relevance and findability issues
- Highest-value improvements
- Risks or edge cases to test

Missing information policy:
Proceed with assumptions unless the search experience or user jobs are unclear.

Quality bar:
- Findability focus.
- Relevance realism.
- Practical improvements.