Help Users Recognize, Diagnose, and Recover from Errors
Write error messages in plain language, place them near the problem, and show people how to recover.
A useful error message names the problem and shows the next move.
Something went wrong is not enough. People need to know what happened, where it happened, and what they can do next. A useful error message turns a dead end into a clear next step.
Origin
Jakob Nielsen included this principle in his 1994 heuristics. Tim Neusesser and Evan Sunwall's 2023 guidance organizes effective error messages around visibility, clear communication, and reducing the work needed to recover.
Place the message beside the field or action that caused the problem. Use text, icons, and contrast so the error does not depend on color alone.
Describe the exact issue in familiar language. Hide technical codes unless they are genuinely useful for diagnosis or support.
Offer a practical next step and avoid blame. Tell people what they can change, retry, or choose instead.
Protect the work already done. Keep entered information when possible and let people correct the problem without starting over.
Digital systems
CLEAR Password Requirements
CLEAR shows password requirements beside the field and marks which ones are still unmet. People can see what needs attention and correct it in the same place.
Physical signals
Wrong Way Sign
A Wrong Way sign appears where a driver could enter against traffic. It names the problem and gives one immediate instruction: stop. The message arrives while recovery is still possible.
A vague message tells people that something failed but leaves them to find the cause and invent a fix. If their input also disappears, the system adds more work to an already frustrating moment.
Show the error where it happened, explain it clearly, preserve the person's work, and provide the next useful action. The message should help them continue, not simply announce failure.