Anatomy
┌──────────────────────────────────────────────────────────────┐
│ ▤ Acme Ops Jobs Customers Invoices Reports ⚙ ▾ │
│ ═════ │
└──────────────────────────────────────────────────────────────┘
↑ home link ↑ ranked by frequency ↑ rare things pooled
═ current section, marked with weight + rule
Three obligations, and the third is the one that gets dropped:
- Identical placement on every screen, including errors, empty states and modals-turned-pages. A nav that moves is not persistent.
- Ranked contents. Order is a design decision, not the order features shipped in.
- A visible current state. This is the cheapest orientation available and the most commonly skipped. Without it the nav says where you can go but not where you are.
Why it works
It converts wayfinding from a per-screen problem into a solved constant. Once a person has learned the nav — which takes one session — every screen in the product inherits that learning for free. That is the highest-leverage consistency in an application.
It also makes deep links safe. Someone landing on a record from an email is not stranded, because the same nav is there as on the home screen.
The ranking is where the real judgment sits, and it is the surface, don't bury principle applied to the top level: prominence equals frequency times importance. Depth for rarely-used things is correct, not a bug.
Getting it wrong
- The org chart in the navbar. Sections named after internal teams, so every user has to learn your structure to find their task.
- Fourteen flat items. Everything promoted, so nothing is.
- Current state by colour alone. Fails in greyscale and for anyone who does not perceive that hue difference. Add weight or a rule.
- A nav that hides on scroll and does not come back predictably. Now reaching it is a gesture people have to discover.
Exemplars
Linear keeps a narrow, quiet sidebar that never moves and never competes, with the current item marked by background rather than colour saturation. It demonstrates that persistent does not have to mean prominent.
Stripe shows the ranking done honestly: Payments, Balances, Customers at the top level, and a genuinely large surface of configuration deliberately pooled under Settings. Most products would have promoted several of those.
The extractable rule: a navigation bar is a published ranking. Whatever is in it, you are asserting people need often. If that assertion is not true, the bar is costing attention on every screen in the product.