navigation-designlisted

# Navigation Design Create intuitive wayfinding systems for content and applications. Navigation design determines whether users find what they need or abandon in frustration. Good navigation is invisible; bad navigation is the #1 complaint on support channels. ## When to Use - Designing site-wide navigation (top nav, sidebar, footer) - Planning a sitemap or information architecture - Structuring sidebar menus for documentation - Designing breadcrumb systems - Organizing content hierarchy and categorization - Evaluating whether current navigation is working (analytics, user feedback) ## When NOT to Use - Mapping user journeys across touchpoints over time (use user-journey-design) - Writing navigation labels, microcopy, or button text (use ux-writing) - Implementing Next.js routing, layouts, or parallel routes (use nextjs-development) - Designing visual styling of navigation components (use frontend-design) ## Decision Tree ``` What navigation problem are you solving? │ ├─ Structuring a new site/app │ ├─ Broad, shallow content? → Flat IA + global nav │ ├─ Deep, hierarchical content? → Tree IA + sidebar nav │ ├─ Hub-and-spoke workflow? → Hub IA + contextual nav │ └─ Multi-dimensional content? → Faceted IA + filter nav │ ├─ Improving existing navigation │ ├─ Users can't find content? → Audit with 3-click rule + card sorting │ ├─ Too many top-level items? → Consolidate to 7±2; use progressive disclosure │ ├─ Users get lost in deep pages? → Add breadcrumbs + contextu