I work in IT, and nothing against you, but a bunch of devs do write horrible, useless error messages. I can’t count the number of times I’ve seen an error message that just says “an error has occurred” and you’re left to figure out what error.
If the error message is that stupid, I’m 100% with you. I suspect that’s the result of a direct instruction to developers to dumb down the messages to avoid creating distress in users, which is idiotic.
However, final users in a corporate environment should be taught that if they get a message with a lot of information, and they don’t understand that information, it’s not for them, and they need to leave it alone or take precise notes of what the message says, so somebody from IT who does understand it can act on it. But most users act like the error message is radioactive or they’re participating in a competition of who can dismiss the message faster: when support asks about the error, they say hey don’t know because they have dismissed it.
Almost every finished product I’ve seen has a generic error message like that which makes it extremely frustrating when you’re technical and actually want to attempt to fix the problem. I had the same issue with a WiFi connected Canon printer. As a dev myself, I know how difficult it can be to write a useful error message for every edge case, but it’s not that difficult to be a bit helpful lol
Regarding users hatred of error messages: when I worked in my University’s computer lab about 15 years ago a student complained that she couldn’t download a file. I went with her to see what the issue was and had her show me what she was doing. She’d attempt to download the file, quickly dismiss a pop-up, and then angrily say “see?! It’s not working!!”. I told her to do it again, but not dismiss the pop-up so quickly so I could see what it said. Of course, it was asking for permission to save the file to the HDD and she kept clicking “no” 🤦♂️
I told her to do it again, but not dismiss the pop-up so quickly so I could see what it said.
I shit you not, I’ve had a user do worse.
I’ve done the same exact scenario as you with one difference. I told her the same thing you did. And then. She closed the message again. While I was pointing at it, and asking her to read it out loud.
I.
Pointed. At the screen. And said read this out loud.
If the error message is that stupid, I’m 100% with you. I suspect that’s the result of a direct instruction to developers to dumb down the messages to avoid creating distress in users, which is idiotic.
However, final users in a corporate environment should be taught that if they get a message with a lot of information, and they don’t understand that information, it’s not for them, and they need to leave it alone or take precise notes of what the message says, so somebody from IT who does understand it can act on it. But most users act like the error message is radioactive or they’re participating in a competition of who can dismiss the message faster: when support asks about the error, they say hey don’t know because they have dismissed it.
Almost every finished product I’ve seen has a generic error message like that which makes it extremely frustrating when you’re technical and actually want to attempt to fix the problem. I had the same issue with a WiFi connected Canon printer. As a dev myself, I know how difficult it can be to write a useful error message for every edge case, but it’s not that difficult to be a bit helpful lol
Regarding users hatred of error messages: when I worked in my University’s computer lab about 15 years ago a student complained that she couldn’t download a file. I went with her to see what the issue was and had her show me what she was doing. She’d attempt to download the file, quickly dismiss a pop-up, and then angrily say “see?! It’s not working!!”. I told her to do it again, but not dismiss the pop-up so quickly so I could see what it said. Of course, it was asking for permission to save the file to the HDD and she kept clicking “no” 🤦♂️
I shit you not, I’ve had a user do worse.
I’ve done the same exact scenario as you with one difference. I told her the same thing you did. And then. She closed the message again. While I was pointing at it, and asking her to read it out loud.
I.
Pointed. At the screen. And said read this out loud.
She moved her mouse to my finger.
And closed the message.
I.
Can’t.