Acknowledge every user action.
Ensure all meaningful actions produce visible system responses.
Contents 3. Interaction Mechanics & Agency 4. Feedback
How action is confirmed.
First, ask yourself
“Does your system acknowledge users’ actions promptly and truthfully?”
Mission statement
Ensure users understand outcomes by providing timely and clear responses.
Key heuristics Feedback
- Every meaningful user action must produce a visible system response.
- Acknowledgment must occur without delay.
- Feedback must indicate that user intent was understood and accepted.
- Feedback must communicate what changed, not merely that activity occurred.
- Feedback must clarify what was affected before and after execution.
- Distinct outcomes must produce distinct feedback signals.
- Feedback must represent state accurately and proportionally.
- Essential feedback must remain visible until resolved.
- Feedback must include clear next steps when errors occur.
Executive brief
The system must acknowledge actions clearly and respond in ways users can trust.
Core questions Feedback
“Does the system acknowledge actions clearly, quickly, and accurately?”
“Can users understand and rely on what happened?”
Focus areas
Timing-first
“Was the system’s response immediate?”
“Was there any doubt about whether the action succeeded?”
Meaning-first
“Does feedback explain what actually happened?”
“Can users distinguish success, partial success, or failure?”
Trust-first
“Is uncertainty communicated honestly?”
“Does feedback ever mislead by omission?”
AI-aware
“Is the system’s confidence proportional to its certainty?”
“Does feedback distinguish guesses from facts?”
UX directives Feedback
Provide immediate acknowledgment.
Respond to actions without delay to prevent duplicate input and uncertainty.
Confirm user intent explicitly.
Indicate the system understood and accepted the intended action.
Ensure feedback conveys meaningful outcome.
Communicate what changed or occurred, not merely that activity happened.
Make scope and consequence explicit in feedback.
Clarify what was affected before and after execution.
Differentiate feedback by outcome.
Use distinct signals for success, partial completion, warning, and failure states.
Ensure feedback is accurate and proportional.
Prevent conveying false accuracy or overconfidence.
Persist critical feedback until resolved.
Do not allow essential information to disappear prematurely.
Provide recovery guidance within feedback.
Offer clear next steps when errors or exceptions occur.
Executive summary
- Feedback is visible system response, not mere activity indication.
- It confirms that user intent was received and what outcome occurred.
- The system must acknowledge every meaningful action immediately and proportionally.
- Feedback must make scope, consequence, and state change explicit.
- Critical signals must persist and differentiate success, warning, and failure clearly.
- Feedback succeeds when users understand what happened, why it happened, and what to do next.
Success indicators
- Every user action receives a visible response.
- The system responds immediately to user input.
- Feedback clearly shows what changed or happened.
- Different outcomes are clearly distinguished.
- Feedback remains visible until the user understands the result.
One-line summary
Before users can trust their actions, they must know what the system did in response.