Frictional Interface

Definition

Surfaces, interfaces or user experiences that increase the time and space it takes to complete a goal or perform an action.

An example of a frictional interface is a complex parking ticket machine.

Description

Friction, in this sense, is measured in the gap between the simplicity of the user's intention and the complexity of the procedure required to satisfy it. Someone approaching a parking machine wants one thing: to leave a car somewhere for a while without being fined. What they encounter is a sequence of decisions they did not know they would have to make — zone number, duration, payment method, licence plate entry, whether to press the green button before or after inserting coins — each individually defensible, collectively defeating.

Friction Is Usually Accidental

The parking machine is not designed to frustrate. Its complexity is the visible residue of everything behind it: several tariff zones inherited from different municipal decisions, three payment systems added at different times, an enforcement regime that requires a plate number, a hardware platform chosen years earlier, accessibility rules, and a manufacturer's firmware nobody at the council can change. Each requirement was added by someone solving a real problem. None of them were solving the user's problem, and no one was responsible for the total.

This is the general shape of frictional interfaces. They are rarely the product of a decision to make something hard; they are the product of no one being accountable for the whole experience while many people are accountable for parts of it. Organisational structure leaks into the interface — a phenomenon closely related to Conway's law, which observes that systems tend to reproduce the communication structures of the organisations that build them.

Frictional interfaces also tend to fail in ways that are invisible to their owners. The machine reports successful transactions. It does not report the people who gave up, drove away, or parked without paying, so the metric that would reveal the friction is precisely the one that is not collected.

Deliberate Friction

Not all friction is unwanted. Confirmation dialogs before destructive actions, waiting periods, deliberate delays in publishing, and multi-step authentication are all intentional friction, added because a fast path would be dangerous. The distinction is whether the friction protects the user or merely exposes them to someone else's complexity.

The inverse case — friction added against the user's interest — is now generally discussed as dark patterns: cancellation flows that are far harder than sign-up flows, consent dialogs where refusal takes more clicks than acceptance, and unsubscribe processes routed through several screens. These are frictional interfaces built on purpose, and they are legible as such precisely because the friction is asymmetric: easy in the direction that benefits the operator, hard in the direction that does not.

Diagnosing Friction

• Count the decisions the interface requires that the user's goal does not.
• Compare the effort of the desired path with the effort of its reversal.
• Look for requirements that exist to serve a back-end system rather than the person in front of it.
• Ask what proportion of approaches end in abandonment, and whether anyone measures it.

Related Reading

• Calm Technology
• Designing Interactions
• Persistent Paleontology
• Materials