Usability asks whether the task is achieved; experience covers all feelings before, during, and after use

What it is

The dividing line is the object of attention: usability watches the task—can the target user achieve the goal smoothly; experience watches the person—every feeling, judgment, and memory from before the need arose to long after use. The task is one input to experience, but experience's ledger runs far longer than the task.

Why it happens

The split comes from different units of evaluation: usability evaluates "task × performance" and can be measured in isolation from the rest of a person's day; experience evaluates "product contact within a stretch of life," and the same interface feels different on an anxious morning and a lazy weekend. Usability conclusions need no out-of-use variables; experience conclusions are shaped mainly by them—how expectations formed, who it was told to afterward, whether it's remembered next time. Shrinking experience into the task frame systematically drops the before-and-after entries of the ledger.

Studying it

Run two toolkits for two objects: task-based testing for usability (performance metrics, problem lists), efficient under controlled conditions; longitudinal and ethnographic methods for experience—diary studies, home visits, pre/post interviews, long-run behavioral data—covering where expectations came from and what memory kept. Methodologically, stop the toolkits from impersonating each other: task tests cannot conclude about experience (insufficient validity), and interviews cannot localize usability problems (insufficient granularity).

Where it stops holding

The line is a perspective, not a territory: both study the same interaction. Usability failures almost always post entries to the experience ledger, and a poor experience feeds back into task performance (anxiety degrades precision). For pure high-frequency tool products, the task dimension carries more of experience's weight and the practical gap narrows; for leisure, identity, and social products, the beyond-task ledger dominates.

Applying it

• Keep two question lines in every project: a "task line" for can-it-be-done and how-fast, and an "experience line" tracking expectations, key emotions, and after-the-fact verdicts.
• Schedule and budget usability tests and experience research separately, with separate deliverables (problem list versus feeling map).
• Triage by line before prescribing: can't find the button is task-line; "it feels unpleasant" is experience-line—the treatments differ.

Related

• Same group: B5.11.2 Experience includes expectation, brand, and social context, most of which the interface does not control · B5.11.3 Under some experience goals, deliberate inefficiency is correct design, in direct conflict with usability goals · B5.11.4 Experience cannot be measured directly through task performance the way usability can; it is only inferred
• Nearby: B5.05 Experience versus usability · P1 Emotional Design
• Search terms: ux vs usability · holistic experience · task performance