Frame errors as system conditions.
Never attribute failures to users.
Contents 7. Trust, Safety & Responsibility 3. Error Communication
How systems communicate when things go wrong.
First, ask yourself
“Does your system help users recover instead of assigning blame?”
Mission statement
Ensure users respond appropriately to issues by explaining errors clearly without vagueness or blame.
Key heuristics Error Communication
- Errors must be framed as system conditions, not user faults.
- Error messaging must use system-owned, respectful language.
- Failure communication must remain calm and respectful.
- Failures must be described clearly in understandable language.
- Error messages must specify where and why the issue occurred.
- Clear guidance for resolution and continuation must accompany errors.
- Language urgency must match actual impact.
- Technical causes must be translated into user-relevant terms.
- Failure messaging must support continued engagement.
Executive brief
The system must communicate errors in ways that support users, not judge them.
Core questions Error Communication
“When errors occur, does the system guide and support users, or assign blame?”
“Do error messages help users recover effectively?”
Focus areas
Tone-first
“Does the system speak with users, not at them?”
“Is the language calm and respectful under failure?”
Action-first
“Does the message explain what to do next?”
“Can users fix the problem without guessing?”
Trust-aware
“Does the error handling build confidence rather than anxiety?”
“Would users feel safe making mistakes?”
AI-aware
“Are uncertainty and system limits communicated?”
“Does automation take responsibility for its failures?”
UX directives Error Communication
Use system-owned language in error messaging.
Communicate accountability clearly and respectfully.
Maintain calm, respectful tone.
Do not use language that induces stress or defensiveness.
Provide clear explanation of failures.
Describe what occurred in plain language.
Localize and specify error context.
Identify where and why issues occurred.
Include actionable recovery guidance.
Provide clear instructions for resolution and continuation.
Calibrate language to consequence.
Match urgency and emphasis to actual impact.
Translate technical causes into user-relevant language.
Do not expose internal system terminology unnecessarily.
Protect user confidence after failure.
Ensure messaging supports continued engagement.
Executive summary
- Error Communication frames failures as system conditions, not user faults.
- It communicates accountability clearly, calmly, and respectfully.
- The system must explain what occurred, where it occurred, and why it matters in user-relevant language.
- Messages must include actionable guidance that supports immediate recovery and continuation.
- Tone and urgency must align proportionally with actual consequence.
- Error Communication succeeds when users remain confident, informed, and able to proceed after failure.
Success indicators
- Error messages clearly explain what happened.
- The system takes responsibility for the problem.
- Messages use calm and respectful language.
- Errors identify where the problem occurred.
- Users are given clear steps to resolve the issue.
One-line summary
Before users can recover from failure, they must be spoken to clearly and respectfully.