Destructive friction is isolation, delay, and typing
Aliases: destructive friction · spatial isolation · delayed execution
What it is
If a destructive act must remain, the flow can raise the cost of a miss and of an automated click with friction. Three common tools: keep the dangerous control out of the ordinary cluster (spatial isolation), make effect later than the click (delay), require something other than a click (typed confirmation). This entry only names the menu. It does not scale intensity to harm, and it does not develop typed confirmation as a method of its own.
Why it happens
Friction attacks continuity at the skill layer. Isolation breaks capture from “adjacent button, same gesture”: delete does not sit to the right of save, and is not the end of a swipe. Delay splits “clicked” from “the world changed,” giving attention one chance to return—effective for a miss whose finger has not yet lifted, a countdown window for someone already walking away. Typed confirmation changes the channel from aiming to generating: typing cannot compile “OK” into the same click chain. The three tools break different joints—choice, time, channel—and can stack, but stacking is cost, not automatic safety.
Studying it
Add isolation, a multi-second delay, or typing to the same irreversible delete, against a no-friction control.
Independent variables: distance between dangerous and ordinary controls, delay before effect, whether a second, non-click channel is required. Dependent variables: adjacent-miss rate, automated click-through, time to complete, rate of expert workarounds or complaints.
In the lab, delay is often treated as “click once more.” Forbid a tappable primary button before the delay ends, or the study measures another confirm, not delay.
Where it stops holding
A thumb’s hot zone on a phone can make “move it farther” work on desktop and still land in the same zone on mobile. Delay does not apply to security responses that must take effect now. Typed confirmation is the costliest item; naming it in the menu is enough, and how to use it belongs to that method. For accessibility, isolation cannot be position alone—it needs names and grouping—and delay must be perceivable to assistive technology, not only a visual countdown.
Applying it
- Draw an action map: do ordinary and destructive acts share a row, a swipe, a shortcut? If they share, isolate first.
- For acts that need a cooling-off but not typing, delay the effect and offer cancel inside the delay.
- Treat the three tools as a menu, not a default stack; record which one each path actually uses.
- Verify by throwing adjacent misses and a repeated-click script at every destructive path. If position did not block it, isolate; if repeated clicks still finish it, consider delay or a second channel.