Feedback

Immediate, informative communication of the result of an action. In the design sense this is distinct from the systems sense of feedback loops: here it means telling the user what just happened. Every action should produce a perceptible, timely response.

Why it Matters

Without feedback, people cannot tell whether an action registered, so they repeat it, give up, or make errors. Feedback closes the loop between acting and understanding the result. Nudge lists "give feedback" as a core tool of choice architecture: telling people how they are doing (an energy bill that flags unusual use, a warning before an irreversible step) steers behavior without removing any option.

Signals

• Users press a control twice because nothing visibly happened.
• Uncertainty about whether the system is working; long silent waits.

Benefits

Confidence, fewer repeated or erroneous actions, and a sense of being in control.

Risks

Too little feedback (silence) or too much (constant alerts that get ignored); feedback so delayed it no longer connects to the action; uninformative feedback like a bare error code.

Tensions

Enough feedback to inform versus so much it becomes noise. Feedback must be prioritized by importance, or the signals that matter drown.

Examples

A button that visibly depresses and clicks; a spinner during a load; a confirmation that a message was sent.