Usability Heuristics
Error Prevention
Stop problems before they happen — that beats even the best error message.
Where it comes from
It's the fifth of Jakob Nielsen's ten usability heuristics. Nielsen's point is that even good error messages are a second-best solution — better still is a careful design that prevents the problem from occurring in the first place.
Why it matters for your website
The best error message is one that never has to appear. Nielsen Norman Group's fifth heuristic says good design prevents problems before they happen. Every friction point a user doesn't hit is a conversion you don't lose.
Nielsen distinguishes two kinds of error to prevent: slips (right intention, wrong execution) and mistakes (wrong intention from a misunderstanding) — and good design heads off both, with helpful constraints, good defaults, confirmations for risky actions, and forgiving input.
Every error a user doesn't hit is a moment of friction, frustration, and potential abandonment you've removed before it could cost you. Prevention is invisible when it works — which is exactly why it's undervalued and worth designing for deliberately.
Wrong vs right
A form that lets users enter an invalid value and only tells them after they submit.
Constraints, good defaults, and forgiving input that prevent the invalid entry in the first place.
A destructive action with no confirmation, so a single mis-click causes real harm.
A confirmation or undo for risky actions, preventing the costly mistake.
Relying on error messages to mop up problems the design could have stopped.
Designing the problem out, so the error message never has to appear.
Understanding Error Prevention
Error prevention is the fifth of Jakob Nielsen's ten usability heuristics, and it carries a pointed message: even the best error message is a second-best outcome. The ideal is a design careful enough that the error never happens — because preventing a problem is always better for the user than helping them recover from one.
Nielsen frames prevention around the two types of error from Norman's work. Slips — right intention, wrong execution — are headed off by constraints, good defaults, and forgiving input. Mistakes — wrong intention from a misunderstanding — are headed off by clear information and confirmation of consequential actions. Good design works on both.
The payoff is invisible, which is why it's underrated. Every error a user never hits is a moment of friction, frustration, and possible abandonment you removed before it could cost you a conversion. Prevention does its best work silently. It's the heuristic companion to Norman's constraints, and it connects to error recovery and Postel's robustness principle.
How Kweri checks it
Kweri can spot some opportunities for error prevention — forms that appear to accept invalid input, destructive actions without confirmation or undo, and rigid inputs that invite mistakes — and prompt you to design the problem out. What it can't always verify without exercising the interface is exactly how the system behaves on bad input or risky actions, since that plays out in interaction. So Kweri surfaces likely places to add constraints, defaults, or confirmations, while confirming the real error behaviour means testing the live flow with mistakes.
FAQ
What is error prevention in UX?
It's Jakob Nielsen's fifth usability heuristic: good design prevents problems from occurring rather than relying on error messages to handle them afterwards. The best error message is one that never has to appear.
Why is preventing errors better than good error messages?
Because an error message, however clear, still means the user hit a problem — costing time, friction, and confidence. Preventing the error spares them that entirely. Recovery is second-best; prevention is the goal.
How do I prevent errors in design?
Use helpful constraints, sensible defaults, forgiving input, and confirmations for risky actions. Prevent slips (right intention, wrong execution) with constraints, and mistakes (wrong intention) with clear information that corrects misunderstanding.
What's the difference between error prevention and error recovery?
Error prevention stops mistakes from happening; error recovery helps users fix the ones that do. Nielsen's heuristics cover both — prevention (heuristic 5) is preferred, with good error messages (heuristic 9) as the safety net.
How is error prevention related to constraints?
Constraints are a primary tool for error prevention. Disabling invalid options, shaping inputs so only valid ones fit, and ruling out impossible actions all stop errors before they can occur — the design-level mechanism behind the heuristic.
Related principles
User errors divide into two fundamentally different types: slips (right goal, wrong action — a lapse of execution) and mistakes (wrong goal — a failure of understanding). Each requires a different design response.
Error messages should be plain English, name the exact problem, and suggest the fix.
Errors should be flagged as users complete each field, not after the entire form is submitted — post-submit error discovery forces users to stop, hunt for problems, and often repeat work they've already done.
Every unnecessary form field adds cognitive cost and reduces completion — ask only for what is needed to complete the current step, and defer everything else.
Attribution & sources
Identified by Jakob Nielsen (1994). Catalogued from Nielsen Norman Group — Error Prevention.
The fifth of Nielsen's 10 Usability Heuristics; the linked article is the reference used here.
See Error Prevention on your own site
Run a free Kweri audit — a plain-English review of your site’s speed, accessibility, SEO and design, ranked by what to fix first. No login, no jargon.
Run a free audit →