A user taps a 'Submit' button on a mobile form. Nothing visually changes for 1.2 seconds while the server processes the request. What is the most significant design problem this creates?
AThe loading time is too slow — server response should be optimized before launch
BThe button lacks sufficient visual contrast, making it hard to locate on the screen
CThe absence of immediate feedback creates uncertainty about whether the tap registered, likely causing duplicate submissions or abandonment
DThe form needs better error validation to prevent server delays on submission
Feedback must be immediate — within roughly 100ms for users to feel that the system responded. At 1.2 seconds with no visual change, users cannot tell whether their tap registered. The natural response is to tap again (duplicate submission) or assume something is broken and abandon. Even a subtle change — the button graying out, a loading spinner, a haptic pulse — closes this uncertainty gap immediately. Server speed is a separate concern from the feedback design problem.
Question 2 Multiple Choice
An app shows a full-screen confetti animation every time a user checks off any item on a to-do list. Which feedback design principle does this most clearly violate?
AImmediacy — the animation takes too long to appear after the action
BClarity — the animation doesn't explain in text what was completed
CProportionality — the weight of the feedback is far greater than the weight of the action
DConsistency — the same animation should not be reused for every item
Proportionality requires feedback intensity to match action significance. Checking off a to-do item is a minor, routine action — it warrants a minor response like a strikethrough or checkmark. A full-screen animation treats a trivial action as a major event, which becomes annoying and disruptive through repetition. Proportionality scales from subtle (hover states, focus rings) to substantial (confirmation dialogs for irreversible actions like account deletion).
Question 3 True / False
A button currently processing a server request should look identical to its default state so users aren't confused by intermediate states.
TTrue
FFalse
Answer: False
Interactive elements should communicate all meaningful states, including loading/processing. An unchanged button during server processing leaves users uncertain whether their action was received, prompting duplicate submissions. The loading state — a spinner, disabled appearance, or progress indicator — closes this communication gap. Well-designed buttons communicate at minimum: default, hover, active/pressed, disabled, and loading states. Each state serves a distinct communicative function.
Question 4 True / False
Feedback design is primarily an aesthetic concern — it improves how an interface looks and feels, but does not fundamentally affect whether users can accomplish their goals.
TTrue
FFalse
Answer: False
Feedback design is a structural requirement for any interactive system. Without feedback, users cannot know whether their actions had any effect. When a 'Submit' button produces no response, or a success message appears for a failed operation, users cannot accomplish their goals reliably — they retry unnecessarily, lose confidence, and abandon tasks. The deeper purpose of feedback is building trust: consistent, predictable responses make the interface feel reliable. Inadequate feedback is a functional failure, not a cosmetic one.
Question 5 Short Answer
A password input field shows only a red outline when the user enters an invalid password. Explain why this feedback is insufficient and describe what effective error feedback would include.
Think about your answer, then reveal below.
Model answer: A red outline indicates that something is wrong but doesn't explain what is wrong or how to fix it. Effective error feedback must be clear — it communicates not just that failure occurred but its nature and the path to resolution. An effective version includes the visual indicator plus a specific message such as 'Password must be at least 8 characters and include one number.' Without the message, users must guess the requirement and cycle through failed attempts. Clear error feedback is actionable: it empowers the user to correct the problem rather than leaving them stuck.
This question targets the 'clear' principle of feedback design. Clarity means feedback communicates enough for the user to understand what happened and what to do next — not just that something happened. An error state that only signals failure without explaining it satisfies 'immediate' and 'proportional' but fails 'clear,' making the feedback incomplete.