Skip to content
UX Atlas
PatternExpert heuristicFoundational

Destructive Actions

Actions that remove or destroy, which need separation in space, distinct styling and a recovery path.

Definition

A destructive action removes data or causes an effect the user cannot easily reverse. The design obligations are to make it hard to trigger accidentally, obvious in consequence, and recoverable wherever technically possible.

Expert heuristic. A review criterion developed by practitioners. Useful and widely taught, but evaluated by judgement rather than measurement.

On this page
  1. Definition
  2. Layered protection, cheapest first
  3. In practice
  4. Continue from here

Layered protection, cheapest first

  1. 1.Separate it in space from frequently used actions, which removes most accidental triggers at zero cost.
  2. 2.Style it distinctly, using the danger colour plus text, never colour alone.
  3. 3.Make it recoverable: soft delete with a restore window is almost always achievable.
  4. 4.Offer undo immediately after, in a persistent inline message rather than a vanishing toast.
  5. 5.Confirm, only if it is genuinely irreversible.
  6. 6.Require typed confirmation, only if it is catastrophic.

In practice

Delete in the overflow menu

Lists

Moving delete out of the row and into an overflow menu removes the most common accidental deletion without meaningfully reducing discoverability.

Continue from here

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Applies when you are designing

Settings

Principles behind this

The reasoning this solution is an application of.

Often used with

These usually appear in the same screen or the same decision.

Related concept

Connected closely enough to change how you apply this.