Defination
When errors occur, systems should communicate them clearly using understandable language and constructive guidance. Error messages should explain the problem, indicate its cause, and suggest actionable steps for recovery.
What Does It Mean?
When errors happen (and they will), users should:
👉 Recognize what went wrong.
👉 Understand (diagnose) why it happened.
👉 Recover by knowing what to do next.
In short: error messages should be clear, specific, and helpful.
Everyday Examples
• Bad: “Error 505.”
• Good: “Your password is too short. It must be at least 8 characters.”
• Bad: “Transaction failed.”
• Good: “Payment declined. Please check your card number or try another method.”
See the difference? The first set leaves you confused, the second guides you to fix the problem.
Why It Matters
• Reduces frustration – Users don’t feel lost or blamed.
• Builds trust – Helpful systems feel like partners, not enemies.
• Saves time – Clear recovery steps prevent trial-and-error guessing.
Unclear error messages make users quit, complain, or abandon the product altogether.
Case Study: Slack’s Playful Error Messages
Slack is famous for human-friendly error handling. For example, if something goes wrong, you might see:
“Hmm, something’s not working. Try refreshing, or we’ll get this fixed ASAP.”
It’s clear, polite, and even a little friendly—turning a negative moment into a manageable one.
Compare that to a cold “Error 404” page with no explanation—big difference!
Quick Tips for Designers
• Use plain language – Avoid codes; explain in human terms.
• Be specific – Tell users exactly what’s wrong.
• Offer solutions – Suggest steps to fix the problem.
• Stay polite – Don’t blame the user; errors are part of the system, not the person.
• Design recovery paths – Add “Try again,” “Back,” or “Contact support” options.
Next read:
Usability Heuristics 10- Help and Documentation
Was this article helpful?