Shortcuts must be shown beside their menu items to support learning

What it is

If a shortcut mapping lives only on a dedicated help page, people must decide to study before they can see it. Placing the chord beside the matching menu item or button lets learning happen on the way to a command already being sought. That is incidental learning: no separate lesson. Display is not decoration. It is the routine moment that attaches a recall-based expert path to a recognition-based main path.

Why it happens

Each time a menu opens, the eye that scans labels also sweeps the chord on the right. After a few repetitions, command name and key sequence are paired in one fixation, and a motor program can begin before anyone practises on purpose. Without the label, menu clicking automatises and the signal “a faster finger action exists” never arrives; the expert path detaches from the main path, and adoption stays with the few who happened to read a manual. The label also offers an immediate check: after a wrong chord, reopening the menu shows whether those keys belong to this item. Placement must be stable—the same command should show the same string in the menu, the context menu, and the command palette, or the pairings overwrite each other.

Studying it

Command-adoption studies toggle shortcut labels beside menu items and track sessions from “menu only” to “starts using the chord,” plus retention after labels are later removed. Independent variables include presence of labels, command frequency, and whether a separate shortcut table exists; dependent measures include the expert-path adoption curve, whether gaze lands on the label, and delayed recall. Asking “do you know this shortcut?” overestimates: many who know it do not use it. Log the actual invocation channel.

Where it stops holding

Icon buttons have no “beside” for a long label; a tooltip or a long-press note must carry the same pairing, and an empty tooltip is equivalent to no display. Mobile UIs often lack a menu bar, so shortcut learning moves to a command palette or a keymap and cannot copy desktop side-labels as-is. People who already fire chords automatically stop reading the labels, but the labels remain a cue for intermittent users and for someone else picking up the machine; do not delete them for visual quiet.

Applying it

• Print the full chord on menu items, palette rows, and button tooltips, using the same string in all three.
• Do not host shortcut learning on a standalone “Keyboard shortcuts” settings page; that page is lookup, not where pairing occurs.
• Watch logs for high-frequency commands shifting from menu clicks to shortcuts; if labels exist and the curve stays flat, check contrast and truncation.

Related

• Same group: C6.03.1 Shortcuts are an expert path, not the only path · C6.03.2 Tradeoff between mnemonic and positional assignment · C6.03.4 Conflict priority with system-level shortcuts
• Adjacent: C6.04 Modifier keys · C3.20 Gesture discoverability
• Search: incidental learning · menu accelerator · shortcut disclosure