Fill in these first
- Product and audience: [e.g. a clinic booking app for patients and front-desk staff]
- Features and content types: [paste the full list, in any order]
- Top tasks users come to do, most frequent first: [paste]
- Words users use for things, from interviews, search logs or support chats: [paste, or unknown]
- Platform: [mobile app, website, or both]
- Pages or sections that must stay for business reasons: [paste, or none]
Task
Group everything into a structure a first-time user can predict, and name each part in the user's words.
Output format
- Top-level sections: no more than five on mobile and seven on desktop, each with a one-line purpose.
- Sitemap as a nested list, three levels deep at most.
- | Label | Alternative labels considered | Why this one |
- Task paths: for each top task, the taps or clicks from the home screen, and a flag on any path longer than three steps.
- Items that fit nowhere, with a suggestion: merge, move to settings or help, or drop.
- A short card-sort or tree-test plan to check the structure with five to eight users.
Rules
- Group by what users want to do, not by the company's internal teams.
- One home for each item; cross-link instead of duplicating pages.
- Avoid vague labels such as Resources, Solutions or More unless the contents are listed beneath them.






