# Navigation Design

Navigation design creates visible, predictable paths that help users understand their location, available destinations, and next steps.

- Type: practice
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/navigation-design/>)

## What it means

Navigation design is the selection, organization, labeling, and presentation of pathways through a product. It includes global and local menus, contextual links, breadcrumbs, tabs, indexes, and wayfinding cues. Navigation expresses part of the underlying information architecture, but it is not the whole architecture: it is the interface through which users move among places and tasks.

## Why it matters

Clear navigation reduces uncertainty and supports both direct task completion and exploration. It communicates the product’s scope, helps people recover from wrong turns, and makes important destinations discoverable without requiring exact search terms. Consistency also frees users to focus on their goal instead of repeatedly learning how movement works.

## When to use it

Use navigation design for any multi-screen product, especially when users revisit several sections, compare alternatives, or need to understand where they are. Review it when important destinations are hidden, menu labels have grown inconsistent, mobile patterns reduce discoverability, or analytics show looping and backtracking.

## How it works

1. Identify priority destinations and journeys from research rather than giving every page equal prominence.
2. Map destinations to a coherent structure and choose labels that users can distinguish and predict.
3. Select patterns suited to the breadth, depth, device, and frequency of use; keep persistent options visible when practical.
4. Provide orientation through current-state cues, meaningful page titles, breadcrumbs, and consistent placement.
5. Test realistic find-and-return tasks across viewport sizes, input methods, and assistive technologies.

## A practical example

A project-management app keeps primary areas—Home, Projects, Inbox, and Reports—in a persistent sidebar. Within a project, tabs expose Overview, Tasks, Files, and Activity, while breadcrumbs show the portfolio context. Less common administration links sit in a clearly labeled settings area instead of competing with daily work.

## Where it breaks

Persistent menus consume space, while hidden menus save space at the cost of discoverability; the right tradeoff depends on context and frequency. Navigation cannot rescue an incoherent content model or vague labels. Analytics reveal movement but not intent, so combine behavioral data with observation and task-based testing.

## Common mistakes

- Hiding primary destinations behind an icon without a strong constraint.
- Using different labels or placements for the same destination across screens.
- Designing from page count alone instead of priority tasks and user expectations.

## Sources

1. [Hamburger Menus and Hidden Navigation Hurt UX Metrics](<https://www.nngroup.com/articles/hamburger-menus/>) — Nielsen Norman Group · Usability research
2. [Navigation Usability Research Reports](<https://www.nngroup.com/reports/topic/navigation/>) — Nielsen Norman Group · Research collection
3. [The Difference Between Information Architecture and Navigation](<https://www.nngroup.com/articles/ia-vs-navigation/>) — Nielsen Norman Group · Professional guidance

## Related topics

- [Information Architecture](<https://wiki.soroush.uk/topic/information-architecture/>)
- [Labeling Systems](<https://wiki.soroush.uk/topic/labeling-systems/>)
- [Information Scent](<https://wiki.soroush.uk/topic/information-scent/>)
