Destructive actions must not sit next to frequent ones
Aliases: slip onto delete · accidental destruction · neighbour risk
What it is
Send is tapped dozens of times a day in a compose bar. Delete draft, parked on its left, vanishes the draft the first time a landing is off. Destructive adjacency is an irreversible or high-cost action sharing a neighbouring hit region with a frequent action that is already practised. The miss is not Delete looking like Send. It is Send’s landing distribution already covering Delete’s territory.
Send, Save, Next — those are the dangerous neighbours. Help, tapped rarely, next to Delete almost never fires it.
Why it happens
The contact of a frequent target is not a point. It is a cloud of landings. The more practised, the more hurried, the larger the variance and the longer the tail. A neighbour that reaches into that tail is tapped at the frequent action’s rate — a slip, the intention still the frequent action. Isolation is geometrically false once the centre-to-centre gap is smaller than the frequent landing radius plus the destructive hit-target radius.
Visual distinction (red, a trash glyph) does not stop a hand already in flight. Distinction is for people still reading. Adjacency fails on the tap that is not reading.
Studying it
Train the frequent action toward automatic, then place a destructive control beside it (a reversible stand-in such as Move to trash) and count misses under time pressure.
Independent variables: centre-to-centre distance, whether the destructive control is visually emphasised, time pressure, amount of practice on the frequent action. Dependent variables: taps intended for the frequent control that land on the destructive one, radius of the landing cloud.
Plot the landings as an ellipse and see whether it invades the destructive hit target; that guides spacing better than a miss rate alone.
Where it stops holding
When the destructive action is the current task (tidying a file manager, bulk delete), it is the frequent one, and isolation turns toward controls that would abort it — Select all, Back. A stylus or a mouse has a tighter cloud than a thumb, so the same pixel gap may already suffice on desktop. Switch scanning walks a linear order; adjacency becomes temporal, and a blank step has to be inserted in the order, not a pixel gap.
Applying it
- List the left and right neighbours of every frequent action. Take delete, empty, unlink, discard edit off that list, into an overflow, a long-press, or a distant secondary region.
- When they must share a bar, insert an unhittable gap whose width is taken from the frequent action’s landing cloud on the real device, not from the default icon-grid slot.
- Make Send/Save a solid primary and the destructive a weak text control, pulled apart, with unequal hit targets — equal size maximises how much tail is delivered into the neighbour.
- How to check: twenty consecutive taps on the frequent button on the target device, dots overlaid on a screenshot. Any dot inside the destructive rectangle fails the pair.