The screenshot shows an error message from a computer in the library. The error message says: “Could not perform this operation because the default mail client is not properly installed.”. There appears to be a of technical error. Errors are a an unfortunate part of the human-machine interaction. As they interfere with the intended task by their nature, error messages can degrade user experience, particularly if the message does not follow basic principles.

1. The message should communicate be clear and addressed to the audience. A non-technical user group should be spared of technical details, instead provide a simple statement. The original error text includes technical language which most users do not understand nor care about. It just raises anger to be “bothered” by the error in the first place and then to be denied an understanding of what is happening. The message should also be kept short.

2. Relate to what the user wanted to do. In case of this error message, for example, “There is a technical problem, action* could not be performed.”. *action should refer to the interaction that the user wanted to conduct.

3. An error message should include an advice to the user. For example, “Please try again later.” if someone is already working on the problem or “Please ask your administrator Ms. XZY for help: email: … phone: …” if a responsible person can be contacted.

4. The message might include something personal “we” and an excuse, “We are sorry.”. Whereas this does not change the situation, it helps people to relieve some of the caused negative emotions and can enhance user experience of the whole ordeal.

5. The user experience of the dialogue can be further turned positive if the error message includes something funny, for example, a photo or joke. Later in this everyday usability series I will show a collection of well designed error message