Executable actions should be visible
Aliases: visibility · action visibility · action exposure
What it is
Visibility is the extent to which people can discover, in their current task and state, what actions a system offers, whether they are available, and roughly what they do. A fully implemented feature is nearly absent to most users when it sits in an unexpected place, has no perceptible entry, or is mixed with irrelevant content. Visibility concerns exposing action opportunities, not putting every function on screen at once.
Why it happens
People form a set of possible actions from visible objects, labels, and state, then select a next step. When an entry is clear, stable, and task-relevant, the search space is smaller. When hidden or without a signifier, people must use memory, guessing, hierarchy browsing, or probing to expand that set. Visibility thus affects first discovery, error recovery, and task switching, as well as whether people realize a capability exists.
Studying it
Give people a goal without a path and observe whether they independently find a key action, where they start searching, how long it takes, and whether abandonment leads them to believe the capability exists. Measure discovery, first clicks, navigation depth, help seeking, and error paths. Test across screen size, permission state, and task context, since responsive layout or state changes often make an entry disappear.
Where it stops holding
Visible does not mean permanently exposed. Infrequent, advanced, or context-specific functions can appear at an appropriate moment without disrupting the primary task. The issue is when a critical capability cannot be reasonably found when needed. Overexposure also creates density, choice, and attention burden that makes the primary action less conspicuous; visibility must be designed together with hierarchy and priority.
Applying it
- Identify the key actions for each primary task and ensure they have predictable entries, clear names, and recognizable state when relevant.
- Manage complexity with grouping, progressive disclosure, and contextual presentation rather than hiding everything in menus to lower apparent density.
- Test discovery through unguided tasks and live search behavior, especially first use, error recovery, and device switching.