Loading…
Loading…
Making relevant controls and information visible so users know what actions are possible.
stellae.design
Visibility is Don Norman's principle that relevant parts of a system should be visible and convey the right message. The more visible functions are, the more likely users will know what to do next. It includes both 'can I see it?' (discoverability) and 'can I understand its state?' (feedback). The tension is: showing everything creates clutter, hiding everything creates confusion. The solution is progressive disclosure — primary functions visible, secondary ones accessible.
Visibility, as defined by Don Norman, states that the correct controls and their current states should be visible to the user without requiring recall or guesswork. When a system makes its functions visible, users can form accurate mental models and take confident action. Violations of this principle force users to memorize commands, hunt for features, or rely on documentation that most people never read.
A registration form validates each field as the user completes it, displaying a green check for valid entries and a red message for errors directly beneath the input. The user never has to submit the form to discover problems, reducing frustration and form abandonment. The current state of each field is always visible without additional interaction.
A rich-text editor displays bold, italic, and alignment buttons in a persistent toolbar with toggled states that reflect the current selection's formatting. Users can see at a glance which styles are active and which tools are available. This direct visibility eliminates the need to memorize keyboard shortcuts for basic operations.
A mobile app relies entirely on swipe gestures to navigate between sections with no visible tabs, buttons, or indicators. New users have no way to discover these interactions without a tutorial overlay that most will skip or forget. The app's own analytics reveal that a majority of users never access features beyond the home screen.
• A common mistake is equating minimalism with hiding functionality; removing visible controls to achieve a clean aesthetic often sacrifices discoverability for first-time users. Another error is making states visible only through color changes without additional cues like icons or text, which excludes users with color vision deficiencies. Teams also frequently forget to make system status visible during asynchronous operations, leaving users uncertain whether their action was registered.
Was this article helpful?