Annoyances.
by
saintlupus
·
· Score: 5, Insightful
It may be annoying to my end users when I attempt to explain things to them and they don't understand the terms I'm using.
But it's annoying to me when they insist on being ignorant about the tools that they need to do their jobs, and that I'm paid to maintain. A tiny bit of effort on their part would pay huge dividends.
Why is is that people think being ignorant of how a computer works is something to be so damned _proud_ of? Nobody says "I'm car-illiterate" with a little chuckle after they wrap a sedan around a tree, but users who accidentally destroy their computers somehow think it's IT's fault.
IT has its own annoying quirks. Langer says some IT people label users as neophytes and then blame them for any difficulties. "The user insists their e-mail doesn't work, and the IT person says, 'My e-mail works perfectly,' and assumes the user is the problem. Users really find this annoying," he says.
Ha! Here's how that typical scenario goes...
USER: My e-mail doesn't work.
IT: What's wrong?
USER: I can't send e-mail. E-Mail doesn't work. The system must be down.
IT: None of the other 1700 employees have had any problems at all today with their e-mail. Can you be more specific about what your problem is?
USER: It doesn't work for me.
IT: Did the computer give you any error message?
USER: I think so but I wasn't paying attention.
IT: You realize that when something goes wrong on the computer, it tells you what went wrong? That message helps us know what the problem is?
As much as you're going to hate this, in this scenario the IT user is the poor communicator. The user in your scenario doesn't have the skill set to communicate properly.
Ask questions like:
"Can you start the program?" "Are you using web mail?" ("desktop client" may be too high-brow or technical for them - believe it or not, and most people know what web mail is - obviously there's only two choices here)
The last thing the IT user says is really condescending. This is exactly what the article talks about.
No, you don't have it straight.
by
schon
·
· Score: 5, Insightful
It's not what you say, it's how you say it.
This is annoying: "Well, my email is working, so it must be a problem on your end."
This is not: "Hmm, let me check our mail server - well, everything seems OK there, let's see if the problem is on your computer."
Two ways of saying the same thing, one is antagonistic, the other is constructive.
That's what social skills are all about - learning to communicate effectively.
Um...because using a computer is more complex?
by
rd_syringe
·
· Score: 5, Insightful
How about because using a computer is more complex than driving car?
This is the exact lack of perspective in IT people that I wrote about in another post. Just because you understand what a "command prompt" is doesn't mean everyone else does. But the majority of us knows how to push a gas pedal and steer a wheel.
Computers, unlike cars, constantly have problems that require checking the internal hardware or software configurations. Do you know how to refit your car's exhaust manifold? If cars were as flaky as computers, wouldn't you feel annoyed at the anti-social, nerdy car mechanics whose lives are spent arguing over car model brands as though they're religions, and taking time out of their oh-so-busy schedules of bitching to each other in order to fix your incessant problems?
Yeah...perspective is good.
Re:The answer is
by
Gabrill
·
· Score: 5, Insightful
That's not an article. It's an advertisement for a book.
-- Always going forward, 'cause we can't find reverse.
Re:Even if it's user error...
by
fermion
·
· Score: 5, Insightful
I will one step further. The humans in the process are able to be retrained or terminated. But another part of the process is available resources and human vagaries. For example, there may be no resources for training or replacement with more qualified humans. Likewise, the process may not allow particular humans to be terminated, either because of real or perceived value.
Now, the help desk people generally do not have the personal or company resources to adjust the processes to accommodate the available humans. However, there are many people in every organization who do have these resources, and yet do nothing. They sit at their expensive desks jacking off and shopping instead of finding creative solutions to quality and user interface issues. They blame the wage slaves and customers for not precisely following their half assed implementation of a process. They waste company resources by making expensive wage slave replacement a part of the process. I have seen both sides of this, so I am not talking from theory.
So, if you see a problem, and cannot fix it yourself, document the problem, think of a solution, and don't just blame the people calling you.
-- "She's a scientist and a lesbian. She's not going to let it slide."
Orphan Black
It may be annoying to my end users when I attempt to explain things to them and they don't understand the terms I'm using.
But it's annoying to me when they insist on being ignorant about the tools that they need to do their jobs, and that I'm paid to maintain. A tiny bit of effort on their part would pay huge dividends.
Why is is that people think being ignorant of how a computer works is something to be so damned _proud_ of? Nobody says "I'm car-illiterate" with a little chuckle after they wrap a sedan around a tree, but users who accidentally destroy their computers somehow think it's IT's fault.
--saint
IT has its own annoying quirks. Langer says some IT people label users as neophytes and then blame them for any difficulties. "The user insists their e-mail doesn't work, and the IT person says, 'My e-mail works perfectly,' and assumes the user is the problem. Users really find this annoying," he says.
Ha! Here's how that typical scenario goes...
USER: My e-mail doesn't work.
IT: What's wrong?
USER: I can't send e-mail. E-Mail doesn't work. The system must be down.
IT: None of the other 1700 employees have had any problems at all today with their e-mail. Can you be more specific about what your problem is?
USER: It doesn't work for me.
IT: Did the computer give you any error message?
USER: I think so but I wasn't paying attention.
IT: You realize that when something goes wrong on the computer, it tells you what went wrong? That message helps us know what the problem is?
USER: Yes, but e-mail doesn't work.
It's not what you say, it's how you say it.
This is annoying:
"Well, my email is working, so it must be a problem on your end."
This is not:
"Hmm, let me check our mail server - well, everything seems OK there, let's see if the problem is on your computer."
Two ways of saying the same thing, one is antagonistic, the other is constructive.
That's what social skills are all about - learning to communicate effectively.
How about because using a computer is more complex than driving car?
This is the exact lack of perspective in IT people that I wrote about in another post. Just because you understand what a "command prompt" is doesn't mean everyone else does. But the majority of us knows how to push a gas pedal and steer a wheel.
Computers, unlike cars, constantly have problems that require checking the internal hardware or software configurations. Do you know how to refit your car's exhaust manifold? If cars were as flaky as computers, wouldn't you feel annoyed at the anti-social, nerdy car mechanics whose lives are spent arguing over car model brands as though they're religions, and taking time out of their oh-so-busy schedules of bitching to each other in order to fix your incessant problems?
Yeah...perspective is good.
That's not an article. It's an advertisement for a book.
Always going forward, 'cause we can't find reverse.
Now, the help desk people generally do not have the personal or company resources to adjust the processes to accommodate the available humans. However, there are many people in every organization who do have these resources, and yet do nothing. They sit at their expensive desks jacking off and shopping instead of finding creative solutions to quality and user interface issues. They blame the wage slaves and customers for not precisely following their half assed implementation of a process. They waste company resources by making expensive wage slave replacement a part of the process. I have seen both sides of this, so I am not talking from theory.
So, if you see a problem, and cannot fix it yourself, document the problem, think of a solution, and don't just blame the people calling you.
"She's a scientist and a lesbian. She's not going to let it slide." Orphan Black