Shortcuts let frequent functions skip the full hierarchy

What it is

Full navigation parks destinations in a tree or in groups; arrival walks that path. A navigation shortcut lifts the most-walked few onto a surface that is always tappable, so frequent functions do not climb from root to leaf every time. It is not a new information architecture. It is a short-cut to a place that already exists. Once the short-cut becomes another tree, it is no longer a shortcut.

Why it happens

A hierarchy’s value is coverage and structure; its tax is depth. Frequent paths pay that tax every day, which is the worst bargain. A shortcut collapses the depth term in “arrivals × depth” to one step, and total cost drops. People can still reach the same place through the full navigation; the shortcut only accelerates. It usually sits in a standing zone for thumb or pointer: beside the tab bar, at the top of a sidebar, a pinned row on a workbench. Because it copies arrival, not a second set of objects, the target should be a node the full navigation already has, or the short-cut and the map will point at two worlds.

A shortcut is not how new functions are discovered. People who have never walked that path will not learn the tree from it. Putting an exploratory entry in the shortcut both occupies a slot meant for frequent paths and fails to teach structure. What it actually replaces is “I already know where, I just do not want to climb”.

Where it stops holding

When destinations are few and already one level, a shortcut is a duplicate. When depth is only two and that level is already persistently visible, the gain is tiny. On touch, a shortcut that competes with primary navigation becomes another row to scan: depth does not fall, scanning rises. One-shot tasks (a wizard) should not have a shortcut; the entry should vanish when the task ends.

Applying it

• Pick truly frequent nodes by arrival count and lift them onto a standing surface; the full tree still keeps the same nodes.
• Point shortcuts only at places that already exist; do not invent pages that have no tree node just for the shortcut.
• Do not put a never-walked new feature in the shortcut as a recommendation; recommendations are a different surface.
• How to check: count hops for a frequent task on the full navigation versus the shortcut; the latter should be clearly shorter. If a newcomer can only finish their first task via the shortcut, the main path was hollowed out and the shortcut is doing discovery it should not.

Related

• Within the group: E5.16.2 Pinned items must stay few, or they stop being shortcuts · E5.16.3 Customizability of shortcuts shapes long-term use · E5.16.4 Duplicate pins and regular nav must stay in sync
• Adjacent: E5.04 Hamburger Menus · E5.14 Command Palettes
• Search terms: navigation shortcut · pinned destination · bypass hierarchy