A shortcut nobody knows exists never turns a novice into anybody faster

What it is

Giving an action an accelerator isn't enough on its own — if the user has no idea the faster path exists, the accelerator is just dead functionality sitting there. Moving a user from novice toward expert requires the interface to actively surface, at the moment the user takes the base path, the fact that a faster way exists — rather than assuming the user will dig through documentation or stumble onto it. Without this active surfacing step, most users will stay on the base path indefinitely, regardless of how long they've used the product.

Why it happens

Discovering a path requires that path to fall within the user's current attention, and while executing a base action they already know well, a user's attention is on completing the task itself — they won't proactively search for a faster alternative they don't know exists. That isn't laziness; it's ordinary attention allocation: someone who can already complete the task has no reason to go looking for something they don't know is there. Making the upgrade path visible means putting that hint exactly at the moment and place the user has just finished the action, close enough in time that "what I just did" and "there's actually a faster way" connect naturally in the user's mind — not tucked into a separate entry point the user would never think to visit on their own.

Where it stops holding

This hint is only worth investing in for actions executed repeatedly — showing "there's a faster way" after a one-off action is pointless, since the user never gets a second chance to use it. The frequency of the hint also needs to taper off: if the same hint keeps reappearing and the user never adopts it, that hint isn't triggering learning, and continuing to show it just becomes a new source of distraction — at that point the frequency should drop or the presentation should change, rather than assuming enough repetitions will eventually work.

Applying it

• Right after a user completes an action through the base path that has an equivalent shortcut, surface that shortcut hint nearby (briefly showing the corresponding key combination after a menu action executes, for example), tying the discovery moment to the action itself rather than filing it away on a separate help page.
• For command-driven interfaces, provide a unified entry point that shows both the base name and its corresponding shortcut input side by side (a command palette, say), so a user searching for a feature by name passively sees its faster trigger at the same time.
• Verification: track how a cohort's adoption rate of a given high-frequency action's shortcut changes with tenure. If that curve stays flat over a long stretch, the current hint's timing or placement isn't actually reaching the user's attention and needs to change — don't conclude the cohort simply "doesn't want to learn."

Related

• Same group: A11.04.1 Novices rely on recognition, experts rely on recall · A11.04.2 Accelerators and the base path must coexist
• Adjacent: A7.15 Layered mental models: functional, structural, and implementation levels
• Search: shortcut discoverability · progressive disclosure · feature adoption curve