Why a product needs to explain itself
A person approaching an unfamiliar product has three immediate questions: What can I do with it? Where should I act? Did my action work? A well-designed product answers these questions through its form and behavior, rather than relying entirely on instructions. This matters for a door handle, a phone app and a household robot alike.
Three useful ideas help explain how that happens. An affordance is an action that a product makes possible for a particular user: a handle can be grasped, for example. A signifier is a perceptible clue about where or how to act, such as a label beside a control. Feedback is the response that lets the user know what happened. The three work together, but they are not interchangeable. A control may be usable yet hard to notice, or easy to notice yet unclear after it is pressed.
Affordances: start with what people can do
Physical objects often suggest actions through their shape. A broad plate on a door invites a push; a protruding handle offers a place to pull. The action is not universal, though. A handle that is easy for one person to grip may be difficult for someone wearing gloves or with limited hand strength. Considering different users and settings helps designers avoid treating a familiar shape as an explanation that works for everyone.
On a touchscreen, the glass itself does not physically offer a separate button at every point. The interface has to establish which regions respond to a tap, swipe or drag. Designers can make common actions reachable and consistent, while avoiding gestures that users must discover by accident. In a prototype for a new device, an early test can be simple: ask someone who has not seen it before what they think they can do, then watch where they try to act. The gap between intention and behavior is often more informative than a polished demonstration.
Signifiers: make the next step visible
A signifier points people toward an action. It might be a raised edge around a button, a word such as “Open,” or a visible grip on a removable panel. Clear signifiers reduce the need to guess. They are especially valuable when a product combines several functions in a small space, as many consumer devices do.
Appearance alone can also mislead. A glossy circle might look like a button but do nothing; a touch-sensitive surface might have no visible boundary at all. If a user repeatedly presses the wrong place, the problem may not be a lack of skill. The product may be sending the wrong signal. Labels should name the action or outcome in language the intended audience understands, rather than using an icon whose meaning depends on prior experience. For important controls, combining a label with shape or position can give users more than one way to find their bearings.
Feedback: confirm the action and the result
After someone acts, the product should respond in a way they can perceive. A mechanical switch may click; an app may show that a setting changed; a device may display its charging status. Without feedback, people may repeat an action, wonder whether the product is working, or leave before a task is complete. Feedback should arrive at the right moment and relate clearly to the action just taken.
A response should also distinguish progress from completion. If a smart appliance receives a command but needs time to carry it out, showing that it is working is different from claiming the job is done. If an action fails, a useful message says what went wrong in ordinary language and offers a reasonable next step when possible. Sound, light and vibration can reinforce one another, but none is reliable for every person or setting. A quiet room, bright sunlight or a user’s sensory needs may change which signal is most useful.
Putting the principles together
Imagine a small home robot designed to carry items between rooms. Its carrying tray provides an affordance: a person can place an object on it. A contrasting edge and a short label could signify where an item belongs. A light or message could then confirm that the robot detected the load and is ready to move. If it cannot proceed, it should indicate that state rather than silently waiting. This is an illustrative design scenario, not a claim that any particular robot works this way.
The same questions apply when reviewing an existing product or sketching a new one: Can the intended user perform the action? Can they tell where and how? Can they tell what happened afterward? Watching people attempt a task without coaching can reveal mismatches among those answers. Improving a product may mean changing its shape, adding a clearer cue, or making its response more specific. Good usability is not about making every product look simple; it is about making the next useful action and its consequences understandable.
