4 ms·
There’s more general concept of perception here that is worth thinking about. Users can get awfully confused by generic, misleading or overly technical error m
by dgb23 3y ago
There’s more general concept of perception here that is worth thinking about.
Users can get awfully confused by generic, misleading or overly technical error messages. So they call/write you and confuse you even more.
“There is something wrong about X.” Where X is some misinterpreted partial of a message. This only gets cleared up if you let them walk you through what happened step by step and/or examine logs etc.
Error messages are an important part of a UI. No matter if they’re user errors or internal errors.
There are always errors that you don’t foresee and just need to display generic messages for. But even then there should be a very clear, short(!) description and a unmistakable call to action.
- pixl97 3y agoUgh, not 15 minutes before this I was testing a new yet to be released version of my companies software. And while testing I get an error message like "Cannot do X with upload" Number one this is a behavior change and should not have been changed in the first place. But number two, all the error had to say was "Cannot do X with upload because application is set to Y" The first one generates a support ticket, the second one gives a legitimate reason on why the failure occurred and what they can do about it.