Protective
Slows you down for you, roughly in proportion to what you could lose. An undo window, a review screen before money moves, a pause before a message reaches four hundred people.
Test: would you thank it on your worst day?
Lab note 00 A field guide to the steps between wanting and doing
Product design has spent two decades sanding away every obstacle. Most of that was a gift. But a few obstacles were never obstacles — they were the moment where you decided, consented, noticed, or got a second chance. And some of the friction that remains isn't protecting anyone at all; it's quietly keeping people out.
Slide toward zero and the words lose traction. Slide too far and they lock up.
01 · The material
“Friction” is used as an insult in product meetings: anything that slows a person down. That framing hides a question that matters more than speed — whose interest does the slowdown serve, and can everyone get through it? Ask that, and the same-looking step splits into three very different things.
Slows you down for you, roughly in proportion to what you could lose. An undo window, a review screen before money moves, a pause before a message reaches four hundred people.
Test: would you thank it on your worst day?
Slows you down for them — and usually only in one direction. Joining takes a tap; leaving takes a phone call. Accepting is a big button; refusing is five screens.
Test: is the effort symmetrical?
May be well-intended, but treats one kind of body, memory, device or schedule as the default. A puzzle with no alternative; a booking that requires a smartphone; office-hours-only.
Test: is there a second way through?
02 · The friction bench
Ten everyday design situations, each built at five friction settings. The four gauges are a Design scenario model — reasoned estimates to make trade-offs visible, not measurements. Where a real study or rule exists, it's cited under the card.
·
Use the slider, arrow keys, or the step buttons.
03 · Six principles
A decision can matter enormously and still deserve no friction if it's easy to reverse. Moving money, deleting data and making legal commitments are different: the web's accessibility guidelines ask that such submissions be reversible, checked for errors, or reviewable before they're final. WCAG 2.2 · SC 3.3.4
An undo period after the action keeps nearly all the speed and recovers most mistakes. A dialog before the action interrupts everyone to catch a few. Where reversal is possible, build reversal first.
Confirmation dialogs work when they're unusual. Nielsen Norman Group warns against using them for routine actions: people learn to click through, and the dialog stops preventing anything. NN/g on confirmation dialogs
“Are you sure?” is a lazy question. “This permanently deletes 214 photos shared with 3 people” is friction that does work: it gives the pause something to think about.
Asymmetry is the fingerprint of manipulation. If joining is one tap and leaving is a phone call, the friction isn't protecting the person — it's protecting revenue from the person.
A security step that requires remembering, transcribing or solving something must offer another route. WCAG's authentication criterion specifically names allowing password managers and paste as acceptable help. WCAG 2.2 · SC 3.3.8
04 · Telling them apart
| Question | Protective | Manipulative | Excluding |
|---|---|---|---|
| Who benefits from the pause? | The person paying it | The business | Often nobody; it's an assumption |
| Is it symmetrical? | Same effort either way, or more on the riskier side | Easy in, hard out | Hard for some people in both directions |
| Is it honest about why? | States the consequence plainly | Uses guilt, false urgency or hidden defaults | Usually silent about who it fails |
| Is it proportionate? | Grows with irreversibility | Grows with how much revenue is at stake | Fixed, regardless of stakes |
| Is there another way through? | Yes — undo, help, alternatives | Deliberately obscured | No — that's the defect |
05 · Field test
Nine real-world patterns. File each one as protective, manipulative or excluding. Some are deliberately close calls — the explanation matters more than the score.
06 · Reversible workshop
Start from the frictionless version of a situation and add design moves — including a few dark ones, so you can see what they do to the gauges. Every change is in an undo history. When you're happy, export a decision card to share with a team.
07 · Against easy
Interpretation These are arguments, not findings. Each comes with the strongest objection I know.
i.
Products tend to count ease at the instant of action — the tap, the checkout. The cost of an unconsidered action arrives later: the return, the regret, the subscription found three months on. A metric that only sees the first moment will always vote for less friction.
But: people are entitled to make quick choices they'll sometimes regret. Designing for “future you” can slide into paternalism if it isn't paired with easy reversal.
ii.
Consent isn't a checkbox; it's a moment of noticing what you're agreeing to. Remove every pause and you can end up with actions nobody exactly chose — tracking switched on by default, purchases from a pocket, posts shared on reflex.
But: pauses that appear everywhere become noise. Consent theatre — a banner on every page — may produce less real choice than one good default.
iii.
A frictionless front end often relocates the work: to support staff untangling mistakes, to the person reconciling accidental charges, to whoever must explain to a relative why the money went to the wrong account. Ease for one party can be a bill for another.
But: the reverse is equally true. Every approval layer and verification step moves effort onto the people least able to absorb it.
iv.
Booking a slot at a museum, writing a letter rather than a reaction, walking to a place — sometimes the effort shapes the attention we bring. Flattening every experience into the same instant tap can quietly flatten what the experience was for.
But: “effort is meaningful” is easy to say when the effort is optional for you. For many disabled people, convenience isn't laziness; it's access that was fought for. Romanticising friction is its own kind of exclusion.
08 · Sources & labels
Scenario gauges, verdicts and workshop scores are a deliberately simple model. Real products should be tested with the actual people who use them — especially people using assistive technology.
Last step, deliberately
Found a scenario where the bench gets it wrong? Know a protective step that deserves a place here — or a “safeguard” that locked someone out? This is the one bit of friction on the page worth adding.
Opens your own email app. Nothing is sent or stored by this page.