Global navigation
Users revisit several top-level product or service areas.
- Type
- UI-UX
- Sources
- 3
- Trail checked
Headers, breadcrumbs, tabs, side navigation, steps, local anchors, and return paths.
Browse all problem familiesNavigation exposes the site's structure at the moment a person needs to move. A useful route has a recognizable label, a predictable destination, and an orientation cue after arrival.
Strong: A patient opens Appointments from the main navigation, sees Check in on the appointment page, and uses a breadcrumb to return to appointment details.
Weak: A patient opens Services, then Account, then Help while looking for check-in because each label appears equally plausible.
Try it: Trace one task across three pages and mark every point where the person chooses a route or checks their location.
Begin with the core behavior, apply it in different contexts, then review cases that reveal the quality boundary. Open each entry for its decision rule, states, example, and source trail.
0 of 21 studies complete
Start this family →Learn the shared task and the core interaction choices.
Users revisit several top-level product or service areas.
A screen needs a current title plus back, close, menu, search, save, share, edit, or overflow actions.
Pages sit inside a clear parent-child hierarchy.
A multi-page transaction or form asks users one thing per page.
Pages include repeated navigation, headers, breadcrumbs, filters, or other content before the main content.
The current page has a few genuinely adjacent pages, services, programs, or resources users often need next.
Choose a specialized form for the context and follow its complete behavior.
A named service is used repeatedly by some users.
A product area has several related pages arranged in a visible hierarchy.
Users switch between sibling panels frequently.
A long content page has several meaningful sections users may want to jump to.
A linear form, application, checkout, or setup flow has three or more meaningful steps.
An end-to-end journey spans several pieces of guidance, service links, departments, or channels.
The collection has many ordered results.
A compact mobile app has three to five high-frequency top-level destinations.
A constrained app needs access to more destinations than fit in the visible navigation surface.
A top-level navigation section has many related child destinations.
Users need persistent access to support, search, account, notifications, language, switching, or sign-out controls.
Users need to traverse a broad product surface quickly.
Users inspect multiple objects and often need to return to one they recently opened.
A small set of peer slides must share one constrained display area.
Study failure cases and identify the better recovery route.
Use this anti-pattern to review result pages, data tables, search results, inboxes, catalogs, audit logs, resource lists, and generated pagination controls.
Try fewer words, clear the filter, or search across all pattern families.
Search all patterns