How much friction in a flow is healthy vs purely wasteful?

Published Read 3 min read

On this page

Friction is healthy exactly as far as it makes the user pause before something consequential or irreversible and serves their interest, and it turns wasteful the instant it adds a step that serves no one. The amount is not a number you tune toward zero. It is a line you draw by asking whose interest each step protects. A pause that gives a person a beat to catch a costly mistake is friction working for them. A field, a screen, or a tap that exists for the system’s convenience or out of habit is friction working against them. Deliberate friction has a reason you can name. Waste does not.

The reasoning is that friction is just resistance, and resistance can be either a guardrail or an obstacle depending on what it is placed in front of. Before a significant, hard-to-undo action, resistance is protective: it slows the user down at the one moment slowing down pays off, and they would thank you for it if a slip would have cost them. Resistance placed in front of a routine, recoverable, or trivial action is obstruction: it taxes the person for nothing, because there was no mistake worth preventing and no interest of theirs being served. The “remove all friction to make it effortless” reflex flattens this distinction by treating every step as equal drag, and in doing so it strips the useful pauses along with the wasteful ones. Effortless is the wrong target. Effortless where it should be easy, and deliberately resistant where it should be careful, is the right one.

Consider a checkout flow. A required account creation before a guest can buy is wasteful friction, a step that serves the store’s data goals and obstructs the customer who just wants to pay, and it is exactly the kind of resistance to cut. But a final review screen that shows the full order, the shipping address, and the total before the charge goes through is healthy friction, a pause that protects the customer from shipping to the wrong place or paying a surprise amount they cannot easily reverse. Same flow, two kinds of resistance, and the difference is entirely whether the step is there for the user or in spite of them.

Even protective friction has to stay proportionate. A pause earns its place by matching the weight of what it guards, so a confirmation before an irreversible deletion is fair while three confirmations before the same act is the protective instinct curdling back into waste. Friction can also be the right answer in spirit but the wrong size, too heavy for a small risk or too light for a large one, and “is this for the user” does not excuse “is this more than the risk deserves.” Useful friction is calibrated to consequence, not just justified by it.

When you audit a flow, walk it step by step and ask of each one whose interest it serves and what mistake it prevents. Where a step protects the user from a real, costly, or irreversible error, keep it and size it to the stakes. Where a step serves the system, a metric, or an old habit and guards against nothing the user would regret, cut it without hesitation. Stop measuring flows by how few steps they have and start measuring them by whether every remaining step is working for the person walking through it.

Related posts:

  1. At what point does a strong hero flatten everything below it? A hero flattens the page the moment the section directly below it stops earning attention on its own. That is the line, and it is a behavioral test, not a......
  2. How long should a line of text be before readability starts to drop? Readability holds when a line of body text runs roughly forty-five to seventy-five characters, counting letters, spaces, and punctuation, with the mid-sixties often cited as the comfortable target. Stray much......
  3. When does a confirmation step protect users vs just annoy them? A confirmation step earns its interruption only when the action it guards is destructive, hard to reverse, or genuinely high-cost, and it becomes pure annoyance the moment it sits in......
  4. When is a full-width section right vs a contained, centered one? Choose full width when the content is meant to envelop the viewer and a contained, centered width when the content is meant to be read. That single distinction settles most......
  5. How do you keep a hero readable from phone to ultrawide? A hero stays readable across every width when you decouple the text's legibility from the background image's behavior. The mechanism is that an image and the type laid over it......
  6. Should you build a color system from one hue or several? Start from one hue and expand only when the product proves it needs more. A single-hue system, built from one color stretched across tints, shades, and a neutral ramp, reads......
  7. How much whitespace is too much before a layout feels empty instead of intentional? Whitespace becomes too much the moment it stops doing a job. The tipping point is not a pixel value, a margin token, or a percentage of the viewport. It is......
  8. When does a second typeface add hierarchy vs just add noise? A second typeface earns its place only when it draws a clear functional line, the most common one being headings against body, and it becomes noise the moment it decorates......
  9. Should dark mode be a true inversion, or designed separately? Dark mode should be designed separately, as its own deliberate theme, not produced by inverting the light one. A literal flip is tempting because it looks like a single switch,......
  10. Why can shipping one more feature make a product feel worse to use? Shipping one more feature can make a product feel worse because every feature adds interface, choices, and surface area, and that accumulation crowds the core even when the new feature......
  11. How do you design for the user who lands mid-flow from a deep link? You design for the deep-linked user by treating every screen as a possible front door: orient them on arrival, supply or recover the context the earlier steps would have given,......
  12. Should navigation be sticky, or does that depend on page length? The call turns on page length and how often users need to re-navigate, and it resolves cleanly: make the nav sticky on long, multi-section pages and let it scroll away......
  13. When does a bold accent color energize a design vs overwhelm it? A bold accent energizes a design when it is rationed to a few high-priority moments against a calm base, and it overwhelms the moment it spreads across the interface. The......

Leave a comment

Your email address will not be published. Required fields are marked *