B2.06.1Feedbackdesignresearch

Every action needs perceptible information about its result

Aliases: feedback · action outcome · state return

What it is

Feedback is perceptible, interpretable information that a system provides after a person's action. It can confirm that an action was received, show a change in object or process state, explain failure, or indicate that processing continues. Without feedback, people cannot reliably distinguish “nothing happened,” “it is happening,” and “it happened somewhere out of sight.”

Why it happens

Interaction is a continuing action–interpretation loop: people act, then update their understanding of system state and next steps from environmental change. Visual change, sound, haptics, text, and progress can all return information, but must connect intelligibly to the preceding action and task context. When a result occurs far away, is obscured, or has no salient change, the mental model does not update and people may repeat action or take a wrong path.

Studying it

In real tasks, record whether people pause, repeat, ask, or search for confirmation after acting, then ask what state they believe the system is in. Compare state-judgment accuracy, repeated action, and completion quality under different feedback forms, locations, and content. Include conditions with limited visual, auditory, or tactile channels to verify that important outcomes remain equivalently available.

Where it stops holding

Not every tiny internal change deserves a separate interruption; frequent, reversible, immediately visible actions can use lightweight feedback. Conversely, a changed page is not automatically effective feedback: if it cannot answer whether an action succeeded, what resulted, or what comes next, it is merely animation or decoration. Feedback also cannot replace clear initial signifiers and constraints.

Applying it

  • Define the state each meaningful action must communicate: received, processing, success, partial completion, failure, or user action required.
  • Associate feedback with its trigger and result location, using in-place change, a concise summary, or highlighting so it can be found easily.
  • Provide more than one perceptible channel for critical state, and test whether people can state the current condition without guessing.

Related

  • Same group: B2.06.2 Feedback must be timely; delay is attributed to nonresponse · B2.06.3 Feedback intensity should match action importance · B2.06.4 Excessive feedback is actively ignored
  • Nearby: B2.05 Constraints · B2.07 Consistency
  • Search terms: feedback · system status · action outcome

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/B2.06.1