How should you approach error messages to balance guidance and helpfulness?

How should you approach error messages to balance guidance and helpfulness?

• A. Generic, non-specific messages.
• B. Specific, actionable; avoid blaming; show how to fix and what happens next.
• C. Blame the user and shame.
• D. Only display error codes.

Answer: (B)

Error messages should be specific and actionable, guiding the user on how to fix the issue and what will happen next. Avoid blaming language and instead acknowledge the problem in a calm, constructive way, plus provide concrete steps to resolve it and a clear indication of the next system behavior. This approach helps users recover quickly, reduces confusion, and lowers support requests because people know exactly what to do and what to expect after they act. Generic messages leave users guessing and stuck, while blaming language undermines confidence and motivation. Relying only on error codes forces users to look up meanings, creating friction and frustration.

Error messages should be specific and actionable, guiding the user on how to fix the issue and what will happen next. Avoid blaming language and instead acknowledge the problem in a calm, constructive way, plus provide concrete steps to resolve it and a clear indication of the next system behavior. This approach helps users recover quickly, reduces confusion, and lowers support requests because people know exactly what to do and what to expect after they act. Generic messages leave users guessing and stuck, while blaming language undermines confidence and motivation. Relying only on error codes forces users to look up meanings, creating friction and frustration.