Skip to content
UX Atlas
Plate PRIN·004 · PrincipleGrid A2 · Rev. 2026-08-14

Feedback

Every action needs a perceivable response that says it was received and what it did.

PrincipleExpert heuristicFoundational

Definition

One of Don Norman's core design principles. Feedback is the immediate, informative return of information about the result of an action. It must be immediate, informative, and proportionate to the significance of the action.

Expert heuristic. A review criterion developed by practitioners. Useful and widely taught, but evaluated by judgement rather than measurement.

On this plate
  1. 1Definition
  2. 2Feedback has layers
  3. 3Matching the feedback to the action
  4. 4In practice
  5. 5Local chart
  6. 6Sources
  7. 7Continue from here

Reach for this when

  • Specifying states for any interactive component.
  • Designing drag, resize or other continuous interactions.
  • Reviewing a flow where users repeat actions because they are unsure they worked.
  • An action has a consequence the reader cannot see from where they are standing.

Common mistakes

  • Missing focus states, which breaks keyboard use entirely.
  • Feedback that appears far from the action.
  • Success messages for operations that have not completed.

Feedback has layers

  1. 1.Input acknowledgement: the control shows it received the press, within about 100ms. Usually a state change on the element itself.
  2. 2.Process indication: something shows work is happening, if it takes long enough to notice.
  3. 3.Outcome: the result is visible, and the interface reflects the new state.
  4. 4.Consequence: any secondary effects are legible, such as a counter updating or an item appearing in a list.

Do

  • Give every interactive element visible hover, active, focus and disabled states.
  • Change the thing that changed, so the outcome is visible in place.
  • Match feedback intensity to consequence: subtle for routine, prominent for significant.
  • Announce non-visual feedback to assistive technology.

Do not

  • Rely on a toast alone for an important outcome.
  • Give the same feedback for success and failure.
  • Animate feedback so slowly that it becomes the wait.
  • Use sound or haptics as the only channel.

Matching the feedback to the action

Feedback that is louder than the action it reports is noise, and feedback quieter than the action is missing.

ActionFeedback that fits
Toggling a settingThe control moves, and nothing else
Saving a draftA quiet, persistent saved indicator with a time
Sending a messageThe message appears, with a pending state until confirmed
Deleting one itemThe row leaves, and an undo stays for a few seconds
Deleting forty itemsA summary of what happened, and what it affected
A background jobA place to check progress, and a notification on completion

In practice

  1. i.

    Drag and drop target highlighting

    File and board interfaces

    Highlighting the valid drop zone as the drag begins is feedforward. Animating the item into place is feedback. Without the first, users drop into the wrong place and rely on undo.

  2. ii.

    Live order totals

    Checkout

    Updating the total as shipping options change removes a surprise at the final step, which is where surprises are most expensive.

  3. iii.

    The button that did nothing visible

    Missing acknowledgement

    An export button started a job on the server and changed nothing on screen. People pressed it repeatedly, which produced four identical files and a support ticket about duplicate exports.

Local chart

PRIN·004 · Region I · Grid A2

This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.

ToastCMP·014 · APPLIED THROUGHToggle SwitchCMP·007 · APPLIED THROUGHLoading StatesPAT·011 · APPLIED THROUGHOptimistic UIPAT·013 · APPLIED THROUGHMotionFND·052 · APPLIED THROUGHVisual StatesFND·053 · APPLIED THROUGHDesigning an AI Suggestion Feature People Would UseCASE·010 · PRACTICAL EXAMPLEInteraction DesignTERM·034 · SHORT DEFINITIONMicrointeractionTERM·035 · SHORT DEFINITIONFocus IndicatorsA11Y·003 · RELATED CONCEPTHelp Users Recognise, Diagnose and Recover From ErrorsHEUR·009 · RELATED CONCEPTVisibility of System StatusHEUR·001 · RELATED CONCEPT

Sources

Where a source establishes something narrower than the popular reading of it, the note says so.

  1. [1]

    The Design of Everyday Things

    D. A. Norman, Basic Books, 1988, revised 2013

Continue from here

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Applied through

Where this shows up as a concrete interface decision.

Practical example

A worked decision where this was the deciding factor.

Short definition

The one-paragraph version, for when that is all you need.

Related concept

Connected closely enough to change how you apply this.