Intentional Friction Is Not Bad UX
The easiest path through your product is not always the one users should take. For a decade, the UX field acted like it was.
The frictionlessness imperative — reduce clicks, eliminate barriers, make every flow as fast as possible — produced real improvements. Checkout forms got shorter. Onboarding dropped from ten steps to three. Features that used to require a manual became discoverable. Users got better at using more things.
It also produced gym membership cancellation flows designed to take forty-five minutes, "I agree" checkboxes pre-ticked on surveillance data defaults, and free trial credit card captures that auto-convert at the maximum billing tier with a single missed email.
That's not accidental bad UX. That's friction deployed intentionally — in service of the business rather than the user.
What Friction Does at the Cognitive Level
Friction in UX is any cognitive or physical resistance between a user and their next action. The conventional framing is that friction is always the enemy: a symptom of poor design, a drop-off trigger, a conversion killer to be A/B-tested into oblivion.
That framing ignores what friction does at the cognitive level. Friction creates a pause. That pause is where judgment lives.
B.J. Fogg's Behavior Design Lab at Stanford characterizes friction as a motivational threshold modifier — it does not prevent behavior, it requires that motivation be strong enough to overcome it. Fogg's Behavior Model shows behavior occurs when motivation and ability converge with a prompt at the right moment. Friction reduces perceived ability; it raises the bar for which motivations actually produce action.
The question is never "should this flow have friction?" It is "which behaviors should require higher motivation to complete?"
Some behaviors should be easy. Some behaviors benefit from being slower.
Three Categories That Benefit from Designed-In Friction
Irreversible decisions. Deleting an account, confirming a large financial transfer, permanently removing data shared by multiple users — these are actions where the undo path is costly or nonexistent. Confirmation dialogs, mandatory review steps, cooling-off periods: these are not apologies for bad design. They exist because the error cost of doing something irreversible accidentally exceeds the annoyance cost of an extra click by several orders of magnitude.
GitHub's account deletion flow requires you to type the full repository name before proceeding. That is friction by any definition. It is also correct design for an irreversible action that affects potentially thousands of developers depending on that code.
Default-exploiting enrollments. Research from the UK's Financial Conduct Authority on consumer vulnerability documented that pre-ticked subscription checkboxes and automatic enrollment defaults disproportionately harm low-attention and low-literacy users — exactly the users least able to navigate the downstream consequences. Friction at the enrollment point — an explicit opt-in, a confirmation screen, an unchecked box — redistributes harm avoidance from user responsibility to product design.
The insight here is distributional. For high-attention users, the extra step is mild annoyance. For vulnerable users, it is the difference between an informed decision and a costly mistake.
High-stakes social actions. In 2020, Twitter introduced a prompt asking users to read articles before retweeting them. Pure friction: an interruption between the intent to share and the action of sharing. An internal study found it increased link-open rates by 40% among prompted users. The deceleration produced better-quality behavior, without preventing the behavior entirely.
The design goal was not to stop retweets. It was to raise the floor on what a retweet means.
How Protective Friction Differs from Dark Patterns
The line is not subtle once you ask the right question: who benefits from this friction?
Dark patterns use friction to protect business interests at user expense. The unsubscribe flow requiring three menus, two confirmations, and a seven-day waiting period — that friction benefits subscription revenue retention. The user is made worse off by every step. The business is made better off.
Protective friction imposes a cost on the user in exchange for protection from a larger downstream cost. It is deployed at the moment before an action that is difficult to undo, risky for the user, or likely to be regretted. The friction is explicitly in the user's interest, even when it is annoying.
Regulators have started codifying this distinction. The EU's Digital Markets Act (2022) makes it an enforceable violation to make it disproportionately difficult for users to unsubscribe from services or change privacy settings to less data-sharing defaults. The CFPB's 2024 guidance on digital financial products named specific friction patterns as potentially unfair practices under consumer protection law.
The design of friction is being regulated as an ethical question. The field has been slower to catch up.
Auditing Your Own Flows
If you want to know whether your product's friction is protective or predatory, run two tests:
The downstream regret test. For any friction point, ask: what happens to users who don't encounter this step and proceed anyway? If they frequently return to undo the action, contact support to cancel, or express buyer's remorse — the friction was protecting them. Its absence is a cost they bear.
The beneficiary test. Map who benefits from each friction point. Protective friction should benefit the user — reduced error, better-informed decision, protected reversibility. Predatory friction benefits the product — reduced churn, increased upsells, higher default enrollment rates. The distribution should not be ambiguous.
A cooling-off period before a subscription purchase auto-activates has a measurable effect on user outcomes: people who have a day to confirm their decision and proceed have lower early-churn rates than users pushed through a frictionless checkout. The friction filtered for genuine intent. The business benefit is real and it is aligned with user benefit.
That alignment is the test.
What the Field Got Wrong
The decade-long project of eliminating friction was correct about most friction. Bad UX deserved to die. Confusing flows, arbitrary confirmation steps, gratuitous multistep processes — all of that was correctly targeted.
The error was treating frictionlessness as the objective rather than as a tool. Frictionless flows maximize throughput. In contexts where throughput is the goal, that's fine. In contexts where quality of decision matters more than speed of decision — financial choices, irreversible actions, high-stakes enrollments — optimizing for throughput is optimizing against the user.
The hardest thing to unlearn is that slower is sometimes better. Not because friction is good, but because some decisions deserve more than the minimum time required to click.
See also: Form Errors Are a Design Failure, Not a User Problem — on how the same instinct that eliminated friction also taught us to blame users for confusion that belongs to the designer.
Photo by Francesco Ungaro via Pexels.