Feedback explained
Feedback makes visible what the system did after an action or what state it is in. Success messages, progress indicators, and useful error text are different forms of feedback. Useful feedback appears at the right time, near the action, with enough detail to support the next decision. It communicates progress during a process, the result afterward, and a recovery path if something fails.
Why it matters.
A silent interface creates uncertainty. Clear, timely information helps people know whether to wait or what to do next. Missing feedback can lead to repeated clicks, duplicate actions, or fear of lost work. Too many alerts hide important messages, so the form should match the message's importance.
Let's look at an example.
Think of saving a file.
Showing ‘Saving…’ followed by ‘Saved’ means people do not have to repeat the action to check whether it worked. If saving fails, a generic Error message is not enough; explain how to retry. If the draft remains safe locally, say so as well.
How to apply it.
- 01
Define waiting and result states for important actions.
- 02
Explain what went wrong and how to recover in error messages.
- 03
Show feedback close to where the action happened.
“Silence often feels like uncertainty to users.