The cost of hidden functions rises with use frequency
Aliases: hidden feature · access cost · frequency effect
What it is
Putting a function in a menu, secondary page, hover state, or gesture reduces apparent main-screen complexity, but adds steps to find, open, and confirm it on every access. This hidden feature cost may be small for low-frequency predictable capability. When the same operation is repeated, extra steps, memory demands, and interruption accumulate until they outweigh the visual cost of a visible entry.
Why it happens
Each invocation of a hidden function requires locating an entry, opening its container, identifying a target, and returning to the primary task. Even after practice speeds the motion, hierarchy switching and spatial displacement still interrupt rhythm. As frequency rises, small per-use friction becomes aggregate time, error opportunity, and frustration. When entry position or wording is unstable, forgetting and search cost return with every use.
Studying it
Do not test first discovery only. Record use frequency, access time, menu openings, misselection, and task-switching cost for the same function in representative workflows. Compare hidden and persistent entries in sustained or repeated tasks to see whether a cumulative difference remains after learning. Log analysis can reveal repeated detours, feature abandonment, or substitute paths.
Where it stops holding
High frequency does not mean every control must remain exposed. With limited space, shortcuts, contextual toolbars, pinnable panels, or customization can reduce repeat-access cost. Low-frequency functions should not be buried arbitrarily either, particularly in error recovery or safety contexts. Frequency is only one factor alongside importance, time sensitivity, predictability, and user expertise.
Applying it
- Use real repetition and time sensitivity to give frequent, critical operations persistent, adjacent, or pinnable entries.
- When a function must be contained, keep its name and position stable and offer search, shortcuts, or recent-use access to reduce repeated location.
- Review path length and call distribution regularly; when a hidden operation becomes a high-frequency path, adjust its visibility level.