Intentional vs Unintentional Friction in UX Design

The short answer

Friction in UX design refers to anything that slows a user down. Not all friction is a problem. Unintentional friction caused by unclear design, missing feedback, or unpredictable behaviour, adds cognitive load without giving users anything in return and should be removed. Intentional friction that takes the form of deliberate pauses, confirmations, and review steps at high-commitment moments, protects users from mistakes and builds trust. The goal is not frictionless design but friction that is correctly positioned.

Why friction became a dirty word in UX

The instinct to remove friction from digital services is understandable. Friction, in everyday language, means resistance, and resistance is uncomfortable. If a journey feels slow, awkward, or requires too much effort, removing whatever is causing that feeling seems like the obvious fix.

For this reason, friction reduction can become a standard UX goal. Fewer steps. Fewer confirmations. Faster completion. Shorter flows. In many contexts, those are entirely valid design improvements.

But the goal of friction reduction, applied without distinction, has produced services that feel fast but don’t give the user confidence. Services that move users through quickly but leave them uncertain of what happened, unable to correct mistakes, and unsure whether their actions had the effect they intended.

The distinction that changes everything: intentional vs unintentional friction

The problem is not friction itself, but specifically the friction that isn’t doing useful work.

Unintentional friction occurs when users are slowed down because the design is unclear, unpredictable, or requires them to stop and figure something out. It appears at points like these:

• Users hesitate because they don’t know what just happened
• They repeat an action to check if it worked
• They backtrack because they’re unsure it’s safe to continue
• They encounter an error message that doesn’t explain what to do next
• They can’t tell whether something saved or was lost

This kind of friction feels like resistance because that is exactly what it is; it’s the user pushing against unclear design. It adds cognitive load without giving users anything useful in return, meaning that it should be identified and removed.

Intentional friction works differently. It slows users down on purpose, at moments where speed is not the goal. These are points in a journey where users are:

• About to commit personal or financial information
• Performing an irreversible or destructive action
• Returning to a task they started earlier and need to reorient
• Deciding whether they are ready to submit or continue

At these moments, a pause, a confirmation, or a clear summary gives users space to orient themselves, verify their intent, and proceed with confidence. That friction is protective rather than obstructive. Removing it doesn’t improve the experience, it actually introduces risk where there previously was none.

Why teams remove the wrong kind of friction

The most common failure mode in journey optimisation is removing intentional friction in the name of efficiency while leaving unintentional friction unresolved.

Confirmations get stripped out because they add a step. Summaries disappear because they add length. Review screens are compressed or removed because they appear to slow users down. Meanwhile, unclear feedback states, missing outcome messages, and vague error handling — the actual sources of unintentional friction — remain untouched because they’re harder to see in an analytics dashboard.

The result is a journey that looks fast in a user flow diagram but doesn’t feel reliable in practice. Users who encounter an irreversible action with no confirmation won’t feel the benefit of the removed step, but they will feel anxiety. And with that feeling of anxiety, they will lose trust in the service.

Design decisions that remove intentional friction to improve metrics often generate support contacts, repeated submission attempts, and abandonment that never appear in the same dashboard that justified the change.

A diagnostic question for reviewing friction

When reviewing an existing journey that feels slow or frustrating, the natural question is: how do we make this faster? That question usually produces the wrong answer, because it assumes friction is the problem rather than asking what kind of friction is present.

A more useful question is:

Is this friction helping the user make a decision, or compensating for something unclear earlier in the journey?

If the friction is compensating for unclear design upstream — for example, users are hesitating because an earlier step was ambiguous — the solution is to fix that upstream gap, not to accept the hesitation as unavoidable or try to move users past it more quickly.

If the friction is helping users make a decision — for example, a review screen is giving users the opportunity to check their information before committing — the solution is to keep it, support it, and perhaps even strengthen it.

What well-positioned friction looks like in practice

Intentional friction doesn’t make journeys feel slow or difficult when it’s done well. It makes them feel deliberate and trustworthy. Patterns that demonstrate this include:

• Review and confirm screens that summarise information before submission, giving users one clear opportunity to check and correct before a commitment is made.
• Destructive action confirmations that require explicit acknowledgement before deletion, cancellation, or irreversible changes; not as obstruction, but as protection.
• Save and return interactions that make the state of a partial task explicit when users return, so that they know exactly where they are and what remains to be done.
• Progressive disclosure in long forms that break commitment into stages, reducing the cognitive cost of each individual step while maintaining a clear path to completion.

None of these patterns make services objectively longer in a way that hurts users. They make services predictable, and predictability is what allows users to move through them with confidence rather than hesitation.

Frequently asked questions