High-frequency functions should not live in the hamburger
Aliases: menu demotion · expose frequent destinations
What it is
A hamburger can hold places people visit rarely. Keeping frequent items out of the hamburger is a different rule: destinations that already rank high by open count or by task criticality must remain tappable before the menu is opened. Hiding hurts use of everything inside, but for frequent items the hurt is not acceptable — it adds a step to a path walked every day, and buys nothing except a tidier chrome.
Why it happens
The cost of a navigation is “find the entry” times “how often you go”. Hide a rare item and the total stays small because the count is low. Hide a frequent item and even one extra tap, multiplied by dozens of trips a day, dominates the product’s navigation tax. Frequent paths become muscle memory: the entry has to sit in a stable visible place, not behind a container that must be opened and then aimed at. Putting Messages, the workbench, or the current project in a hamburger asks people to make a container decision on the road they know best.
Demotion also sends a signal. Items in the menu are read as secondary. If the product actually completes its main task through that item, the mental model fights the structure: people look for the main task on the visible surface, conclude the product does not have it, and do not go hunting in the menu. When visible slots run out, the right moves are to merge destinations, offer shortcuts, or decide again what the main task is — not to park still-frequent items in the hamburger and call them “still reachable”.
Where it stops holding
Frequency is per audience and per version, from real data. An audit page an admin opens daily is rare for everyone else and can live in a menu; for the admin it should be exposed or given a role-specific visible bar. Seasonal peaks (tax season, a campaign console) temporarily promote a quiet item; there should be an exposable path, not a wait for the next information-architecture rewrite. User-pinned items may sit on the visible surface even if they are not frequent in the global stats — frequency is counted for the person who uses them. Settings, About, and Sign out are almost always rare and belong in a menu; do not mix them with the exposed main task for the sake of symmetry.
Applying it
- Rank destinations by arrivals per person per day. Items at the front that sit on the main-task path must not exist only inside the hamburger.
- When visible slots run out, cut truly rare items, merge peer destinations, or offer pins — do not demote still-front-rank items into the menu.
- What remains in the hamburger should be account, legal, and occasional lab switches: things that do not depend on being seen while passing. Name them clearly; do not rely on people remembering that the main function is inside.
- How to check: export a week of navigation clicks and list arrivals for every hamburger item. Anything in the same order of magnitude as the visible bar should be exposed for a round, then re-checked against main-task health. Also have someone go to their most frequent place with their eyes closed; if the hand goes to the hamburger first, that item should not be inside.