Design Feedback Loops
Feedback & States · feedback
Updated 2026-07-28
- Every user action creates a question:
- Did it work?
- What changed?
- What happens next?
- Close the loop:
- Click → response.
- Upload → progress.
- Save → confirmation.
- Error → recovery.
- Missing feedback creates uncertainty.
- Too much feedback creates noise.
- The goal is confidence:
- Enough information to understand.
- Not enough to distract.
- Great interfaces constantly reassure users that the system understands them.
- Every action should create a response.
- A feedback loop has three parts:
Action:
Response:
Understanding:
- Feedback can be:
- Visual.
- Audio.
- Motion.
- Text.
- No feedback creates uncertainty.
- Fast feedback creates trust.
Related guides