Feedback
You press the button. Nothing lights, nothing clicks. So you press it again — and again.
You know it’s a control, and you know which one to press — Modules 1 and 2. Now the quietest question of all: did anything happen? Every button, every tap, every ‘submit’ owes you an answer. When it stays silent, you can’t tell success from failure — so you jab it again, or give up, or break something twice.
Feedback is the system telling you what it just did. Do it well and a single flicker turns doubt into trust. Do it badly — too slow, too quiet, or too loud — and people over-press, panic, or stop believing the interface at all. You’ll feel that on a dead lift button, then a silent wait, then an interface that will not stop shouting.
- See why a control with no feedback makes people over-act, doubt, and quietly blame themselves.
- Match feedback to the wait: instant for a tap, progress for anything slow — the Gulf of Evaluation.
- Feel why too much feedback is the same as none — noise you learn to tune out.
- Put feedback where the action is, and make it proportionate to what just happened.
The dead button
You press the lift button. Nothing lights, nothing clicks. Did it register? You press again. And again. This is the most common feedback failure alive — a control that works but never says so. In the silence you assume it didn’t hear you, so you over-act.
Call the lift on both. First the silent button, then one that answers with a single flicker. Feel how silence makes you jab, and one flicker makes you trust.
The silent wait
One press earns one flicker. But what about the seconds after — while the thing actually happens? You tap ‘Send,’ and now… nothing. Is it uploading? Did it freeze? Should you tap again? That anxious gap between what the system is doing and what you can see has a name: the Gulf of Evaluation.
Send the same photo twice — once into silence, once with a bar that shows every step. Same four seconds, opposite feelings.
The screaming interface
So more feedback is always better? No. When every icon badges, every action toasts, and everything buzzes at once, the signal drowns in its own noise — and you learn to ignore all of it, including the one alert that actually mattered.
Your payment just failed. Find that alert — first in an app where everything screams, then in one that speaks only when it must.
Good feedback is immediate, honest, and quiet
Feedback sounds like a nicety until you meet a system that withholds it. Named clearly, it is one of the quiet forces that decides whether a product feels alive in your hands or dead.
Every action deserves an answer.
The first rule is immediacy. A control must react the instant you touch it — a press-state, a highlight, a click. Under about a tenth of a second it feels instant; past that, doubt creeps in. If the real work takes longer, acknowledge the touch now and report progress as it goes.
The second is honesty and information. Feedback should say what actually happened, not just that something did. ‘Sent’ beats a shrug; ‘Uploading 60%’ beats a bare spinner; ‘Card declined — check the expiry’ beats a red box. The slower or more consequential the action, the more the feedback must explain.
The third is proportion and place. Match the signal to what matters — a whisper for the routine, a clear alarm for the rare emergency — and never let everything shout, or people go deaf to all of it. And put the response where the action was: the error by the field, the confirmation by the button, the change on the thing that changed.
So the working test is a question: after every action, could the user answer “did it work, and what happened?” without guessing? The closer to yes, the more the interface feels like a conversation — and a conversation is a thing people trust.
Which feedback is clearer?
Five face-offs. Same moment, two responses — one leaves you guessing, one tells you exactly what happened. Pick the clearer, then see why.
Feedback done right
Good feedback is almost invisible — you only notice it when it is missing. Here are two you rely on without a thought.
A small ‘Saved’ that appears and fades. It never blocks you, but it answers the only question you had: did that work? Silence would have left you re-checking.
A spinner says only ‘working.’ A bar says how far and how long — so a four-second wait feels like a countdown, not a freeze.
Feedback tells you what happened. But why did you expect something else? Because you were running a story of how the thing works — and when that story is wrong, feedback alone won’t save you. That is the next bridge: conceptual models, the story a design puts in your head, and how to make it the right one.
The real references
Feedback and system status are among the oldest, best-studied ideas in the field. Four worth your time. (Opens in a new tab.)
The Feedback glossary
Six words that turn “this feels unresponsive” into a precise fix. Tap a card to flip it.
Questions you actually ask
What people get wrong
Read the feedback
Ten questions in seven formats, tagged by thinking level — each with layered hints: a nudge, the reasoning, then a deeper connection. A wrong answer opens a door, never a dead end. Served from the question bank, never hardcoded.