
Friction is the extra time, steps or effort required to complete an action. It is often treated as the enemy of efficiency, but smoother is not always better.
Consider a large bank transfer. Before submission, a confirmation screen shows the recipient and amount and asks the user to check again. The step does not remove the option to transfer. It briefly interrupts the movement of the finger and creates a chance to notice an incorrect account number. Here, friction is not merely an obstacle; it builds checking into the action itself.
Friction differs from prohibition. A prohibition closes an option, while friction preserves it and changes only how quickly or easily it can be taken. It also differs from arbitrary complication. If checking an account balance always requires repeated verification, the extra steps do not match the risk and simply consume attention.
We should therefore assess friction by asking not only how many steps it adds, but what it protects, who bears it and whether it can be bypassed. High-risk actions that are difficult to undo may justify some friction; low-risk actions repeated often should usually remain smooth. Good design does not eliminate all friction. It places resistance where a pause is genuinely useful.
Discover more from Geoffrey Chen
Subscribe to get the latest posts sent to your email.