Under some experience goals, deliberate inefficiency is correct design, in direct conflict with usability goals

What it is

Usability's direction is removing obstacles, but some experiences depend on obstacles: a game's difficulty, a puzzle's sticking points, the time a handwritten card takes, the ritual of unwrapping. In these contexts, the smoother the task, the less the experience is worth—deliberate friction is correct design, not a usability defect.

Why it happens

The conflict comes from where value lives: in tool contexts value sits in the output and the process is a cost, so shorter is better; in experience contexts value lives in the process itself (mastery, growth, ritual, suspense), and compressing the process evaporates the value with it. Slow and hard are content there, not friction—difficulty manufactures achievement, waiting manufactures anticipation. Usability measurement's default assumption—output fixed, smoother path better—fails wherever value is endogenous to the process, and the metrics systematically rank wrongly.

Studying it

Judging whether a friction is deliberate takes an evidence chain: the value hypothesis (what experience goal the friction serves) → motivation segmentation (who comes for the process) → friction calibratability (whether difficulty stays within the user's zone, balancing frustration against achievement). Measure with intent metrics instead of efficiency: replay rates, whether recommendations mention the process, and where quitting points fall along the difficulty curve. Out-of-control frustration and designed challenge leave different signatures—quits cluster near the skill ceiling in the latter, scatter uniformly or pile up at the start in the former.

Where it stops holding

Deliberate inefficiency holds only under strict conditions: the friction must be intelligible (users know why it's hard), conquerable (a path to getting stronger exists), and in service of a goal users endorse. Imposing friction on tool tasks is nearly always wrong—when users have no alternative, friction is not experience but exploitation (a deliberately buried cancel button is a dark pattern, not friction design). Where both values coexist in one product (layer operations are tools; the color-grading process is experience), friction must be placed precisely by task segment.

Applying it

• Tag every flow's value type up front: output-type (remove all friction) or process-type (keep and tune the friction).
• In process-type flows, make difficulty explicit and adjustable—difficulty picks, skip rights, assist toggles—keeping challenge inside the user's controllable band.
• Evaluate process-type experiences by quit-point distribution, not average duration: quits clustering near the difficulty ceiling is healthy; uniform scatter or early pile-up means the challenge is out of control.

Related

• Same group: B5.11.1 Usability asks whether the task is achieved; experience covers all feelings before, during, and after use · B5.11.2 Experience includes expectation, brand, and social context, most of which the interface does not control · B5.11.4 Experience cannot be measured directly through task performance the way usability can; it is only inferred
• Nearby: W1 Game interaction and skill expression · B4.16 Instrumental versus agentive interaction
• Search terms: deliberate friction · desirable difficulty · dark patterns