Something went wrong: How to write better error messages.
April 4, 2024
As UX professionals, we know that error messages are an inevitable part of the user experience. No matter how well-designed and tested your product is, there will always be something that goes awry. And when that happens, it's crucial to have clear and helpful error messages to guide the user through the problem. So, what makes a good error message? Here are a few tips to keep in mind:
Be specific. Don't just say "an error occurred" or "something went wrong." Tell the user exactly what the problem is, and why it's happening. For example, "Sorry, we couldn't save your changes because you're not connected to the internet."
Be actionable. Give the user a clear next step to take to resolve the issue. For example, "Please check your internet connection and try again."
Be human. Remember that the user is a person, not a machine. Use language that is easy to understand and avoid jargon.
Don't blame the user. Error messages can be frustrating, and the last thing you want to do is make the user feel like they did something wrong. Instead, take responsibility for the error and offer a solution.
Test, test, test. Make sure to test your error messages with real users to ensure they are clear and helpful.
In conclusion, writing good error messages is an art and science. It's important to remember to be specific, actionable, human, and don't blame the user. By following these tips, you'll be well on your way to creating error messages that will delight your users, instead of frustrating them.