The system of menus, links, and pathways that allows users to move through a product and find information. Effective navigation is predictable, consistently placed, and labeled in language users recognize — not internal jargon.
Common contexts
- Auditing navigation labels by testing them in a tree test to see if users' language matches the current category names
- Deciding between a persistent sidebar, a top nav, and a bottom tab bar for a cross-platform product used on both desktop and mobile
- Reducing a three-level nested navigation to two levels after analytics show the third level receives near-zero direct traffic
Use when
Redesign navigation when findability metrics decline, users report getting lost, or when the content structure has grown significantly beyond the original IA — navigation debt compounds quickly.
Avoid when
Don't redesign navigation without research into how users describe and search for content — replacing one label set with another based on internal logic often produces equal or worse findability.
Navigation problems are almost always IA problems wearing a UI costume — relabeling links fixes surface confusion, but if the underlying structure doesn't match users' mental models, the confusion returns.
Real-world examples
- Spotify's bottom tab bar uses five icons (Home, Search, Your Library, Premium, Settings) sized for thumb reach — an architecture validated by eye-tracking showing users rarely scrolled to desktop-style top navigation.
- GOV.UK deliberately removed all top-level navigation from their site in 2013, replacing it with search and contextual in-page links — a radical decision validated by testing showing search-first was faster for 95% of user tasks.
- Amazon's desktop mega-menu exposes three levels of product taxonomy on hover, allowing power shoppers to jump directly to 'DSLR cameras under $500' without two intermediate category pages.