Friction

Friction is anything that makes it harder for users to accomplish their goals in your product. Every additional step, confusing interface, slow load time, or unnecessary question creates friction that can cause users to abandon their task. While some friction serves legitimate purposes, unnecessary friction is a primary enemy of user experience and conversion.

Why it matters

Friction compounds. A single extra step might reduce conversion by a few percent. Ten extra steps might reduce it by half. Users have limited patience and attention; each friction point consumes some of both. Eventually, they leave.

The impact of friction is often invisible because you only see users who persisted. The users who bounced due to friction never show up in your completion metrics - they simply disappear, often without explanation.

Reducing friction is frequently the highest-leverage improvement a product can make. Before adding new features, ensuring users can actually reach existing features often delivers more value.

Types of friction

Friction appears in multiple forms:

Interaction friction involves the mechanics of using the product: too many clicks, confusing navigation, unclear buttons, small tap targets, or awkward workflows.

Cognitive friction involves the mental effort required: complex terminology, too many choices, unclear instructions, inconsistent patterns, or unexpected behavior.

Emotional friction involves negative feelings the product creates: frustration, anxiety, distrust, or feeling stupid. Security warnings, error messages, and unclear commitments often create emotional friction.

Technical friction involves performance issues: slow load times, laggy interactions, errors, or device incompatibility.

Process friction involves required steps that may be necessary but still impede progress: account creation, verification, billing setup, or configuration.

Finding friction

Several methods reveal where friction exists:

Analytics show where users drop off. High abandonment at specific steps indicates friction worth investigating.

User testing lets you watch users struggle in real time. Observing confusion, hesitation, or frustration reveals friction that metrics alone might miss.

Session recordings provide similar insight at scale. Pattern recognition across many sessions reveals common friction points.

User feedback directly tells you where users struggle. "Why do I have to..." and "I couldn't figure out how to..." are friction signals.

Support tickets often describe friction. Repeated questions about the same issue indicate unclear user experience.

Heuristic evaluation applies usability principles to identify likely friction points before users encounter them.

Reducing friction

Once identified, friction can be addressed:

Remove unnecessary steps. Question every interaction. Does this step add value proportional to its cost?

Simplify decisions. Reduce options, provide smart defaults, and save complex configuration for advanced users who need it.

Improve clarity. Better labels, clearer instructions, more intuitive icons. When users understand what to do, they do it faster.

Optimize performance. Fast pages feel effortless. Slow pages feel like obstacles.

Provide feedback. Show users their progress, confirm their actions, and acknowledge their input. Uncertainty creates friction.

Handle errors gracefully. When things go wrong, clear explanations and easy recovery reduce friction impact.

Remember state. Don't make users re-enter information or repeat configurations. Preserve context across sessions.

Intentional friction

Not all friction is bad. Some friction serves important purposes:

Confirmation friction prevents costly mistakes. "Are you sure you want to delete?" is friction that protects users.

Security friction protects sensitive actions. Authentication steps are friction that users generally accept for appropriate reasons.

Commitment friction filters out unserious users. Sometimes you want users to invest effort to ensure they're genuinely interested.

Legal friction satisfies compliance requirements. Terms of service acceptance is friction that may be legally required.

The key is distinguishing friction that serves users from friction that just makes things harder. Intentional friction should be minimized while accepted; unnecessary friction should be eliminated.

Friction and product decisions

Friction considerations should inform product decisions:

Tools like Klero surface friction through user feedback. When users describe what's hard, confusing, or frustrating, they're pointing directly at friction that deserves attention.