User-Friendly Error Message Principles
You'll learn the four core principles that transform confusing technical errors into helpful, human-centered messages.
Why Error Messages Matter
When things go wrong, your error messages are often the only communication between your app and a frustrated user. A good error message can mean the difference between a user fixing the issue themselves or abandoning your site entirely.
The Four Core Principles
1. Clarity
Say exactly what happened in simple language. Instead of "ERR_NULL_REFERENCE", say "We couldn't find your profile information."
Think of it like a GPS: "Recalculating route" is clearer than "NAV_ERROR_CODE_2847."
2. Actionability
Tell users what they can do about it. Don't just say something failed—explain the next step.
- ❌ Bad: "Authentication failed"
- ✅ Good: "Your password was incorrect. Please try again or reset your password."
3. Empathy
Use a friendly, understanding tone. Avoid blaming the user. Remember: they're already frustrated.
- ❌ Bad: "You entered an invalid email"
- ✅ Good: "That email format doesn't look quite right. Please check and try again."
4. Avoid Technical Jargon
Your users aren't developers. Skip the stack traces, error codes, and internal terminology.
- ❌ Bad: "CORS policy violation on preflight request"
- ✅ Good: "We're having trouble connecting right now. Please try again in a moment."
Real-World Application
These principles work together. A well-crafted message is clear ("Payment failed"), actionable ("Please check your card details"), and empathetic ("Don't worry—no charges were made"), all without mentioning "HTTP 402" or "transaction_id: null".
Key Takeaway: Great error messages are clear, actionable, empathetic, and jargon-free—they guide users toward solutions instead of leaving them confused and helpless.