Slashdot Mirror
Making the Most of IT support?
wetfeetl33t asks: "On Slashdot, we've seen quite a few stories about employees who are unhappy with their company's IT department, or are seeking advice on how they can whip their company's IT department into shape. So, enough of the complaints about the supposed stupidity of technicians, the incompetence of sysadmins, or the excessive network down time. A better question is: how can users work peacefully and effectively with their IT department and make the interaction between the IT people and other employees as productive as possible?"
Isn't it obvious?
Treat the people with some respect. Not only is it the right thing to do, but they'll probably fall over from you even doing it. Most IT people I know get treated like crap, and they don't deserve that.
Nobody does.
I find that bombarding IT with little requests like help with my desktop background, system volume, printers, plugging peripherals like my iPod into the desktop, and a bunch of other things that I could presumably do myself really helps keep those IT monkeys busy running up and down the stairs from their dungeon to my ivory tower.
The networks seem to be okay, and I have all my files, so it's not like they have anything better to do. Maybe they'd rather be surfing Slashdot. I don't know. But I'd rather they lost some weight and became more pleasing to look at. All the running around is helping their looks.
Maybe we should also install a shower...
When Joe Cubicle calls the building manager about his heat or AC problems, he has (or soon learns) a reasonable expectation of what he can ask for, and what will get done for him.
/Napster /Skype / weatherbug/ etc.. and the company VPN connection won't work - they expect instant gratification.
When Fred Copyguy calls the Xero/Canon tech because he jammed the double-sided collated stapler function again, his company is paying for either a hefty contract or a site visit. If Fred does this too often, he is dealt with.
When Phil McCracken gets sued for sexual harassment, he makes an appointment to see counsel, and waits while the case is dragged through depositions and hearings.
Unfortunately, when these same nitwits call IT because they installed the latest Free Poker game
Corporate-think needs to perceive the computing infrasructure,including the personnel, as an expensive, specialized tool. If you want me to replace this [machine, router, 1st-level support tech] like a $10 pencil sharpener, then always keep a dozen spares around and ready, or give me an expense account so I can just run down to CompUSA and buy 6 or 8 on any given day. OTOH, if you want me to save that $80,000+ in dusty equipment and redundant training then treat the entire system with the respect and care just like you do the building / campus / Corporate Counsel office.
Plan ahead. Respect the time of your coworkers. When you suddenly come to your sysadmins with set of tasks which "needs to get done today", remember that your sysadmins need to push out other projects to work on your project.
The stereotype of a "Grumpy Sysadmin" probably comes from the fact that one minute we're deeply involved with a technical project performing mental gymnastics and the next minute someone is standing at our desk, demanding attention. Now. It is very difficult to return back to that project or remember where we were.
System Administraton is different then other jobs in the business. We typically deal with a very high level of interruption & multitasking-- and probably more then anyone else in the company. It's not unusual for me to have 12 hour workdays where absolutely NONE of the tasks were on my todo list when I walked in that morning-- a day and a half FULL of interruptions.
"Can of worms? The can is open... the worms are everywhere."
As a professional systems administrator for nearly ten years, I have certainly been in my fair share of crappy IT environments. I think the issues can usually be fixed by adhering to two principles:
1. You get what you pay for
This is a far-reaching statement. The first aspect is salary. Companies (well, universities) are always trying to get by with meager salaries that are NOT competitive at all (let alone poor to non-existent raises, benefits, etc.). In my opinion, it is better to pay one really competitive salary than two or three shitty ones. That one person is going to be so much more valuable than three scrubs; more experience, better attitude, maybe actually be happy with their job and stay for a while. Sure, you can get good people for cheap on occasion, but they are going to be miserable because they know how badly you're screwing them. That demotivates otherwise good employees, leading to decline in work performance as well as leaving for greener pastures.
In a field like systems administration, there is a really big emphasis on personal initiative. You have to proactively go looking for problems before they become problems, come up with bizarre-ass ways to fix things immediately or within the confines of your budget (usually small or zero), man-power, etc. If you're seriously unhappy with your job, it drains your initiative. I have personally experienced this. I want to do a good job, and I take pride in my work, but since I know that I'm being treated like shit (in ways other than pay too), I have a harder time caring as much as I would like to about my work. Thats just the way people operate; if you want the best out of your employees, you have to recognize that.
Stemming from this: you need to fire worthless people. The inability or unwillingness to fire worthless employees is one of the biggest problems for employers that I see. If a sysadmin is always causing more work just by his attitude and ineptitude, then they need to get the boot. If you don't do that, all of his co-workers who aren't fuckups are going to see that you don't care about the quality of their work. Another demotivator.
Also pertaining to this: you are paying these people to administer your computers. NOT to move furniture. NOT to hang pictures on the walls. NOT to do anything with anything that doesn't plug into the wall and beep when it turns on. Its one thing to do a favor for someone, its another to turn into a moving man when you ought to be doing a highly skilled job for your salary.
Aside from salaries, you need to pay for equipment. IT costs money, computers cost money, software costs money. Just because computers are $800 instead of $5000 now doesn't mean that they're free. IT departments need budgets, they need control over those budgets, and they need to be set at reasonable levels. There is a lot of waste here, from sending people to training seminars and paying for support contracts that you don't really need (or use). That isn't what we need. We need money for hardware. If you have to cobble things together, or use a production server to test out things, you're going to run into trouble sooner or later. A lot of the time out-dated, overly heterogenous or inadequate hardware is one of the biggest contributors to an overburdened IT staff. Getting rid of all those 400MHz PCs running Windows ME (when the rest of the place is using XP) is a huge help, more than worth that $800 you need to shell out.
Number two is: Let the experts handle it.
I have worked in a few places where computer decisions were made by someone with no technical knowledge, often based on the latest buzzwords or something someone told them or who knows what. Professors who need 24" LCDs because it will make their computers faster (false), people who think they need a LaserJet 1300 because its a higher number than 1200 (the difference is so minimal as to be a complete waste of time and money). On a larger scale, the complete decision making process of the computer infrastructure may be entirely out of th
There's just no substitute, on both "sides".
In my experiences, users who don't know crap about IT consistently generate the kinds of user problems noted here, and IT people who don't bother to learn anything about the concerns of their users (and who tend to be like Nick Barnes) create the rest of the problems.
It takes time and effort to understand the other guy, and lots of people are unwilling to do it. Senior management has to set the example, which they often don't (though they like to give it lip service).
It is usually much easier to debug a problem if you at least have direction in which you can search.
I usually work for smaller shops with a Windows SBS Server and 10-20 Computers.
Users usually feel intimitated if you ask them what they did, before it stopped working. You need to tell them that you're not blaming them in any way, and just want to find out what might have caused the problem, and that nobody will ever hear what they tell you. You need to sound calm and professional when you talk to a customer.
But for me, this usually works.
"Well, i want to a pornographic website, and there was this dialogue i didn't understand"
"I tried to install this wireless network at my home, and.."
Etc. pp. This usually works very well. Never get mad at someone who made a mistake, suppress your emotions, always stay calm, and tell them that you're there to help them (and get 200 bucks per hour).
how can users work peacefully and effectively with their IT department?
Simple.
STFU.
RTFM.
Dialectician. Archology.