Marcus Andrey Study
Ler em português Library

UX Foundations · Step 5 · 6 min read

Affordances, signifiers and feedback

Why some things feel obvious to use and others need a sign. Affordances, signifiers and feedback as Don Norman uses them, the famous "Norman door", how a screen shows what can be clicked, and the three response times that decide what feedback people need.

Four slide switches, each with a lamp: every action needs a response. Point at a switch: it slides on and its lamp lights, the feedback that it worked. Illustration: Marcus Andrey, drawn with Hairline (MIT, Lucas Marques).

Every action deserves a response. Before people act, the design has to show them what they can do and where. After they act, it has to show them that something happened. When either half is missing, people push doors that should be pulled, tap buttons twice and wonder if their payment went through. This lesson gives you three words to talk about both halves: affordances, signifiers and feedback.

What you'll be able to do after reading:

  • Explain the difference between an affordance and a signifier
  • Recognise a "Norman door" on a screen and fix it
  • Choose the right feedback for a delay of 0.1, 1 or 10 seconds
  • Use these words in critiques instead of "it feels unclear"

1. Affordances: what you can do

An affordance is what an object lets a person do. A chair affords sitting; a flat plate on a door affords pushing. Don Norman brought the word into design in his book first published as The Psychology of Everyday Things (1988), later The Design of Everyday Things.

Norman later admitted the word was often misunderstood: "I should have used the term "perceived affordance," for in design, we care much more about what the user perceives than what is actually true" (Norman, Affordances and Design, jnd.org). On a screen, almost anything can be clicked, so what matters is what people believe they can do. In his words: "In graphical, screen-based interfaces, all that the designer has available is control over perceived affordances."


2. Signifiers: where and how

In the revised edition of The Design of Everyday Things (Basic Books, 2013), Norman added a second word to fix the confusion: signifiers. Affordances are what actions are possible; signifiers tell people where and how to act. He had already defined it in an earlier essay: "A "signifier" is some sort of indicator, some signal in the physical or social world that can be interpreted meaningfully" (Norman, Signifiers, not affordances, 2008).

A door handle, the word "Push", a button's shadow and an underlined link are all signifiers. On the web, NN/g lists the cues that tell people something is clickable: "borders, color, size, consistency, placement, and adherence to web standards" (NN/g, Loranger, Beyond Blue Links, 2015). The same article warns that very flat designs can strip out those cues, so people can't tell what is clickable.

A glass door with two stickers side by side: one says PULL, the other says PUSH.
When a door needs a sign, its design isn't signalling how to use it. Here the signs contradict each other, so people have to guess. Photo: Robert S. Donovan, edited to blur a company name, Wikimedia Commons, CC BY 2.0.

The Norman door. A "Norman door" is a door whose design sends the wrong signal, so it needs a sign to explain itself. As 99% Invisible put it: a so-called "Norman Door" "has design elements that give you the wrong usability signals to the point that special signage is needed to clarify how they work" (99% Invisible, Norman Doors, 2016). Screens have Norman doors too:

On a door On a screen The fix
A pull handle on a push door Text that looks like a link but isn't Style only real links as links
No handle at all A card that opens on click, with no hint Add a visible cue (a chevron, "View details")
A "Push" sign taped on A tooltip saying "Click the title to edit" Make the title look editable, or add an Edit button
Two doors, only one opens Two identical buttons, one disabled Show the disabled state clearly, and say why

3. Feedback: what just happened

Feedback is the response after an action: the button changes colour when pressed, a message says "Saved", a progress bar fills. It's the first of Nielsen's heuristics: systems "should always keep users informed about what is going on, through appropriate feedback within reasonable time" (NN/g, Harley, Visibility of System Status, 2018).

How much feedback you need depends on how long people wait. Jakob Nielsen's three limits, from his 1993 book Usability Engineering, still hold (NN/g, Nielsen, Response Times: The 3 Important Limits, 1993):

  1. 0.1 sFeels instant

    People feel they are moving things themselves.

    Just show the result
  2. 1 sFlow stays

    People notice the delay but keep their train of thought.

    Over 1 s: show it is working
  3. 10 sAttention slips

    People start to think about something else.

    Show progress and time left
Nielsen's three response-time limits (1993) and the feedback each one needs. Diagram: Marcus Andrey, CC BY 4.0.
Wait What people feel Feedback to give
About 0.1 s "the system is reacting instantaneously" None beyond the result itself
About 1 s The delay is noticed, but the "flow of thought" isn't broken Usually nothing special; over 1 s, show it's working
About 10 s The limit "for keeping the user's attention focused on the dialogue" A percent-done indicator and, if possible, the time left

A worked example. You tap "Pay" in a shopping app. In under 0.1 s, the button should look pressed (feedback that your tap landed). If the payment takes 3 seconds, show a spinner and disable the button so people don't pay twice. If it takes 15 seconds, show steps ("Contacting your bank…") or a progress bar. Then, always, a clear success or error message.


4. Common mistakes

  • Hiding signifiers for a "clean" look: flat text buttons, icons with no labels, swipe-only actions.
  • Making things that aren't clickable look clickable (blue text, underlines, card shadows).
  • Fixing a confusing control with instructions instead of changing the control.
  • No pressed state, so people tap again and trigger the action twice.
  • A spinner for a 30-second task, with no sign of progress or time left.

5. Vocabulary

Term Meaning
Affordance What an object or element lets a person do
Perceived affordance What a person believes they can do with it
Signifier A visible cue that shows where and how to act
Feedback The system's response after an action
Norman door Something whose design sends the wrong signal, so it needs a sign
Response time How long the system takes to respond to an action

6. Try it (no tools needed)

  1. Walk around your home or office and find one Norman door: a tap, a cooker, a door, a remote control. Write what it affords, what signals it gives, and why those signals mislead.
  2. Open an app you use and find three things you can tap. For each, write the signifier that told you so.
  3. Pick one action in the app (send, save, pay) and time it with your phone. Which of the three limits does it hit? Is the feedback right for that wait?

Reflection questions: When did a screen leave you unsure if your action worked? What one change would have told you?


7. If you already practise

  • In reviews, separate the three questions: "Can people tell they can act?" (signifier), "Can they tell where?" (signifier and placement), "Can they tell it worked?" (feedback).
  • Ask developers for real timings of slow actions early; the right loading feedback depends on them.
  • Check every component in your library has visible hover, focus, pressed and disabled states. Those states are signifiers and feedback.

Checklist

Learn more

Books, courses and videos to go deeper

Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

How people think · Interface states: empty, loading, error, success · Forms · Heuristic evaluation · Patterns and when to break them

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close