An error message is user-facing text that explains what went wrong, why it happened, and what the user can do next. Clear, succinct wording replaces vague notices such as “Something went wrong.” section 7.1.4
Useful error messages should:
- Describe the specific failure instead of using a generic system message. section 7.1.4
- Explain the likely cause, such as filters hiding all available data or insufficient permissions. section 7.1.4
- Offer a practical recovery step, such as removing filters, and appear close to the source of the problem in space and time. section 7.1.4 section 7.5
- Match the situation rather than forcing one message across different errors; light humor can work when it remains on-brand and safe for work. section 7.1.4
A message that helps
Instead of “An error occurred,” say: “Oops, you’ve filtered out all the data! Try removing some filters to coax it back.” The message names the problem and suggests the next move. section 7.1.4
Error messages are one part of error prevention. Disabling impossible date choices, for example, can stop users from creating an avoidable failure in the first place. section 7.1.4
