Feedback
A system response that shows an action was received, what changed, and what can happen next.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/feedback/
01What it means
Feedback is the information a product returns after user input or a system event. It can confirm progress, success, failure, selection, status, or consequences through visual, auditory, or haptic signals.[1][2]
02Why it matters
Without timely feedback, people repeat actions, abandon tasks, or build the wrong explanation of system state. Clear feedback closes the action loop and supports confidence, recovery, and learning.
03When to use it
Use feedback for every meaningful action, especially asynchronous operations, destructive commands, validation, mode changes, selections, and background updates.
04How it works
- Acknowledge input promptly, even when processing will take longer.
- Communicate the current state in language appropriate to the user.
- Match prominence and persistence to the consequence of the event.
- Offer recovery or a next step when the result is not successful.
- Ensure status changes are available to assistive technologies.
05A practical example
After a user uploads a large file, the product immediately shows the file name and progress, then announces completion. If the upload fails, it preserves the selection and offers a specific retry action.
06Where it breaks
Too much feedback becomes interruption. Animation, sound, vibration, and alerts should not compete for attention unnecessarily. Feedback also cannot rescue an action whose outcome or wording was unclear in the first place.
Common mistakes
- Showing a spinner with no explanation or progress expectation.
- Using a transient toast for information the user must remember or act on.
- Changing state visually without exposing the update to screen readers.
- Confirming receipt while hiding whether the operation actually succeeded.
07Sources
- The Design of Everyday Things, Revised and ExpandedBasic Books / Don Norman · bookThe Design of Everyday Things, Revised and Expanded
- Understanding Success Criterion 4.1.3: Status MessagesW3C Web Accessibility Initiative · standard guidanceUnderstanding Success Criterion 4.1.3: Status Messages