Marking menus support a smooth shift from watching the menu to muscle memory
Aliases: marking menu · rehearsal principle
What it is
A marking menu pops a labelled ring of sectors around the nib after a short press-and-wait; an immediate stroke skips the menu and hits the same sectors by heading. Novices mark while reading labels; experts use the same arm path from memory. The motion is one path. Becoming expert is not learning a second shortcut vocabulary; it is doing the watched stroke faster and dropping the wait. That is rehearsal: every look at the menu practices the expert act.
Why it happens
The delay splits “I still need to see where to go” and “I already know” as two timings of one control. The wait should end before a person who needs to look has given up—too short, the menu cannot help novices; too long, experts hit the menu every time. Sector layout must stay put or expert muscle memory dies; if frequent items move with context, rehearsal breaks and people stay novices. Nested marking menus use the first heading for a group and the second for a command; experts can chain two segments without stopping. Unlike a linear menu plus a separate hotkey, the hotkey’s motion (keyboard) is not the menu’s motion (pointing), so going from watching to the shortcut is a second memory. Marking menus need a pen, or an equivalent pointer, that can stroke from the object; a mouse right-press can mark too, but the pen is already on the object and skips a mode button.
Studying it
Start people on an unfamiliar command set with a marking menu versus “menu + a separate gesture or hotkey”. Log trials to reliable eyes-off marking and how the fraction of waits falls with practice.
Independent variables: pop-up delay, whether sectors are fixed, nesting, control technique (linear menu / independent pen gesture). Dependent measures: trial–time curve, share of expert (no-wait) trials, regression after the layout is shuffled.
Watch whether novices use the expert trajectory; if they tap sector labels instead of stroking through, rehearsal is broken.
Where it stops holding
Long names or items that need explanation do not fit sector labels. Marking menus help when the verb is known and the heading is not; they do not teach unknown verbs. Screen edges clip the ring; the circle must be nudged on-screen, briefly mismatching absolute heading and visual position. Touch long-press already consumes a delay; stacking another wait conflicts. Users who cannot make a short directed stroke need an equivalent item-by-item focus path.
Applying it
- Delay the sector ring on press; an immediate stroke takes the expert path; both hit the same command.
- Keep sector positions stable inside a tool; do not let “delete” sit up today and left tomorrow, however much context changes.
- Novices must stroke through a sector, not tap the label—taps bypass rehearsal.
- How to check: first-round new users should almost always wait; later, waits fall and the path shape stays. Move a sector and errors should cluster on the old heading, evidence that muscle memory formed. When the ring is nudged at an edge, heading hits should still match the unclipped layout.