The document discusses best practices for writing error messages. It provides guidance on including the problem, cause, and solution in messages. Additional tips include choosing the right format, being precise, writing for understanding, keeping messages short, avoiding blame or scare tactics, and ensuring the message is noticed. Error prevention strategies like validation and auto-correction are also covered. The document emphasizes finding ways to predict and prevent problems while giving users enough information to resolve issues calmly.
1 of 98
More Related Content
We can do better than "unknown error"
1. Charlotte Claussen
The UX Writer Conference June 9, 2021
Unknown error
We can do better than unknown
error
Charlotte Claussen @cphcharli
The UX Writer Conference June 2021
3. User
Error messages? I never know
what it is, so I turn off my
computer for a couple of hours.
6. Microsoft
A common belief is that error messages are the worst user
experience and should be avoided at all costs, but it is more accurate
to say that user confusion is the worst experience and should be
avoided at all costs. Sometimes that cost is a helpful error message.
Source: https://docs.microsoft.com/en-us/windows/win32/uxguide/mess-error
8. Problem Clearly state what has happened
Cause
Solution
The anatomy of an error message
9. Image credit: Unknown author, see for example https://medium.com/@thomasfuchs/how-to-write-an-error-message-883718173322and
https://www.expertreviews.co.uk/software/operating-systems/1401617/how-to-clean-install-windows-10-and-create-boot-media/page/0/1
11. Problem Clearly state what has happened
Cause Explain why the problem occurred
Solution
The anatomy of an error message
21. Types of error messages
Dialogs for critical information that the user must see or react to
In-line or contextual messages for input errors
Toasts for feedback on success or failure of a user action
Banners for errors that affect the system
Log entries for troubleshooting information for IT professionals
Email or chat messages for notifying IT professionals
22. Choose the right format
Be precise
Best practices
31. Choose the right format
Be precise
Write in a way that users can understand
Keep it short use progressive disclosure or help links when needed
Dont blame the users
Best practices
35. Choose the right format
Be precise
Write in a way that users can understand
Keep it short use progressive disclosure or help links when needed
Dont blame the users
Dont scare people
Best practices
38. Choose the right format
Be precise
Write in a way that users can understand
Keep it short use progressive disclosure or help links when needed
Dont blame the users
Dont scare people
Dont be funny or cute
Best practices
42. Choose the right format
Be precise
Write in a way that users can
understand
Keep it short
Dont blame the users
Dont scare people
Dont be funny or cute
Make sure it gets noticed
Best practices
46. Choose the right format
Be precise
Write in a way that users can
understand
Keep it short
Dont blame the users
Dont scare people
Dont be funny or cute
Make sure it gets noticed
One cause, one message
Best practices
49. Choose the right format
Be precise
Write in a way that users can
understand
Keep it short
Dont blame the users
Dont scare people
Dont be funny or cute
Make sure it gets noticed
One cause, one message
One user type, one message
Best practices
52. Choose the right format
Be precise
Write in a way that users can
understand
Keep it short
Dont blame the users
Dont scare people
Dont be funny or cute
Make sure it gets noticed
One cause, one message
One user type, one message
Dont be stupid
Best practices
59. Show previews of results before users commit
Use confirmation dialogs
Use descriptive microcopy in forms
Validate user input
Add helpful constraints
Support undo
Auto-correct misspellings and wrong formats
Fix issues in the background
Error prevention
61. Show previews of results before users commit
Use confirmation dialogs
Use descriptive microcopy in forms
Validate user input
Add helpful constraints
Support undo
Auto-correct misspellings and wrong formats
Fix issues in the background
Error prevention
63. Show previews of results before users commit
Use confirmation dialogs
Use descriptive microcopy in forms
Validate user input
Add helpful constraints
Support undo
Auto-correct misspellings and wrong formats
Fix issues in the background
Error prevention
65. Show previews of results before users commit
Use confirmation dialogs
Use descriptive microcopy in forms
Validate user input
Add helpful constraints
Support undo
Auto-correct misspellings and wrong formats
Fix issues in the background
Error prevention
67. Show previews of results before users commit
Use confirmation dialogs
Use descriptive microcopy in forms
Validate user input
Add helpful constraints
Support undo
Auto-correct misspellings and wrong formats
Fix issues in the background
Error prevention
69. Show previews of results before users commit
Use confirmation dialogs
Use descriptive microcopy in forms
Validate user input
Add helpful constraints
Support undo
Auto-correct misspellings and wrong formats
Fix issues in the background
Error prevention
71. Show previews of results before users commit
Use confirmation dialogs
Use descriptive microcopy in forms
Validate user input
Add helpful constraints
Support undo
Auto-correct misspellings and wrong formats
Fix issues in the background
Error prevention
73. Show previews of results before users commit
Use confirmation dialogs
Use descriptive microcopy in forms
Validate user input
Add helpful constraints
Support undo
Auto-correct misspellings and wrong formats
Fix issues in the background
Error prevention
87. PARTICIPANT_TRANSLATION_DICTIONARY_ADD_FAILED: Your
dictionary could not be added. Refresh the page and try
again
PARTICIPANT_TRANSLATION_DICTIONARY_ADD_FAILED: Your
dictionary could not be edited. Refresh the page and try
again
PARTICIPANT_TRANSLATION_DICTIONARY_ADD_FAILED: Your
dictionary could not be removed. Refresh the page and
try again
91. Ask! Developers, support people, testers
Test the software
Look at the text strings in the code
Ask again
What happens right before the error occurs?
Does the problem affect more than one thing?
Is there a risk of breaking anything or losing data?
What can the user try? How likely is that to work, in percent?
How to get information
92. Dont focus on rules, but think about this:
Find ways to predict and prevent problems
Give users the information they need to move on
Keep the users calm
Key take-aways