Error Prevention and Undo
Level 4 · Designing the interaction
How to make mistakes hard to make and easy to take back. Error prevention, the undo button, and the dark patterns that trick people on purpose.
Course contentsLesson 15 of 21
Level 1 · What UX is
Level 2 · Finding out from users
Level 3 · Making sense of research
Level 4 · Designing the interaction
After this lesson you can
- Prevent an error before it happens
- Offer undo instead of a warning
- Spot a dark pattern
10 mincovers 3 glossary entries
Worth reading first: Interaction Design Basics
How to make mistakes hard to make
Error prevention means making mistakes hard to make, so there is less to fix later. A date picker for a return flight can fade out each day before the first flight. Nobody can pick those days, so nobody books a return before they leave. One faded row stops a whole kind of mistake.
Prevention comes in many forms. Limit choices to the ones that are valid. Fill in what you already know. Check a field as soon as it is typed, not after the whole form is sent. Ask for a password twice only if you cannot offer a show button.
When a mistake gets through, undo takes it back. Delete a message, and a bar appears with an undo link for a few seconds. Many email services let you undo a sent message for up to 30 seconds. A slip is never final.
Undo beats a warning box. Are you sure? pops up so often that people click yes without reading. Undo lets them act at full speed and fix the rare mistake after. Save the warning for actions that truly cannot be undone, like closing an account.
A dark pattern is the opposite of all this. It is a trick in a design that pushes you to do something you did not mean to. A box already ticked to sign you up for emails. A cancel button hidden three menus deep. A countdown timer that resets when you reload.
The name was coined in 2010 by a UX designer who collected examples. Many dark patterns are now against consumer law in parts of the world, such as the EU. Even where they are legal, they trade a sale today for trust tomorrow.
The common mistake is to blame the user for errors. If many people make the same mistake, the design invited it. Fix the design, not the people. A support log full of the same error is a design brief.
Worked example
A photo app drops its warning box
A photo app asked are you sure? every time someone deleted a picture. Users still lost photos, because they clicked yes by habit.
The team removed the box and kept deleted photos for 30 days in a bin. Complaints about lost photos fell to almost none.
The words for this lesson3
Check yourself
Why is undo often better than an are you sure? box?
Finished this lesson?
Marking it complete also marks its 3 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.