Make the interface answer: did it work?
Design feedback states that keep users oriented during system work.
The move: design action feedback as a state sequence. Nielsen Norman Group's visibility-of-system-status heuristic says users should know what is going on. The practical UI question is simple: after every important action, can the user tell whether the system heard them, whether it is still working, and what happened next? The right feedback depends on stakes. A low-risk filter change may only need an immediate visual update. A destructive permission change needs stronger feedback: disabled button while saving, explicit success, audit detail, and recovery. The more expensive the uncertainty, the more explicit the state should be. Do not rely on…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in