Error Recovery
The design of pathways that help users understand, recover from, and prevent errors.
Plain English
Errors are inevitable. The question is not whether users will make mistakes, but how quickly and confidently they can recover from them. Good error recovery design: tells users exactly what went wrong in plain language, shows them exactly how to fix it, and prevents the same error in the future (e.g. by validating inline before submission). The emotional dimension matters: errors that apologise and offer a path forward feel different from errors that blame the user.
Research background
Nielsen's Heuristic #9: 'Help users recognize, diagnose, and recover from errors.' Implementation: (1) Inline validation on blur (not on every keystroke). (2) Error messages in plain language — no error codes unless also providing the human explanation. (3) Contextual placement — errors adjacent to the field they relate to. (4) Auto-recovery where possible (suggest correct spelling, fix formatting automatically). (5) Undo support — let users reverse actions, not just prevent them.
UI examples
✓ Applying the principle
A form that shows "Email already in use — sign in instead?" next to the email field, with a direct link to sign in — error + instant recovery in one message.
✗ Violating it
"Error 404: Resource not found" with no navigation, back button, or search — user is stranded with no recovery path.
AI Prompt
Paste into Claude, Cursor, Bolt, or v0.
Design error recovery: inline validation on blur with specific error messages (not just 'invalid'), auto-suggestions for close-but-wrong inputs, undo support on destructive actions, and a meaningful 404 page with search and navigation.