interaction design
Error recovery and undo
Why is undo often better than a confirmation dialog?
Error recovery is what an interface offers after a mistake: a way back. The strongest form is undo - the action happens immediately, with an easy reversal sitting right there - which lets people move fast without fear, because anything done can be undone. It treats slips as normal and recoverable, not as things to interrogate up front.
Also known as: undo, error recovery, undo pattern, reversibility
Prefer to watch?
Watch the recap 0:46
The demo
A little list. Delete an item - it goes at once, but the way back sits right there. Try deleting, then undoing, and notice you never had to confirm a thing.
What this demo shows (text version)
A short list of items each has a delete control. Deleting one removes it straight away - no "are you sure?" - and shows a brief toast with an "Undo" button. Clicking undo within a few seconds puts the item back exactly where it was; ignore it and the deletion simply stands.
That's error recovery by undo: the action is instant, so the common case is fast and unblocked, and a slip is fully recoverable because the way back is right there. It beats a confirmation dialog for reversible actions, which would interrupt every time and which people learn to click through without reading. Confirmation is reserved for the genuinely irreversible.
For anything reversible, undo usually beats a confirmation dialog: let the action happen at once and offer an easy way back, rather than interrupting every time to ask "are you sure?". Undo keeps people fast and unafraid, and - unlike a prompt people learn to click through - it actually catches the slip. Reserve confirmation for the truly irreversible.
You deleted it, saw it vanish, and the way back was right there - one tap and it returned, no harm done. A confirmation dialog would have stopped you every single time, including the ninety-nine times you meant it. Undo asked nothing up front and still saved you from the one time you didn't.
Undo beats "are you sure?" for reversible actions because it doesn't tax the common case. A confirmation interrupts every action to guard against the rare mistake, and people quickly learn to dismiss it on autopilot - so it stops being read exactly when it would matter. Undo stays silent until you actually need it.
Reversibility changes how people behave: when they know they can undo, they explore, act decisively and trust the product, instead of hesitating over every button. "Make actions reversible" is one of the kindest things a design can do - it converts fear of mistakes into confidence to try.
The pattern has limits. Some actions genuinely can't be undone - sending money, publishing publicly, a permanent delete - and there a confirmation (or a real grace period) earns its interruption. The skill is matching the safeguard to reversibility: undo where you can offer it, confirmation only where you truly can't.