There are principles in UX that feel theoretical until the moment a product breaks one, and then , they become impossible to unsee. Visibility, mapping, and feedback are three of the most foundational, and they are almost always discussed as separate topics, each with its own article, its own diagram, its own definition. But they describe a single, continuous thing: the experience of an interaction from beginning to end. To understand one is to understand why the others matter.
What visibility actually means
Visibility, sometimes called discoverability, describes the ease with which users can navigate a product and find what they are looking for. It is not simply about making things large or prominent; it is about the gap between what a product can do and what a user believes it can do, a gap is where features go to die.
The classic failure mode is burying functionality behind a gesture, behind a menu, behind a label that makes sense to the person who named it but not to the person arriving without context. When we design for visibility, we are asking: if a user needed this, would they find it? Not eventually, not with help, but on their own, in the natural course of using the product? The answer to that question tells you more about the quality of a design than almost any other measure.
Miller's law sits directly underneath good visibility work: the average person can hold around seven items, give or take two, in working memory at any one time. The implication for design, is that surfacing everything at once is not the same as making anything visible; it produces cognitive overload that leaves users finding less, not more. Good visibility is not abundance - it’s clarity about what’s available and where.
What mapping means - and where it breaks
If visibility describes what's available, mapping describes what happens when you act. The principle of mapping is the relationship between the controls a user engages with and the results those controls produce, and the closer that relationship mirrors the user's mental model, the less effort the interaction costs them.
The volume knob is the textbook example: turn it right, the volume rises; turn it left, it falls. This is natural mapping - the spatial logic of the action corresponds to the spatial logic of the outcome in a way that almost anyone would predict without instruction. It works because it draws on physical and cultural experience that users already carry with them; the interface doesn't need to teach them anything, it simply needs not to contradict what they already know.
Where mapping breaks down, confusion rises quickly. A user who expects a left swipe to mean "go back" but finds it means "delete" is not making an error; they are responding to a mapping that contradicts their expectations. The problem compounds as interactions become more abstract - touchscreens, voice interfaces, AR and VR environments all present mapping challenges that physical controls never had to solve, because the spatial analogies that make natural mapping work become harder to establish when there is no physical object at all.
What feedback does - and why its absence creates anxiety
Feedback closes the loop - It’s the confirmation, visual, audible, tactile, or some combination, that the action a user took produced the effect they intended. Without it, a user is left in a state of genuine uncertainty: did it work? Should they try again? Did they do something wrong?
The keyboard click is the oldest example, press a key and three channels of feedback arrive simultaneously: the click, the slight resistance giving way, the character appearing on screen.
The principle holds at every scale from there: a button that visually depresses on click, a progress indicator that appears when a form is submitted, an animation that confirms a file has been moved into place. Each of these is a small act of communication between the product and the person using it.
Labour perception bias adds a useful dimension here; Research suggests that users tend to value a process more when they can perceive effort being made on their behalf, even when the actual processing time is minimal. A brief loading animation, a transition, a confirmation screen - these do not just inform, they communicate that something meaningful has happened. The user who sees nothing after clicking "submit" is not simply uninformed; they are anxious, and anxiety is the enemy of trust.
Visibility, mapping, feedback: a sequence, not a list
What makes these three principles worth understanding together is that they describe a sequence. Visibility determines whether an interaction begins at all; mapping determines how confident the user feels whilst engaging with it; feedback determines whether they feel certain it is complete. A product that fails at any point in the chain breaks the user's sense of control.
Consider what happens when visibility is poor but mapping and feedback are strong: the user eventually stumbles onto the feature, and once there everything works clearly, but they had no path to it - a capable product that feels opaque. Contrast that with a product that is highly visible but provides confusing mapping: the user can see everything but nothing makes sense to act on - an overwhelming product that fails to guide. Feedback problems tend to produce the most acute anxiety, because the interaction felt right and the mapping was clear, but there is no signal that it worked; the user tries again, duplicates their action, or gives up.
Don Norman, whose model of human-computer interaction underlies much of this thinking, described the "gulf of evaluation" - the gap between what the system does and what the user can perceive - and the "gulf of execution" - the gap between what the user wants to do and what the system allows. Visibility and mapping work primarily on the execution side, helping users understand what is available and how to act on it; feedback closes the evaluation gap, confirming that the action and the result correspond. A product that bridges both gulfs consistently is not merely usable; it is one that users feel in control of, and that feeling is what keeps them coming back.
In Summary
The three principles don't add up to a checklist so much as they form a set of recurring questions: can the user see what is there? Does acting on it make sense? Do they know what happened? Asking those questions at every step of a flow - not just at design review, but as an instinct that shapes decisions throughout - is one of the more reliable ways to keep a product honest about what it actually asks of the people using it.
