Definition
Feedback is the system’s way of communicating what’s happening to the user. Every action should have a visible, audible, or tactile response so users know the system has received and is processing their input.
Why It Matters
Without feedback, users feel lost or anxious. They may repeat actions unnecessarily, make mistakes, or abandon tasks. Clear feedback builds confidence, reduces errors, and improves overall satisfaction.
Example – Good vs. Bad
- Good: When uploading a file to Dropbox, a progress bar clearly shows upload status and completion. Users know it’s working.
- Bad: Clicking “Save” in a document editor produces no visible response. Users aren’t sure if their work was saved, leading to repeated clicks or panic.
Do’s
- Show immediate feedback for every user action (button press, form submission, drag-and-drop).
- Use visual cues (progress bars, checkmarks), auditory cues (beeps, notifications), or haptic feedback where appropriate.
- Communicate errors clearly with actionable messages (“Username already taken” instead of “Error 42”).
- Provide confirmation for irreversible actions (“Are you sure you want to delete?”).
Don’ts
- Don’t leave long processes invisible — users assume failure.
- Don’t show vague or technical messages (“Fatal error”) without explanation.
- Don’t overload feedback with unnecessary animations or notifications.
Key Takeaway
Users should always know what the system is doing. Feedback turns uncertainty into trust, guiding them smoothly through every interaction.
