How to Design Error Messages
I haven’t written about one of my favorite services for several moths already, but as usual Pandora gave me a reason to post a comment. When I was trying to “thumb up” a song an error occurred. It wasn’t a typical error message however:
First, it’s written clearly and in human language. It’s as clear as a day which action failed. Second, I’m really touched when the application apologizes: “I’m sorry. It’s my fault.” So nice. Well written error message can really make the difference and even make the user feel better.
There are a couple of things more. The message window looks nice. Font is big and easily readable. There is no OK button, because it’s far from OK when I can’t use one of basic features. The retry option (the positive one) is more exposed than the cancel option (the negative one).
On the other hand you can find error messages like that:
It’s ugly and clumsy. It forces you to agree that it’s OK that the error has appeared. And for most of users it’s completely incomprehensible. On the contrary to Pandora's message that's the great example how error messages shouldn’t be made. Alas, not so rare example.


2 comments:
usually the second one allows you to find out how to try again. If you arenot lazy the second one is better.
That's not about being lazy. That's about user experience. User experience, not developer experience.
Yes, the chances are good that the second message will help me at least a bit to find out what went wrong. But that's only because I used to be a developer once. How many users have experience in software development?
Having said that the question is not if I'm lazy but if I care. I don't want to bother why the darn software doesn't work. That's not my job here. That's developer's part of the job. And they better have some logs, crash dumps or whatever to track the bug down. I don't hack my car when I want to drive to my workplace everyday. It just works or lights user-friendly controls when something is broken. The car doesn't dump technical details when it can't be started. I wouldn't understand it anyway. That's the mechanic's job.
I expect the same from the software I use. And most users are too.
Post a Comment