3 ms·
For me error messages come in two forms. 1. For the user. You can't do that (maybe explain why). Don't do that. 2. Error that's actually there for the suppo
by duxup 4y ago
For me error messages come in two forms.
1. For the user.
You can't do that (maybe explain why). Don't do that.
2. Error that's actually there for the support or engineering team for a customer to convey to support, probably with a handy copy to clipboard link (that the user has at best a 50/50 chance of using no matter how much prodding).
That's it.
Humans generally lock up hard when they see an error in my experience. No amount of information or hand holding will help most of them figure it out. It's better to try to solve it in software.
If the software can't fix the issue internally then they get an error message and 2 things happen:
1. The user is going to try something else and solve it themself (awesome) regardless of the error because they're smart and capable people and could probably solve it no matter what you told them.
2. Their brain locks up, they do the same thing 20 times and get the same result and complain to support with some form of "doesn't work". Doesn't matter what error you give them, they won't even try to tell you what the error was / doesn't register in their brain unless it had a cute cat on it or something (that actually works... so forget this "tone" stuff).
I like the article, but I am skeptical about a UX team who doesn't answer support tickets ... just magically knows what the user is thinking / will work. I get lots of advice on error messages, I change them when they ask, but when it's from folks inside the company who know the product it often isn't helpful.
Heck even users give bad advice about errors. I've had them tell me "Well it should have said X" where X is exactly word for word what it said (they forgot...).
Granted I still try to help the user along, but I'm skeptical that software with any large user base can have "good" error messages.