UX/UI Design: Foundations to Practice · Interaction Design
System Status and Feedback
A person interacting with a digital product has no way of knowing whether their action actually registered unless the system explicitly tells them, and the specific timing and clarity of that feedback shapes whether they trust the product at all.
When a person taps a button or submits a form and receives no visible response within a reasonable, expected amount of time, they cannot distinguish this silence from genuine failure, and in the absence of any feedback, people generally assume the more troubling explanation, that their action did not register at all, often leading them to repeat the action, sometimes multiple times, in a way that can itself cause a genuine error, such as an accidental duplicate submission.
- When no feedback follows an action within a reasonable time, people assume the more troubling explanation, that it failed, often leading them to repeat the action and cause an error.
- Feedback should match an action's actual timescale; a static loading spinner for a multi-minute process leaves someone just as uncertain as no feedback at all.
- Staged feedback for a longer process helps calibrate expectations about remaining time and reassures that progress is actually being made.
- Products often under-invest in clearly confirming success compared to clearly communicating error, leaving people uncertain and prone to unnecessary repeated actions.