Make Status Visible Before Users Wonder
Identify where an interface needs visible system-status feedback.
Principle: every consequential action needs visible feedback within the user's patience window. Feedback Answers a Question A spinner answers "is something happening?" A saved state answers "can I leave?" A progress bar answers "how long might this take?" A warning answers "what risk am I about to accept?" Match the feedback to the decision. Timing Matters Immediate feedback confirms input. Delayed feedback explains progress. Final feedback closes the loop. If any beat is missing, users often repeat the action or abandon the task. Specific Beats Generic "Saving..." is better than silence. "Saving pricing rule for EMEA Enterprise..." is better still…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in