UX/UI design / DIJION
Confirm before deletion or offer Undo afterward?
A guide to choosing confirmation or Undo by separating deletion scope, reversibility and pending server operations.
Adding the same confirmation to every deletion does not guarantee a safe experience. Repeated questions can be dismissed without reading, while a brief notification is insufficient for an irreversible operation. In an illustrative notes app, removing a local draft and deleting all copies of a shared document involve different consequences.
State the scope of the action
Does Delete affect this device, the account or a record shared with others? Make the object, scope and reversibility understandable together. Hiding an item from a list differs from permanently deleting it. Concealing that distinction can make a later reappearance look like a failure or a broken promise.
Choose the interaction according to consequences
Scroll the table horizontally to see all columns.
| Action | Approach to consider | Required explanation |
|---|---|---|
| Reversible local change | Visible Undo | What will be restored |
| Broad permanent loss | Clear confirmation first | Scope and irreversibility |
| Pending remote operation | Accurate state and recovery | Whether the result is certain |
Make Undo a real recovery path
Undo should restore more than the animation. Related data, ordering and access context may need recovery too. A brief message can be missed if it is the only path back. Where appropriate, consider a trash area or persistent history, and define its retention boundary and access rather than assuming it solves every deletion case.
Avoid certainty while the server outcome is unknown
Deletion may have completed even when the request times out. Showing the item again does not prove that it was restored. Verify current state and handle repeated operations safely. If another device changed the record, restoring an old copy must not silently overwrite newer work; define the conflict policy before shipping.
Test deletion and recovery together
- Compare scope explanations for individual and bulk deletion.
- Miss the Undo message and look for an alternative recovery path.
- Delay the deletion response and retry.
- Test restoration after a change on another device.
The deliverable is an outcome-and-recovery contract for each deletion type. An appropriate interaction follows from explaining the real consequences, rather than maximizing the number of confirmation dialogs.