Error Prevention
Error prevention designs risky choices, inputs, defaults, and constraints so common mistakes are avoided before users need an error message.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/error-prevention/
01What it means
Error prevention removes or reduces conditions that produce mistakes. It combines clear language, sensible defaults, constraints, previews, validation, confirmation for consequential actions, and system rules that preserve valid work. The aim is to make the safer path easier, not to blame people more efficiently.[1][2]
- 01Study failuresSlip, misunderstanding, invalid data, system fault
- 02Remove impossible choicesConstraints, safe defaults, preserved data
- 03Explain before actionRequirements and timely validation
- 04Preview consequencesSpecific confirmation for high stakes
- 05Support reversalUndo or recovery where possible
Measure prevented errors alongside abandonment, false positives, accessibility, and completion time.
02Why it matters
Preventing an error is usually cheaper than explaining and repairing it. It protects data, reduces support demand, lowers anxiety, and matters most for payment, deletion, permission changes, and legal submission. Accessible prevention also avoids repeated correction for people using assistive technology.
03When to use it
Use it wherever input is structured, actions are destructive, choices have dependencies, or failure has financial, safety, privacy, or data-loss consequences. Apply safeguards in proportion to impact while keeping frequent, low-risk actions fast and reversible.
04How it works
- Study real failures and distinguish slips, misunderstandings, invalid data, and system faults.
- Remove impossible choices, constrain formats, preserve valid data, and supply safe defaults.
- Give requirements before input; validate when it helps instead of interrupting every keystroke.
- For consequential actions, show a specific preview or confirmation and offer reversal when possible.
- Measure prevented failures alongside abandonment, false positives, accessibility, and completion time.
05A practical example
Before publishing a campaign, the product checks recipients, links, and scheduling conflicts. A review shows audience size, sender, time zone, and consequences. The action says “Schedule 12,430 emails,” and the system permits cancellation during a short grace period.
06Where it breaks
Every safeguard adds friction and can create mistakes. Overvalidation rejects legitimate input, confirmation dialogs become habitual, and disabled controls conceal requirements. Prevention cannot cover every case, so products still need recovery, resilient storage, monitoring, and support.
Common mistakes
- Using generic confirmations until users stop reading
- Disabling submit without explaining what remains unmet
- Discarding valid input when one field fails validation
07Sources
- Understanding SC 3.3.4: Error PreventionW3C Web Accessibility Initiative · Accessibility guidanceUnderstanding SC 3.3.4: Error Prevention
- 10 Usability Heuristics for User Interface DesignNielsen Norman Group · Professional guideline10 Usability Heuristics for User Interface Design