Discussion Locked

DOWNLOAD: The top ten peeves of a support tech

0 helpful
297 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is page 2 of the discussion. Read the opening post

297 replies

by emj65

that those people who constantly call the Helpdesk about not being able to do something they've been doing for YEARS, and ask the same questions over and over again, are the ones who can figure out how to upload a picture and set it as their desktop wallpaper? It's almost as if the work-related stuff is just too hard, but when it's something personal, they'll move mountains to figure it out?! This just aggravates me to no end. These are the same people who will ONLY learn just enough to get by, and won't try anything new, and god forbid we change something (we send e-mails, reminder e-mails, and sit with the deparment before any changes are made), it takes them WEEKS to learn the new format, even if it's only a small change. Am I bitter? Nahhhh.

by rtyo

Yes, what we do often appears as magic. When I run into the "I tried that but it didn't work for me" situation I smile, and say "Yes, but I'll wager your not wearing magic computer fixing jockey shorts."

by graytalon

I had a user that just had a multitude of problems. I could never replicate them. I figured he was just fat fingering the keyboard. I then explained to him that I would work some real magic, but it would only last as long as the item I worked it on stayed in contact with the computer. He said anything would be great. I took a penny, put a blob of black paint under Lincoln's chin. I explained a ritual was worked on the penny because it conducted electrons like a copper wire.

He taped it to his chasis and I didn't get another call from him for months.

by rtyo

"but sometimes the users will refuse any and all blame"

Tthe users will refuse any and all blame- ALWAYS.

by jbusch1

"I have been working on this very important proposal/deliverable/whatever for over six hours and my machine locked up. I haven't saved it since this morning. What are you going to do?!!"

Is it too hard for folks to save files!

by rayjeff

No, it isn't hard. Even if you don't want to remember to save every now and then, SET IT TO SAVE ITSELF!!!

I've told several students that, and they still don't take the hint. Oh, and let's not forget to start a document up and work on it for hours and then you see the ubitious (SP) "Document 1"...

by jjpspam

... sounds like my married father-in-law who uses the computer soley to surf pr0n and chat with his online girl friend.

He calls several times a year.

FIL: My computer's broke.
ME: What's wrong with it?
FIL: It won't Yahoo!

Arghh!

by tonyj_stirling

I get the impression from your post, (perhaps wrongly!) that you might not be aware that the BOFH is still going strong? (Though the same can't be said for his many bosses or users!)

Simon Travaglia brightens up my Friday each week, and the BOFH can be found at www.theregister.co.uk/odds/bofh

Thought you might like to know...

by cheesel

Sometimes, do you ever get to the point that when you hear foot steps coming toward your cube, you just want to hide under the desk?

by cheesel

computer down? Never fear...Info Uppers are here! And to let your computer sleep, try Data Downers!

by cheesel

Yeah, but they call you days later when you have forgotten about their problem and simply say: "It is happening again!" Excuse me, but WHAT is happening again??

renee

by jessie

They call you a week later saying it's happening again and they blame YOU for not fixing it right the first time!

by kevin

I can't take credit for these, nor do I know where they originated...but they always get a grin from every service person I've shared them with :-)

HOW TO GET BETTER SERVICE ON YOUR MACHINE

1. Do not call for service until everyone concerned has had time to form an opinion as to what is wrong. Allow each person the chance to correct the problem. Whenever possible, all controls and adjusting screws should be turned.
2. After several days, when the machine malfunction has become a major emergency, place an urgent call for service. Friday afternoons are best, but anytime after 4:00 p.m. is OK.
3. Alert all personnel so that each can give their version of what is wrong. Suggestions on how to fix the machine will be welcomed by the service man.
4. Hide the service history log that is found inside the machine. Make several references to the man who was here for the same problem last week.
5. Have at least eight graduate engineers present to ask highly technical questions which are in no way related to the immediate problem.
6. The minute the service man arrives, ask what caused the delay. Make it clear that he was to arrive two days ago. Before he can answer, ask him when the machine will be back in service.
7. The machine should be as dirty and greasy as possible. A mixture of oil and pencil sharpener shavings work well. If the machine has electrical components, add staples and paper clips.
8. Assign someone to supervise the repair. A person who has never seen the machine before is preferred. Bad breath is a big plus.
9. Ask again when the machine will be ready for use.
10. Be sure that the lights are off in the room where the machine is to be repaired. A good service man can fix them blindfolded.
11. When the repair is completed, tell him what a swell job he did. Tell him that the job should be swell, it took long enough.
12. Try to talk the service man down on the bill. Those big companies make too much money anyway.
13. After the service man has gone, call his supervisor and tell him the machine is now worse than it was before. Follow up with a letter and send a copy to the company's home office.
14. Ask if the machine is ready yet. If the service man is looking at a schematic diagram, ask if he knows what he is doing.
15. Follow the above rules on every service call, no matter how small the problem is.

by br-549

I had to download a zip --> extract --> open with/load acrobat. For an article that would have loaded instantly as a web page from the site.

by ex-military nut

I like your screen name.

BR549 and ID10t are a couple of temporary passwords I use when users can't remember theirs. And these are the same people who think they can function without us? Go figure. If they only knew!

by cheesel

a food service place. I was upgrading Dunkin' donuts cash registers. Mind you, it could have been much worse, but the pounds of decaying (and sometimes wet) coffee beans under the counters were pretty nasty.

by jaydev

i cannot stand when they report something because they heard it from other department. Oh, we need that patch, fix too. I heard from dept XYZ and they said it's a must patch.
I ask are you have a problem?
Why do you need the patch? I don't want to have that problem...
Those users who want all the patches to avoid potential issues, should take advil, tylenol, asprin and all other medications so they don't get sick... Dummies...

by sbmknight

I have a problem with people who are not competent to do the job they were hired for, and expect the help desk staff to teach them how to do their job... in particular, secretaries who don't know how to use Microsoft Word or Windows, and need to be told *repeatedly* how to perform the most basic tasks. Or people who call because they don't know how to do something, then don't bother to pay attention while you "show them how" (i.e. do it for them...)

by robin.hunt

I agree with all 10 peeves and have dealt with every one of them. My current and most irritating peeve is developers/users insisting they MUST have Admin rights to their desktop in order to do their job. On numerous occasions, we have granted admin rights, only to turn right back around and have the user calling and complaining about their machine running extremely slow or "tons of pop-ups" appearing on their machine. As usual their desktops are inundated with spyware and erroneous software that has been downloaded and now creating problems. Upper management says they will back me on "no admin rights", however, when a user/developer "whines" to a VP, I end up having to give them admin rights. As a result of this constant battle, I also have numerous unlicensed applications that they have installed. I'm damned if I do, and damned if I don't. Does anyone have any suggestions?

by fractalzoom

VPs understand dollars, and you can best make your point if you can speak their language. Can you quantify these events and translate it into a specific amount of increased support costs? A veep won't get it if you go on about spyware and erroneous software, but will perk his/her ears if you can point to an added $3500 or $5000 in support costs.

Translate it into their language!

by fractalzoom

As an IT support professional with 20 years in the trenches helping people use computers to conduct business, I feel the collective pain of many techs posting to this thread.

However, as I read through this list of complaints, I am reminded of a key point: WE ARE PROFESSIONALS. Dealing with these kinds of issues is what we are *paid to do*. While there's certainly a value in venting or blowing off steam among other techs, there's also a danger in indulging in too much of this kind of discourse -- not far below the surface of many of these postings I detect a level of contempt for the IT customers. It's potentially corrosive.

IT exists to aid and propel the business, not the other way around. And after we're done complaining up here, it's important to keep our eyes on the real goal.

My two cents...

by banzairunner

I was in the men's room...minding my own busines...taking care of business...when a user walks up to the urinal next to mine. Here's the worst part, he's done! He's already washed his hands!! He just comes over to the urinal next to mine and says "I know this may not be the best place or time but i have a computer question." I should've turned to face him in mid-stream and said "Sure, what would you like to know." while watering his shoes. But, I stayed professional and answered his query. Geesh! Can't even pee in peace!

by Former member

It's gotten so bad if I walk into the restroom and see a known offender of the sort you described, I will turn and walk out so I can come back five minutes later. Or visit another facility in the building.

by houndog

Had the same thing happen to me! The guy even put his hand on my shoulder to be sure he had my attention. He almost got more than my attantion, more like a good soaking. :)

by chris029

I have worked in many different pc shops, and in a hospital where almost all the employee's were well trained and educated-- they would shut down a monitor to reboot and say the problem was still there. Imagine that.

by rayjeff

Prime example. Last night, a student called me to ask me to "do what I did for her last disk". Monday, the student had a floppy with work on it that she couldn't open. So I did the normal thing of running Chkdsk. I was able to pull the work up, even though the disk was bad.

Yesterday, same thing, different disk. Ok, the student lives an hour away. Because I knew the student would've been able to follow my directions, I told her to come back on-campus to see what I could do. She asked me if the disk would be fixed like the other one. I told her plainly that there was a 50/50 chance it would work, if the situation wasn't the same. She came in. I'm sure I worked on it for about 15-25 minutes. Ended up instead of her three files being on the disk, all were lost. There wasn't anything I could tell her outside of the disk being bad, which it was. So she left, but not before I got that "look". The look of "I thought you could save my work". SOmetimes it's just not possible.

Users wait until it's at the point of no return before they come to you with their problem and then they EXPECT you to fix it. THey don't realize that they should come right when the problem occures so there can be a better chance of success. Just like with printing. You have like six people printing documents and the documents don't come out. What do they do? The universal response of "keep pressing print", instead of coming to you when it doesn't print the first time. And because the printers have no management system or even connected to a print server, I have to go to the individual computers and troubleshoot.

by rayjeff

I am glad to have been able to learn and use DOS before it was completely phased out. It was so neat to be able to use it. I also keep my handy Windows Startup Disk, made from Win 98. When I partition a hard drive, initially, I use it. It's just something about that control you have in DOS that keeps me using it rather than using a partitioning app.

by rayjeff

That's one of the most craziest things I've ever heard. It makes no sense. it's like reading the end the middle of a textbook without getting the foundations from the beginning chapters. And then when some simple (to us) goes wrong, who does it fall back on the help the num-nuts???

by Former member

You'd be surprised by the number of people who seem to think they don't need to learn the basics before they use a spreadsheet or word processor. The computer is supposed to read their minds, I guess.

by caughtlbw

Over my years in IT I've come across every one of these issues, and more.

But as I get older, I'm actually becoming more sympathetic to the User's point of view, and less tolerant of my colleagues attitudes and approaches.

This is particularly true today. There are few jobs in the modern office that can be done without a working computer. And the provision of that equipment is close to ubiquitous.

So for most Users the pc is no different to the telephone on their desk, or the coffee pot in the staff kitchen. It's a fundamental tool without which they cannot work. And as a fundamental tool it should simply work. And if it worked yesterday, it should work the same today. Why not?

I pick up my phone, and I hear dial tone. I press some buttons, and I'm talking to my friend in Rome. The intervening technology is irrelevant to me.

I don't feel inadequate if I cant distinguish an NU tone from an Italian Ring Tone.

I spend half my life in an automobile. I'm only vaguely aware of the workings of a reciprocating internal combustion engine. The technology under the hood is irrelevant to me.

I don't feel inadequate if I cant describe some annoying rattle as coming from the fuel pump rather than the tappets.

This is the attitude that most people take to ubiquitous technology, and so it's the attitude that our Users (correctly) take to the pc sitting on their desk.

They dont care about the underlying technology. They dont believe that they should need to understand, or be able to describe in anything close to correct terminology, the design, implementation, or operation of that technology.

There's a certain intellectual snobbishness that underlies a lot of our complaints about Users. "So-and-so didn't know that you couldn't do thingamy unless you'd already enabled gargly-twit. What a tosser!" This strokes our ego (and given the low profile of IT in so many companies, our egos are often in dire need of stroking).

This also shows up in our intolerance of User's lack of understanding of our terminology. One of my favourites is "domain". Why should any User have to know diddly-squat about what we mean by the word "domain"?

The last two years I've spent my time visiting our remote offices to provide on-site support to our Users. In a lot of cases, these Users have never touched a pc before starting in their current position. On the other hand, especially in the larger offices, they have used pc's all their working life.

Invariably, I've found that if you treat Users as the people that they are, with respect, and in language that has meaning to them, they respond with tolerance, patience, and a surprising willingness to help.

by fractalzoom

I am in full agreement with this statement. There is a prevalent tendency among IT techs to adopt an "us-and-them" approach which ultimately proves toxic to building a viable, working relationship with the business -- you know, that activity that we're ultimately being paid to support?

I thought all those Bastard Operator From Hell essays were really funny. But that doesn't mean it's a viable way to conduct business. If we feel contempt for our users, we won't be able to engage as partners with them.

by rayjeff

I've read the past few posting how the feelings of the majority of us maybe/are not conducive to the users and our employers.

I can agree with that. But what if you work at a place that is technology-driven or technology is an important part of the place. Colleges and universities are hotbeds of technology and I'm sure it's generally expected that faculty/staff be able to use the technology that's implemented/used. I've worked for at three colleges for 7 years now (currently at the 3 college). The first two colleges used technology alot, it's their bread and butter. The faculty/staff had a better than average grasp of how to use it. The current college I work at, technology isn't as much stressed but to compete, technology is implemented more and more. But the training isn't what it should be. Much of that comes down to the faculty/staff not willing to learn. So how do you get people who need the technology to understand they need to learn how to use the technology. If they are trained to begin with, when user issues come up, it makes it easier on the IT staff to figure out a solution.

by old_guy

Its easy for us to forget that once upon a time we to were newbie?s, and as such we had to ask some of these same questions.

Yes, I will agree that there are those that seem to ask the same old tired questions over and over and ....well you get the point. My point is, I have found that at times, it was in fact me who was unable to find a common ground to communicate with my users.

So with a little patience and understanding I found that with most people (not all) I was able to do my job, which is in fact to provide the service the user needs within the organization, to do their job. Being the resident Geek, or that IT guy, is the work I prefer to do and I knew that some days????..

by hal 9000

It still does make it very hard to fix a problem when the person walks out of the office because their computer isn't working and leaves the thing locked and the office locked so no one can get in and rummage about in their personal effects.

Of course I always just have to love the ones who told you a password 2 years ago and expect you to still remember it.

This is a two way street the end user has to show some gratitude for your work as well and not be the one constantly complaining because they have locked away something and you have been unable to fix it while they have been away.

A few years ago I had a CEO's computer constantly falling over and loosing the MBR's which was more than a bit confusing and required many hours of data recovery followed by a complete reload and data restore. To him it was just an inconvenience and shoddy hardware that was causing the problem but when he eventually stayed put to give me a piece of his mind for such a bad computer I found a mobile phone directly beside a scanner that he had fitted and once that was removed there where no more problems.

I'm more than willing to walk that extra mile but it gets really hard when you are abused for the end users lack of knowledge and actual physical damage that they cause. Or the fact that you can not gain access to the broken computer to fix it up as the person has left the office and locked everything up. :D

Col ]:)

by caughtlbw

Don't get me wrong. I don't suffer fools! And of course some people are just not nice people.

But even in these cases it's often worth standing back and looking at things in a broader context.

For instance, sometimes to the User we simply become the embodiment of all that is IT. And they unload all their frustration on hapless us. It's unfair. But understandable. And we've all of us being guilty at some point of the same thing. (Just yesterday I was inexcusably rude to the poor lass on reception coz she didn't have my new security fob. Like it was her fault!)

And then there's differences in mental approach. As IT people we tend to have quite linear, analytical, logical ways of thinking. That's what makes us good at our job. But it can also make it very difficult for us to appreciate that there are other, quite different, ways of thinking. And that these other ways of thinking are equally valid. And that thinking in those other ways is what makes other people good at *their* jobs.

And therefore descriptions or explanations or procedures that to us are simple, indeed trivial, are to other people almost incomprehensible.

I have a friend who's a Visual Merchandiser (fancy name for window dresser). I can look at a shop display window and think it's perfectly ok. He then comes along and: moves that from there to there, turns this slightly around, changes the color of that. A few seemingly tiny alterations. And the display is transformed! I can SEE the difference. But I have absolutely no idea of WHY there's a difference. To him it's simple. He barely has to think about it. It's just obvious. To me it's incomprehensible. And always will be, no matter how he tries to explain it to me, coz my brain just doesn't work that way.

I've certainly had similar experiences to the ones you described! Sometimes I've been able to turn them around, even to my own amusement.

The issue of locked offices I've come across many times. And you know, it's often quite easy to "unlock" that office. ;) (or desk, or filing cabinet) In which case I take pleasure in fixing the pc, leaving a large post-it stuck to the monitor with an appropriate message, and re-locking the office on my way out.

I remember in my very first paid IT job I was in the office by myself on a Saturday, and took a phone call from the company owner. He wanted me to go into his office, log on to his pc, and email him a document that he needed to work on at home. At this point he stopped, realising that his office was locked and I wouldn't be able to get in. I just said "don't worry, I'm already in". The stunned silence on the phone was a joy!

A lot of situations I try to deflect with humour, and then turn to advantage.

For instance, the expectation that I remember a 2 year old password. I might respond with exaggerated shock and say: "You mean you haven't changed your password in 2 years? I'm very sorry, but that's against company policy. Failure to change your password regularly is a sackable offence!"

You can then smile and everybody enjoys the small joke. But it then easily leads on to a friendly discussion about why it's important to change passwords, and why data security is important, and how we use User identities (of which the password is part) to audit activity, and the implications of this, and so on.

And I always try and be constructive. Users often avoid changing passwords, or they choose absurdly obvious passwords, because they find them difficult to remember. So I give them a tool for generating non-obvious but memorable passwords that I use myself.

Take a famous phrase, or a line from a poem, or somesuch, and use the first letter of each word as your password.

"My life hath fallen into the sear, the yellow leaf!"

password is "mlhfitstyl".

So as you sit down each morning to log on, you simply repeat the phrase as a mantra, typing as you go.

Ok, maybe not a method that will work for everyone. But by offering a potential solution to their problem you've shown that you understand, and take them seriously.

Finally, rather more often than we might admit the User is, actually, right.

If I understand correctly the example you gave, you were saying that a mobile phone was placed next to a scanner, the RF emmissions from the phone were being picked up by the scanner's cable and conducted back into the pc, and was then causing the pc to malfunction.

Well, if so then it WAS a shoddy pc! It was poorly designed.

Ok, it wasn't your fault, and you cant be expected to anticipate everything. But, essentially, the User was right.

In these cases I'll always say exactly that. I'll tell the User that they're right (it's both true, AND strokes their ego) and explain why they were right (which also will usually show that I'm not at fault). At this point we both understand the problem, and the User can then make a decision about how to resolve it.

In the example you give, it would be "Yes, I can replace this shoddy pc for you, or you can avoid putting your phone too close to that cable."

There are always Users with whom no approach will ever make a difference. Of course! But I truly think they're few and far between.

by hcetrepus

I have an excellent working relationship with everyone I've done any level of work for, even the ones I dont care for personally.

However, I'm the pee-on, and they are the highly educated. It is a wonder that I am not required to turn on their computers in the morning, and shut them down in the afternoon.

This is a light humor thread, wish I could see more from your point of view, but in my shoes, today at least, I cannot.

by avid

when the client is a 80 something year old lady and who gets all in your personal space and insists on touching you while she leans over your shoulder. and you sit there thinking "lady could you please get your breasts off my back !"
ick !!!

by fractalzoom

I see the situation you're up against in the academic world -- the aim of the organization is not as easily measurable as in the commercial world.

Ultimately, it's an IT operation's responsibility to be aligned with the aims of the organization it is supporting. The goals and priorities of the organization need to drive the goals and priorities of IT. And that can ultimately only be achieved by the IT leadership, by their establishing a partnership and level of communication with the organization that facilitates cooperation in selecting and deploying technologies. It becomes the differnce between IT being reactive (having things done to it and having to respond) and proactive (being engaged in the planning, and being a listened-to voice in establishing the training and support requirements.)

Of course, the unfortunate part is that this can't be driven by the techs in the trenches, who bear the brunt of the abuse. IT leadership has to be an advocate for IT out in the business while being an advocate for the business within IT. And until IT management gets a clue, life in the trenches stays tough.

by rayjeff

And that is the main or one of the top five problems where I'm at now. The IT leadership is lacking because they, or shall I say he, makes misdirected judgements or not even judgements at all. One would be the college's website. If you were to see it, even if you had a just the most basic understanding of web developmemt or webpages in general, you would pick up that the website is out-of-date. Not just by the dang copyright date showing it's out-of-date, but the design methods. The website has not been updated since its inception in 2002; before then, the college did not have a website. Control of the website isn't centralized on-site, but at the hosting site, which isn't the college, obviously. Sure, the excuse of not having the manpower could be made to justify not having an updated website. But then I would counter and say, "hey, why not use the resources you have in abundance...the students?". The college has a service learning program, why not let the CIS students work on the website. Not only is it cost-effective, it gives the students real-world experience. But do you think that the IT leadership sees that...obviously not.

When it comes to IT, the leadership is very reactive, but that's a general trait for everything at the college. We troops in the trenches...our voices go on deaf eyes and ears.

by fractalzoom

What a shame.

Just to ask the question for sake of asking it (I think I know what the answer is going to be), have these issues been specifically raised with IT leadership? Have you talked to them and gotten an answer? Do they have a particular reason, or is it a case of benign (or even malignant) neglect?

by caughtlbw

As you say, "if they are trained to begin with..."

I've been in my current job 2 years. I cannot count the number of times I've tried to get the IT department to run superuser courses. I think in that time we've managed to do ONE course. The excuse is always that we dont have the resources.

A typical remote office that I deal with might have 6 Users. If just one of those Users has been to a 2 day "superuser" training course, my job becomes so much easier!

This training covers very basic stuff. How to plug in and setup a printer. How to "ping" the router to see if it's alive. How to change passwords. How to access email via OWA when you aren't in a networked office. etc etc And, of course, in the process you introduce a range of terminology and techie-speak.

Subsequently, when you have to resolve a problem in that office, you either have the benefit of knowing that the local superuser has already covered the basics, or you can liaise directly with the superuser and know that they understand the language.

However, the greatest benefit of the training is that the IT department is no longer a distant, inhuman, unhelpful entity. The superuser's been to Head Office, they've met the people on the helpdesk, seen the server room, been out to the pub with you for a chat and a laugh.

The IT department goes from being an anonymous voice on the phone, to being real people.

The efficiency gains that result are enourmous. Which is why I get frustrated that as a department we dont do more training coz we "lack the resources".

Now, of course, your real question was "So how do you get people...(to) learn how to use the technology?". Which, in this context, is "how do you get them to attend superuser training"?

I dont have an answer to that, but I have an observation.

One of our larger Regional Offices moved offices two years ago. Ever since that move, we've had a stream of problems with the new site. The Users at that office, rightly or wrongly, blame IT for those problems, and for our apparent inability to resolve those problems. Their opinion is that they've received lousy support from us.

I was on site recently, and again broached the issue of superuser training (explaining that it would help them if someone in the office was trained up). Everybody in the office refused absolutely, and actually quite vehemently.

Why?

Because by this point IT was the enemy, and they weren't going to consort with the enemy.

And also because no-one wanted to risk being blamed for problems.

IT has lost the confidence, and hence the cooperation, of the Users at this site. It'll take time, and hard work, for us to recover from this situation.

In contrast, I frequently visit offices (the small ones, with only a few Users) that quite literally have NEVER had a visit from anybody in IT. They might have lots of problems. Usually just little, niggly problems, but ones that are still a hassle. But because I turn up on site, actually fix the problems, and then actually TALK to them, discuss things, explain things, and take them seriously, it's just amazing how quickly they switch from badmouthing IT, to being really cooperative.

And THEN I raise the issue of superuser training. And usually the response is very positive. They want to have a productive and mutually beneficial relationship with IT. They want to help us to help them.

So the observation is that before you can get Users to learn how to use the technology, you first have to have a respectiful, cooperative, and professional relationship with them.

by caughtlbw

....that establishing such a relationship is perhaps *most* difficult in an academic environment.

The most intractable egos I've ever had to deal with have been in Universities. :-(

by hal 9000

Just try telling some Uni Professor or Head of a Department that they are doing something the wrong way and see how far you actually get. ;)

Instead of accepting your instruction they will go complaining to their superiors that you are not helping them to do what they need to. It's as if they want you to rewrite the program to work their way rather than try to work with the technology. :)

Col ]:)

by rayjeff

"IT has lost the confidence, and hence the cooperation, of the Users at this site. It'll take time, and hard work, for us to recover from this situation."

Yes. At the college, the IT department, or shall I say the director of the department has lost the confidence of the faculty and staff. They actaully hate going to the department for anything because of "run-around" fear. And if not that, turn-around time for resolutions takes weeks at a time.

"In contrast, I frequently visit offices (the small ones, with only a few Users) that quite literally have NEVER had a visit from anybody in IT. They might have lots of problems. Usually just little, niggly problems, but ones that are still a hassle. But because I turn up on site, actually fix the problems, and then actually TALK to them, discuss things, explain things, and take them seriously, it's just amazing how quickly they switch from badmouthing IT, to being really cooperative."

"And THEN I raise the issue of superuser training. And usually the response is very positive. They want to have a productive and mutually beneficial relationship with IT. They want to help us to help them.

So the observation is that before you can get Users to learn how to use the technology, you first have to have a respectiful, cooperative, and professional relationship with them."

These two paragraphs go together for me because I have a great relationship with the faculty and staff. They love me because I take the time to help them with their issues and just basically take the time to share my knowledge. I have hear the badmouthing of the IT department all the time. And everyone says the same things. If there was communication and leadership from the IT department to everyone else, especailly the tech support in each division, things could be better. Basically, we are not utilized as we should. If we were allowed to be trained or allowed to work with the IT department, turn around time could be quicker. The faculty and staff have the respect of the tech support people and even one person in the IT department (the network admin that does ALL of the IT work on campus). Why run one person all around campus doing everything when you have 5 other persons in strategic areas on the campus that are in every place you would want to fit an IT person?

The faculty and staff listen to everything we (the tech support) have to say because there's no one else that will talk to them without being "I'm the GOD of technology here and I don't have to tell you anything; you wait on me" speech/look.

by avid

the only thing i would add is "no matter what goes wrong at the office, from pc problems to toilets not flushing, if the IT guy was there in the last month it must be his fault.

by avid

and i just love proving the dates and times a site was visited. and the ever present " it must have been a pop-up that download the 20 gigs of movie clips" and they are on dial-up

by comb5406

My pet peeve is the ridicules process I have to go through in order to read a two-page article. I receive a link to the article via an e-mail from Tech Republic. I click the link to the article. I then must log into Tech Republic. Browser security prevents the article from downloading automatically so I have to click another link. Finally, the article downloads but in a zip format. I then have to unzip to finally retrieve a two-page PDF document. One would think a tech company would have a less cumbersome process. I would imagine most readers do not even bother.

by jbaker

My favorite is the user that makes changes to settings (VPN in most cases at this site), then calls me when it does not work once they get back home (we have some users who use laptops remotely, VPN for email and files, and travel quite a lot). They expect me to know (without them telling me) what they changed, and how to fix it. And, of course, they can never remember what it was that they changed.

by sbmknight

When I get calls from users asking how to do basic things that are documented in our user guide, I tell them I will email them a link to the instructions. When they protest and ask if I can just walk them through it or do it for them (my "favorite"), I tell them no, that the documentation will be more helpful to them because they can keep the link for future reference. This works particularly well with simple things that the user can't blow off because you won't do it for them -- such as network printer installations.

by sbmknight

LOL The part about users with mailboxes over the limit hit home with me. We routinely get calls from users insisting we increase the size of their mailbox storage, which we refuse to do for ANYONE, even those elected to office.

But the best was when a particularly "sensitive" user called, upset because she couldn't email an overdue attachment because she had filled up her mailbox. I tried very patiently to show her how to make room in her mailbox, when suddenly, I heard sobs on the other end and "I'll have to call you back." She never did...

by Former member

In the time I've been online and people asking me for help on things like my site, I've come across some emails that go something like this...

"i tried to open the image and it says it cant do it. HELP ME NOW PLEASE!! I WANT THIS IMAGE!!!"

Come to find out they tried to open the .zip file in the image program so you point this out and they go "what is a zip file?"

Or, you get something like this...

"I don't get how to do this tutorial. I'm SOOOO stupid! LOL! Can you please help me? I really like this tutorial! HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!" (endless stream of exclaimation points....)

I'm glad I never had to do in-person or voice tech support. Though I've had to call for tech support and I felt rather insulted when I get treated like I'm one of those I mentioned above. :(

That's why I'm not too interested in tech support stuff anymore. I want to enjoy getting some of my work done, not fighting with those who really have no idea what a power button is. (Seriously, I have no idea why but I've come across so many of these types).

That's my pet peeve about providing support. :) However, to be fair, I have met others who were knowledgable and even helped me learn a thing or two in the process, and didn't mind giving details of an error or problem. In fact, I've come across some that were so detailed it was a breeze to find the problem right away. If only every situation was like that. :)

by Former member

My company has a strict policy: if you have a computer problem, you call our help desk. Don't approach an IT staff member in the cafeteria, men's room or parking lot. Don't pay us an uninvited visit at our desks while we are furiously hammering away on an existing problem, as that interrupts our concentration. Don't leave ua a worried voice mail as we may have actually gone away on vacation and your message will sit unlistened to for days whereas calling the help desk could have resulted in a much more rapid resolution. We are there to help the user community, but in an orderly fashion: first come, first served, and we have to be able to document, log and prioritize our help desk calls so we can be efficient.

To be fair, most of our user community complies with this. It took a lot of pressure, reminders, and yelling for our CIO to finally get this policy in place, but for the most part its worked. With the exception of the "chosen few" who routinely ignore, disregard or even flagrantly brush aside the stone "call the help desk" rule. No matter how many times they're told to call the help desk, they still persist in trying to approach us directly. Even when informed "You're supposed to call the help desk" and politely refused service until they do, the next time you see them in the hall, get ready for "My Excel formulas aren't working and I need this fixed now!" as you are on your way to assist another user who did the right thing and called the help desk first.

We had one guy in particular that my boss had to call HR on as he simply refused to abide by the help desk policy and hounded us to make him our #1 priority. Sad to say, there are some people in this world who truly believe the way to get results is to be a big pain in the butt so people will satisfy their requests just to get them off their backs. No matter how many times this user was told to call our help desk, he would just ignore that and show up to demand help for a problem. If you told him you had ten other support calls to deal with first, it didn't matter. If you informed him the e-mail system was down and that had to be fixed first, he would insist on knowing when you could get over to fix his issue and refuse to take "I have no idea how long it will take to get this server up again" for an answer - "Will it be a half hour? An hour?"
If you reminded him that the help desk is first come, first served, it didn't matter. If you tried to appeal to his sense of fairness and explain why you had to look at Sally's monitor problem, which had gone on since last Tuesday, he didn't care. He had to be bluntly told nothing would be done until he called the help desk, and sent on his way. And then when forced to do so he would badger us constantly "When is this going to be fixed? When is this going to be fixed?" in the halls, on the telephone, and anywhere else you encountered him.

HR had to get involved (unsurprisingly, they had to get involved with some other issues he was causing as well that resulted in many of his coworkers being frustrated by his behavior) and tell him to knock it off. I think most coworkers can resolve differences without having to get the company officials involved, but in this case it just couldn't be achieved. Now the user reports his problems to the help desk, but in a nasty and sarcastic manner that indicates just how bothersome he feels it is to have to wait his turn and abide by company policy. What I find especially ridiculous is his attitude that we are just a bunch of jerks picking on him. That we're unfair, not letting him just show up, whenever, so we can drop whatever we might be doing to jump right on that Powerpoint problem. That we are bullies who get our kicks out of entangling users in a bureaucratic gulag. I've learned after years of dealing with people like that there is no pleasing them. All you can do is ignore their attitude, not worry about what they think, and refuse to let their problem become your problem.

by Former member

By far one of the biggest frustrations in the IT field is the fact that no matter how well-configured your server is, no matter how properly documented the instructions are, no matter how many things you've thought of in advance to stave off one system problem or another, there is always the possibility some exec will not understand how to use their system and blame you for something not working.

We have a manager who checks her e-mail while on the road. She recently contacted another manager from her personal e-mail account to to complain "the system wouldn't let me in so that's why I'm emailing you from my personal account." Turned out she just wasn't typing in her password right. But the perception was that the system wasn't working. And if the system isn't working, in the corporate world it is NEVER a far leap to the next question: "Whose fault is it?" If you get a few of these ID-10-T issues strung together, at the next manager's meeting you might very well wind up the subject of a grumbling discussion regarding "Why IT has been screwing up lately." Sounds paranoid, I know, but it has happened.

I don't mind meeting with anyone face to face and explaining to them "You didn't type in your password correctly. Let me show you." Problem solved. What I can't stand is the behind-the-back discussions founded on misunderstanding and finger-pointing, where you don't have a chance to defend yourself or explain the facts because you're not present. This is why I always tell users "If this doesn't work let me know so I can straighten it out for you." It might be irritating to get a phone call next week from the user asking why such-and-such thing isn't working, but that is ten times better than hearing from another maanger that the first user in question was bellowing in some meeting that the system or process didn't work.

by Former member

You're right, sharing knowledge is a good thing and I don't mind providing some free brief advice like "Is a flat screen or a regular CRT better for me to buy?" or "should I go with cable modem or DSL." It's the long-winded tales of woe involving some AOL upgrade (I joke with my IT friends that I'd love to get a t-shirt that reads "I don't give a damn about your AOL problem" and wear it under a button down shirt so if I'm approached I can be like Superman and pull open the shirt to reveal the above message), some problem with Photoshop that is producing deteriorated image quality, some scenario involving copying all their old Mickey Mouse club VHS tapes to DVD using such-and-such program which is doing such-and-such thing isntead of the desired result, etc. That's where I feel the intrusion into my personal time is unwarranted and definitely exploitative.

by rongroff

Having worked over 40 years in the computer industry repairing all size types and makes of computers my pet peeve boils down to this: 90% of the problems reported are "Operator caused"! Agreeing with ALL of the Peeves in this article I ask you consider this as the Peeve of ALL Peeves.

by rayjeff

There have been meetings. Formal and informal talks with the director. The answers/responses are all the same. The run-around or promises/assurances made making it a long waiting game. Point is, nothing ever gets done.

It's definately malignant neglect. No doubt about it.

by pivert

you mean that it's like a big software company releasing version X and they still manage to miss the ball? :-) Be thankful they don't build airplanes: "we have a little bug here and we're downloading the latest hotfix. let's hope we can boot before we hit the..."

by myron_s

Having to download a PDF file in a ZIP file then taking the extra step in having to unzip the PDF file from the ZIP file!!!

by sbillings

When I arrive at a user's workstation and others are always approaching me with thing that seem to "pop into" their heads. They always say "while you're here, can you take a look at this for me?"

On a side note, I hate "can you?" and "could you?"--- I much prefer "Will you? and "Would you?"
You may not think it makes a difference when you ask people with can and could instead of will or would but it does!!!

by fractalzoom

I've been watching this thread for the past day or so, and have reached a conclusion that I know will bring flames down upon me...but have you considered that maybe you're whining just a little bit? Buck up. This stuff is a fact of life in IT work. And the more you take the attitude that users are protozoal pond scum, the more you perpetuate the cycle.

Quit whining, and be grateful you're employed...thre are lots of techs in Bangalore who would love to do your job for you.

Peace,
-MF

by hcetrepus

Yeah I remember when i tried switching to decaff......

Reading these are stress releif for me, knowing somewhere else someone puts up with the same "I cant tie my shoes, help me!" that I do, just makes me feel better.

Go ahead... have a caffeinated drink and relax bro.

by caughtlbw

I remember a day about 18 months ago. Three of us in the office to man the phones. Two of them contractors who'd only been with us a month or so.

I got to the office at 7am. First phone call at 7:30. The Area Ops Manager in Oxford couldn't log in. Claimed the VPN connection was down. Turned out he couldn't type his own password.

And so it began.

A couple of hours later I had a User on the phone, another on hold, I was using my own pc and two test-rig pc's on adjacent desks to troubleshoot three previously reported faults (the Users waiting for me to call them back), and I was running two Dameware sessions to remote offices working directly on those User's desktops. All at the same time.

The other 2 guys were similarly loaded.

Every other phone in the office was ringing with people trying to get through to the Helpdesk.

And, of course, we had a continuous stream of local Users walking into the IT office with problems.

This didn't quiet down until 6pm.

In the middle of the afternoon I had a User phone from the Bristol office. A laptop User. He couldn't synchronise his email inbox, and demanded I fix it immediately.

Now, this was a laptop that I'd setup personally. I'd taken *great* care in setting it up, and had thouroughly tested it. I'd specifically tested the functions that he now claimed were not working.

I knew from his description of the problem that settings on the laptop must have been changed, and that the only person who could have changed them was the User. Of course, he denied this absolutely, and more or less blunty accused me of not setting it up properly to begin with (even though it had been running ok for weeks).

Now, I *DID* lose it.

I DID call this User a moron.

I DID call this User a liar.

I DID tell this User I would NOT fix his laptop.

I DID slam the phone down on him.

And, of course, this User DID just happen to be the Staff Union Representative for the entire company.

That was NOT a good day on the Helpdesk.

I HAVE to look back on a day like this, and laugh!

We remember the few bad days. We forget the many good days.

If we dont sometimes laugh and blow off steam, we'd slowly go crazy.

by ace1angel

Now I've been lucky enough to have been with my users for 6 yrs, in that time I have them fairly well trained.

They bring in their laptops for 'a tune up.' when they're in the office, they read and save the Tips and Tricks I send out.

That doesn't mean that I don't have some of the same issues. People who refuse to learn the basics of windows (any version) and keep getting more and more lost, but refuse training. People who try and break computers, and complain when they succeed. People who think they know better and more and then wonder why their system doesn't work. That's IT life.

It's all in how you deal with it.

Personally, I realize I'm paid to be nice and patient, and I do that very well. Then I enjoy little vents like this, where no one gets hurt and most people enjoy sharing the laughs and frustrations.

Respectfully submitted

by hcetrepus

Glad to see this one! Every user assumes that we know what there passwords are, and look blanky at us when they somehow forget, and expect us to know it. Some have even gotten angry for us not knowing!

by mdpetrel

Hi;

The first thing we learned about computer technology is about the hardware and microcode; so we all know that it is really a miracle that all components work together given the complex timings involved at the millisecond level.

There truly are mullions of instances in which a given "fix" will not work, and suddenly does work.

I would NEVER even begin to think that the user had lied about trying a given solution... I know too much about what actually goes on at the device microcode level...

Cheers... mdp

by hcetrepus

My favorote commercial on TV is the one where the bonehead guy is mindlessly shoving hsi pencil into the electric pencil sharpener, wanting it sharpened. Someone comes along, looks at him, and then bends over and plugs it in. I yelled to my wife, "Thans what I do for a LIVING!!"

by mdpetrel

... because this one actually boils down to policy issues... think about it:

Everyone of us has at least a few dozen passwords and or PIN's to memorize. The solution most average people employ is to:

1) either write them all down, in which case security is compromised if you misplace your list, or worse, if you tape it onto your monitor or simply slide it under your keyboard; or

2) pick something REALLY easy for someone to crack, and then use it for all cases.

So, what do we do to ENSURE their security? We generate "gobbledygook" passwords for them. Ok, so *I* can remember the value of PI to 25 digits, but it's flagrantly arrogant of me to expect everyone else to be able to do so...

Sorry, *I* treat every lost password request with sympathy for the user, not disdain.

Cheers... mdp

by philwills

I recently conviced my supervisor to invest in Dameware NT Utilities. We have one site which is almost 4 hours away, which in the past, if there was an urgent problem, someone wasn't going to be home until 8 or 9 that night.

I first convinced the rest of the technicians to use the trial version and eventually we convinced them to buy some licenses.

Now the supervisor uses it almost as much as some of the techs.

by graytalon

for cash, you can use Netmeeting. I was helping my sister-in-law last night, in fact, with Netmeeting. Her system is a Win98 and mine is XP.

But, the great thing about Dameware is you can "force" the client onto any system where you have admin rights. It's really helpful on those calls where the user has locked their password 10 times in 20 mins. You can tie into find they have the caps lock on and look like the hero while you shake your head in disgust.

by ace1angel

I would add the user who is upset because his computer doesn't work at the speed of thought, who insists he knows more because he came for QA at another company. He thinks he's the Beta tester, on a finished app and will do his best to break it and when it does finally give up the ghost yells, "SEE I told you it didn't work!" One who is never satisfied, where you're tempted to ask them what have they done now to mess up the machine, that seems to work for EVERYONE else in the company.

by cdanos

On my list, the #1 has to be:
At a party, social gathering, or even at the deli counter if someone finds out I'm a PC tech they immediately start describing in detail their latest problem with their pc. I usually try to be helpful but really; if I asked someone what they did for a living in the course of a conversation and they said " I'm an accountant." I wouldn't ask for tax tips. People just assume that if you are a tech you must yearn for constant challenges and problems to solve. Never mind that you're just trying to have a life outside of work.

by dmambo

I get double whammied on this. My wife is an Adult Nurse Practitioner, so we get both the tech questions and the health questions. I love it when someone asks her about their home networking problem or me about which antibiotic is best for their strep throat. They must figure that we undergo knowledge osmosis while we sleep.

by ace1angel

Personally, I find out what they do, and blatantly ask them for free advice, Dr? Cool I got this pain.... Accountant? Why not ask about a few Tax laws? Though I liked another person's response, which was to act horrified and recommend they contact a company that does home PC repair.

by hal 9000

I do work for quite a number of small business which meant a lot of traveling and short of almost criminal activity being impossible to get into locked offices so I just spend a lot of time sitting around waiting for the person with the problem to return. When they have to office open I can always get into the machine to fix it so there really isn't a problem there. ;)

But in the case of the scanner one I had built the computer and I was copping the blame for the scanner which had been added which was causing the problem. Of course if they had of told me that they wanted a scanner on the computer I would have supplied one that was shielded and not just a plastic shell that offered no protection, but once I did find the problem it it was a simple solution which worked out great for all parties concerned but if he had not have stayed in the office that one time I would never have found the problem and in all likely hood would still be recovering the data and then reloading the computer overnight so he had it ready the next day. Of course reactivating Windows 3 times in as many months on the same machine had MS wanting to know what was going wrong which unfortunately until I had a solution I couldn't answer. :(

I actually had the same thing happen with one of my test units where I would test different parts over a period of time like Vid Cards different HDD and so forth but every time I changed more than 3 items even if they where replaced with the originals I had to reactivate Windows again which became a real pain so eventually as the need arose I replaced all the OEM copies of Windows XP Pro with Volume License copies and no more problems. :D But it really got nasty one day when I added 12 X 146 GIG SCSI HDD to my main workstation and when I rang MS to get a new activation number I was accused of Pirating a copy or in this case 17 copies of their software as I needed to reactivate 17 different products. ;)

I just replied that the entire MS Software products on the workstation which most of which I never use except for testing purposes for my customers came to less than the cost of one HDD and that in that case I would hardly be the slightest bit concerned about the minimal costs involved in buying the software compared to the costs involved in the buying the additional hardware. :)

But what made the whole thing even funnier was all the software is supplied to me by MS in the pack that I pay for yearly to be an OEM builder so I can install all of this software on an unlimited number of machines for display purposes and use as many copies as I want for business purposes provided they do not leave this place permanently. As I do not run a shop as such but specialize in small business network systems I tend to do a lot of work on site and just do not need a central display location where the business people can come in and look as we go out and see what will be required and then quote accordingly for either something as simple as a single workstation to a complete network. :)

The last installation that I did nearly drove me crazy as they kept changing their minds which was a real pain when it came to running the network leads but somewhat more profitable when it came to the hardware side of things as they started out only wanting 3 workstations all with their own Broadband connection which I talked them out of as it was just a waste and into a small network things then took off and eventually ended up as a 15 station network along with a server installation but because they kept changing their minds as the job progressed it cost them far more than it really should of which I find just as frustrating because I then think that I'm not offering the best value for money that I could be. ;)

Col ]:)

by caughtlbw

Yep, spent 12 years running my own consulting and design business, so I hear what you're saying!

The difficulty in managing requirements creep would definitely be a Pet Peeve for me.

by hal 9000

Place grows and prospers but to get this in the time taken to organize a quote for the requested hardware and then install it what should have been a simple little job turned into a nightmare with me having the constant feeling that on every occasion that they thought of me they where just thinking up way to move to goal posts to see how far they could push me before I broke. :)

Luckily they ran out of money first. :D

Col ]:)

by thumper1

1) Had a secretary who worked for the managing partner in the firm. She was not above letting everyone know that she worked for the boss. She absolutely would not tolerate being made to wait for anything. She called me one day while I was in the middle of a project. Based on the time between her first and second call, and then the call from her boss, (About 1 minute 30 seconds) she expected me to drop what I was doing and RUN down to her office. Not wanting to give anyone a bad time, I explained to her and her boss that sometimes I am in the middle of things that I simply can not drop and would make every effort to get to her ASAP. Made no difference. I started timing the calls. If I was not in her office within 45 seconds of her first call, the next call I got was from the attorney she worked for.

2)I had a secretary whose system was giving her problems. She called me and I went right over to her desk, but when I got there, she was involved in personal phone conversation. (She spent a lot of time on the phone) I waited a good ten minutes for her to finish, didn't say anything. Happened again a few days later, this time I walked away. Found a project in a room that had no phone service. When she finally tracked me down, I said "I thought that since you didn't make any effort to get off the phone, your problem was solved." The third time it happened, I started to walk away. She said "I gotta go" to her phone call and hung up.

3) Secretaries who call you over to diagnose a problem, tell you "I got an error, Your system has Yada, Yada, Yada," Before the event viewer, I used to tell them "I really need to know what the Yada, Yada, Yada is."

4) Had one secretary who was having problems. She was looking over my shoulder while I was attempting to fix it. Duplicating her steps, she apparently I was intentionally trying to screw up her computer. She says "What are you doing!" and HITS me on the shoulder. I stopped what I was doing and said "I can not fix it until I know what it is doing". I debated going to management, didn't. Regretted it later when this secretary became an even bigger PIA.

5) Secretaries who regularly violate company policy by installing software from outside the office. Games, screen savers, wallpaper, etc. Spent too much time fixing hijacked systems.

by mcdevittj

You are walking a user through a step by step process over the the phone, suddenly there is verbal silence at the other end of the line and you hear the pounding of keystrokes. You ask the user "What are you doing right now" but there is no response. Then you hear the inevitable chord.wav and the words "UH OH, what to I do now?" which usually results in initiating a ticket and dispatching a tech to the user's location. A simplified example of this is your instruction "Type in your username BUT DON'T PRESS ENTER when you're done" (in order to instruct pressing the TAB key to advance to the PW field). You hear rapid keyboard strokes and then "UH OH", or perhaps even one of Tricky Dick Nixon's "expletive deleted" words.

by itgirl.2010

I really enjoyed reading your peeves regarding issues of being an IT support person. Many many times over I have felt as you describe in your article. As you mentioned it is encouraging to know others feel as I do. Honestly, I couldn't have put it better myself. Thanks for the support.

LK

by donna.stefanov

I hate it when I start questioning the client calling in with a power problem (this is a phone call). You will go through everything you can think of to troubleshoot the problem only to find out that power went out in the whole building.

by tq66

It's too easy to list gripes. A billion highly sought after TechRepublic participation reports* to the first person to list constructive ways to prevent gripe enducing behaviour.

* at TechRepublic's discretion

by caughtlbw

Whilst at work:

1. Smile
2. Listen
3. Be polite
4. Be respectful
5. Be patient

Whilst not at work:

1. Have a life

Finally, make sure your boss will back you up for those inevitable days when you fall off the straight and narrow.

by hal 9000

With your end users in a constant attempt to get them to learn what not to do or at the very least learn how to minimize any disruptions that they may inadvertently encounter. :)

Unfortunately not everyone is interested in learning as they do not consider this to be their primary job and they already have you handy to fix up what goes wrong! :p

Col ]:)

by weirdfish

...DELTREE!

I still find that I use DOS on occasion at the office. It's MUUUUUCH faster than "click here, click here, click OK, click there, expand this, CTRL+A, SHIFT+DEL......"

by Member 28898618

Bottom line? Your clients pay your salary. If you have to stand at their desk for an hour, or troubleshoot without their help, or order the part 10 times over, you do it because that is your JOB!

After that, in the interest of efficiency, offer suggestions, improve communications, take a break, dream up ways to help people help themselves - even be creative if possible. This is your only recourse. To peeve is to quit. If you cant take the heat, do something else for a living. To serve others is to do what they both need and want, no matter what your opinion is of their intelligence, lack of understanding, or your own feelings of knowledge superiority. Users often get the impression IT techs are arrogant, can you guess why? Your list includes many hints.

by fractalzoom

Thank you for making the same point I've been trying to make in this thread...the bottom line here is that we're professionals in this field, and these are the parameters of the IT landscape, the facts of life in this career field.

I understand the value of venting, but what I'm reading here doesn't sound like healthy venting. Most of what I see here seems to indicate a real contempt for the people being supported -- a dangerous attitude, and one which I do not tolerate in my own IT department.

If doing this kind of work really bothers you that much, go sell used cars or something. Sheesh!

by hal 9000

Then never get near a bunch of Doctors at any conference as they put down their clients who pay them even worse. :p

Here I have yet to see any IT Pros call their end users stupid, idiots or anything else for that matter we are just having a general gripe which is healthy rather than locking it all up inside and then causing health issues. We all already work hard enough but no matter how much time we spend in the office we are still constantly bombarded with questions at the most inopportune times. Is it any wonder that just working IT is the best contractive known to man? :D

Col ]:)

by hal 9000

No matter how much I Dumb It Down most end users still do not understand what I'm saying but they are the ones who ask the hard questions and then want a nontechnical answer that is within their understanding. Most times this just isn't possible so like most IT people I just live with it. :)

Personally I'm sick and tired of seeing my clients eyes glaze over as I talk to them in a direct response to a question that they have asked, so what it matter if they do not understand the difference between a CPU, GPU, HDD, LAN or whatever so long as they can get their e-mail and do their work no body cares. I do not know many IT people who feel "Superior" to their End Users it is just something that the end users dream up because they do not understand us and in all likelihood we do not understand they specialized parts of their jobs either to each his own but that by no means requires us to like the constant senseless stream of calls from the same person who constantly does the same thing and can not understand why it will not work after all it is so easy in the movies so why isn't it the same in real life? :p

Col ]:)

by itwildcat

Try being an IT student, working in the feild (at your own college mind you) as a help desk tech.. and your cisco instructors call you because they can't set basic preferences for their e-mail!! OMG!
At least common users have an excuse!