Diagnose and validate a failing usability task

WHAT THIS TESTS The interviewer wants to see you treat a usability failure like any defect: localize, hypothesize, fix, and verify, rather than reacting with an opinion-driven redesign.

A GOOD ANSWER COVERS Start by localizing the failure precisely. Watch the session recordings to see exactly where users hesitate, click the wrong thing, or abandon, and corroborate with event telemetry such as a funnel showing the step with the steepest drop-off. Classify the failure type: is it discoverability (they cannot find the control), comprehension (they misunderstand the label or state), interaction (the control is fiddly or error-prone), or feedback (they cannot tell if it worked). From that, form a specific root-cause hypothesis instead of guessing. Design a targeted change that addresses the identified cause, keeping the change small enough to attribute its effect. Then validate: run another moderated usability round to confirm the qualitative problem is gone, and measure task success rate and time, ideally via an A/B test against the old version, watching for unintended regressions elsewhere.

COMMON WRONG ANSWERS Proposing a full redesign before knowing where users fail. Trusting subjective opinions over observed behavior and telemetry. Changing several things at once so you cannot tell what helped. Declaring victory from a single happy demo rather than measuring task success.

LIKELY FOLLOW-UPS How many participants do you need to trust the finding. When do you use qualitative testing versus an A/B test. How do you separate a UX problem from a performance bug. How do you guard against fixing one step and breaking another.

ONE CONCRETE EXAMPLE Users failed to apply a discount code. Recordings showed they never found the collapsed code field, and telemetry confirmed near-zero clicks on it. The hypothesis was discoverability, not comprehension. The fix surfaced the field by default. A follow-up test plus an A/B comparison showed code-application success rising substantially with no drop in checkout completion.