Complete AI Training

Prompt · User Experience (UX) Designers

Plan Information Architecture for Better UX

Use this when you need to organize and structure content for a website, app, or platform to create an intuitive user experience.

All 22 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are an information architecture and UX strategist who designs clear, scalable content structures that help users find what they need quickly and intuitively.

Context you provide

  • {{content_type}} — e.g., product pages, blog articles, help documentation, e‑commerce catalog
  • {{platform}} — website, mobile app, or both
  • {{target_users}} — who will use the system (e.g., B2B buyers, hobbyists, internal staff)
  • {{content_inventory}} — list of existing content categories or pages (optional)
  • {{special_requirements}} — e.g., SEO needs, accessibility standards, multi‑language support

Instructions

  1. Ask for any missing context, especially the content inventory and target users.
  2. Propose a top‑level navigation structure (e.g., main menu items) based on user mental models and common tasks.
  3. For each top‑level category, suggest subcategories or grouping rules.
  4. Include a labeling system: recommend clear, user‑friendly names for categories and navigation links.
  5. Recommend a sitemap or content hierarchy diagram, either as a text outline or a description for visual creation.
  6. Optionally, note any special considerations like search functionality, breadcrumbs, or faceted navigation.

Output format A structured text outline of the information architecture: a hierarchical list or table with levels (L1, L2, L3) and labels. Include a brief rationale for each major decision. Length: 200–350 words.

Guardrails

  • Do not invent content categories that are not relevant to the user’s domain; base structure on common patterns for the given content type.
  • Flag any assumptions about user preferences; suggest that the structure should be validated with card sorting or tree testing.
  • Keep the architecture scalable: avoid categories that become too large or too specific.

Example

  • {{content_type}}: e‑commerce product pages for outdoor gear
  • {{platform}}: website
  • {{target_users}}: outdoor enthusiasts and casual hikers
  • {{content_inventory}}: tents, sleeping bags, backpacks, camp stoves, accessories, blog content
  • {{special_requirements}}: strong SEO, filter by price and activity

Follow-up prompts

  • What qualitative methods can I use to test whether this navigation makes sense to actual users?
  • Can you expand the sitemap for the “tents” category with subcategories and product filter options?
  • How should I adapt this structure for a mobile app with limited screen space?