Undo is a design material
What happens to an interface when nothing needs confirming.
·4 min read
The dialog problem
Every confirm dialog is a small admission that the action can't be taken back. At Harbour Mail we timed it: people answered the archive dialog in under 400ms, faster than anyone reads. The question had become a speed bump, and it still let mistakes through.
Taking it out
We made archive immediate and moved the decision after the action instead of before it. A pill offers the thread back for five seconds. Archive three and the pill counts them, so one undo returns all three.
Inbox4 threads
Aoife Brennan09:41
Notes from Thursday's review
Tomás Reyes08:12
Invoice 2026-114
Harbour MailMon
Your weekly summary
Wen LiSun
Prototype link for search
What it changes
Once undo is reliable, the rest of the interface gets lighter. Buttons lose their warnings, menus lose their second step, and destructive actions can sit where they are used instead of behind a settings page.
It only works if undo is honest. Five seconds has to mean five seconds of deciding, so the timer stops under the pointer. And anything that really can't be taken back, like sending, still asks.