Organize around how people think
- Group by objects users recognize: customers, projects, invoices.
- Or by jobs they do: plan, build, report.
- Avoid grouping by your org chart or by the order features were built.
- Use the words customers use. If they say "clients", do not say "accounts".
Principles that scale
| Principle | In practice |
|---|---|
| Limit the top level | Five to seven items covers most products |
| Stay consistent | Navigation should not change between pages |
| Show location | Highlight the current section and use breadcrumbs for depth |
| Support search | A global search and command palette help power users |
| Plan for growth | Create a place for new features before you build them |
Test the structure
Two simple methods reveal most problems. In card sorting, users group your content into categories, which shows how they think. In tree testing, users try to find specific items in a text-only version of your menu, which shows where the structure fails. Both take a few days and prevent expensive redesigns.
Review it every quarter
Add a short IA check to your release rhythm. When a new feature ships, decide where it lives and whether something should move. Small, regular adjustments beat a painful overhaul every two years.



