An error message is a conversation with a person at their most frustrated moment. Make it clear, make it helpful, and never make them feel small.
I still remember the first time an error message made me feel small.
I had filled out a long registration form, pressed submit, and the page simply reloaded with a red line at the top. Something was wrong. It did not say what. It did not say where. It did not say how to fix it.
I closed the tab and never came back.
That experience taught me something I now believe deeply. An error message is not a technical detail. It is a conversation with a person at their most frustrated moment.
Jakob Nielsen addresses this directly in his usability heuristics. One of them is called error prevention, and it begins with an honest observation. “Good error messages are important, but the best designs carefully prevent problems from occurring in the first place.”
When errors do happen, another heuristic asks us to help users recognize, diagnose, and recover from them. Nielsen is precise about what that means. “Error messages should be expressed in plain language (no error codes), precisely indicate the problem, and constructively suggest a solution.”
Plain language. Precision. A solution. That is the whole recipe.
Here is how I put it into practice.
- Prevent before you correct. Use input masks, sensible defaults, and inline hints so mistakes are less likely to happen at all.
- Speak human. Replace codes and system terms with words your users actually use.
- Point to the exact problem. Place the message next to the field that needs attention, not in a vague banner at the top of the page.
- Offer a way forward. Tell people what to do next, not only what went wrong.
- Keep their work. Never clear a form because of one mistake. Losing effort feels like punishment.
- Never blame. The tone should be calm and helpful, as if a patient colleague were sitting beside them.
These details seem small, but they shape how people feel about a product long after the error is fixed. A clear message says we expected this might happen and we are here to help. A cryptic one says you are on your own.
How you handle mistakes tells users how much you value them.
Don Norman wrote in The Design of Everyday Things, “Design is really an act of communication, which means having a deep understanding of the person with whom the designer is communicating.” An error message is that communication at the moment it matters most.
Good error messages are a form of respect. They protect people’s time, their effort, and their confidence.
And confident users come back.