Affordances are qualities of objects that suggest how they should be used; a button 'affords' clicking. Signifiers are perceptible cues that communicate this affordance to users. Effective design makes affordances obvious through visual language—color, shape, texture, and positioning—so users know what actions are possible without explicit instructions.
Analyze real-world objects (door handles, light switches, keyboards) and identify affordances and signifiers. Then apply these insights to digital interfaces by auditing whether buttons, links, and interactive elements are immediately recognizable as clickable.
With your foundation in visual perception and communication, you already understand that humans do not passively receive visual information — they actively interpret it based on learned patterns and environmental cues. Affordances and signifiers are where that perceptual process meets design intent: they are the mechanisms through which objects and interfaces tell you what to do with them, often without a single word of instruction.
An affordance is a relationship between an object and a person — specifically, the actions that the object makes possible for that person. A flat plate on a door affords pushing; a handle affords pulling; a chair affords sitting. Crucially, affordances exist whether or not the user perceives them. A button on a screen affords clicking even if the user does not realize it is a button. This distinction matters because it separates the question "what can be done?" from the question "does the user know what can be done?" The first is about affordance; the second is about something else entirely.
That something else is the signifier — a perceptible cue that communicates the presence of an affordance. A raised, shadowed rectangle on a screen signifies "this is a button you can click." An underlined blue word signifies "this is a link you can follow." A handle's shape signifies "grip me and pull." The signifier is what bridges the gap between what the object can do and what the user understands it can do. Don Norman, who developed these concepts, eventually argued that signifiers are more important to designers than affordances themselves, because designers cannot control what affordances exist in the physical world — but they can control what signals they put in front of users. A door with a flat plate is well-signified: the plate tells you to push. A door with an identical handle on both sides is poorly signified: the handle says "pull," but one side requires pushing, leading to the embarrassing fumble that Norman famously called a "Norman door."
In digital interfaces, the stakes are even higher because there are no physical constraints to guide behavior. A physical door has only two possible actions — push or pull — but a screen full of elements could have dozens of interactive possibilities. Visual signifiers do the work that physical form does in the real world: drop shadows suggest a button is raised and pressable; a cursor changing to a pointer hand signals clickability; a text field with a blinking cursor invites typing. When these signifiers are missing or ambiguous — a link that looks like plain text, a button that looks like a label, an interactive card with no hover state — users hesitate, guess wrong, or miss functionality entirely. The cost of poor signification is not just confusion; it is lost trust and abandoned tasks.
The practical design principle is straightforward: for every affordance you build into an interface, ask whether the signifier is strong enough that a first-time user will understand the action without instruction. If you find yourself needing to add a tooltip, a label, or an onboarding tutorial to explain what something does, that is often a sign that the signifier has failed. The best-designed objects — both physical and digital — feel obvious. That obviousness is not accidental; it is the result of signifiers that are so well-matched to users' existing mental models that the affordance seems to announce itself.
Topics in reflective domains aren't scored by quiz answers. Read, reflect, and mark when you've thought it through.