Create an information architecture and menu tree

Organize cluttered navigation items into a logical, task-oriented app menu hierarchy. Ideal for product redesigns and software cleanup.

Prompt

Prompt
You are an information architect organizing application navigation. Review the provided feature list or messy menu structure. Organize it into an intuitive 2-level or 3-level site map tailored to user tasks rather than internal company org charts. Eliminate redundant categories, rename obscure technical labels to clear verbs or nouns, and group infrequent tasks into a clean account or settings drawer. Output format: 1. Navigation Principles (3 rules applied); 2. Menu Tree (indented Markdown list with bracketed intent for each item); 3. Change Log (list of renamed, combined, or relocated items with brief rationale). My app features are below:

Example output

Example for: growing field service management software

1. Navigation Principles
  • Prioritize daily field technician dispatch operations in the primary view.
  • Consolidate billing, invoicing, and rate cards under a single financial hub.
  • Move technical configuration and webhooks into a dedicated workspace settings menu.
2. Menu Tree
  • Dashboard [Daily performance metrics and real-time alerts]
  • Jobs [Core operational workflows]

    • Schedule & Dispatch [Calendar and assignment grid]
    • Work Orders [Active, pending, and completed service tickets]
    • Route Planner [Technician travel optimization]
  • Customers [CRM data store]

    • Client Accounts [Account records and contract terms]
    • Sites & Assets [Equipment serials and maintenance histories]
  • Finance [Monetary transactions]

    • Invoices [Draft and finalized payment records]
    • Estimates [Quotes pending customer signature]
  • Settings [Administrative controls]

    • Team & Permissions [User seats and field access levels]
    • Integrations [Accounting tools and SMS gateway keys]
3. Change Log
  • Combined Dispatch and Calendar: Formerly two distinct top-level tabs; merged into Schedule & Dispatch under Jobs to remove duplicate route views.
  • Renamed Service Tickets to Work Orders: Aligned terminology with field industry standards.
  • Moved Developer API to Settings: Removed from top navigation to prevent non-admin clutter.
Written by AI from this prompt. Your results will vary.

Paste your product's raw feature list, current menu items, or sitemap right below this prompt into ChatGPT, Claude or Gemini. Ask the model to suggest alternative sorting for mobile drawers if needed.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Design