I find good/funny/interesting things on Slashdot, and one of my more favorite features of the site is where a user can post a question, and then the trolls/users of the site will post their best attempt at funny/witty comments and banter. Generally, these are just junk, but I liked this one question and it was something I already had on my mind…
“I work for a small software company (around 60 people) as the sole IT guy. It’s my first time in a position like this and after about 1.5 years I’m starting to get a bit burned out. I try to be friendly, helpful, and responsive and I get no respect whatsoever. Users tend to be flat-out rude when they have a problem, violate our pretty liberal policies constantly, and expect complex projects to be finished immediately upon requesting them. My knee-jerk reaction is to be a bastard, although I’ve avoided it up to this point. It’s getting harder. For those of you who have been doing this a lot longer, how do you get a reasonable level of respect from your users while not being a jerk?”
http://it.slashdot.org/article.pl?sid=09/06/09/2028202
I don’t like posting on that site since I’m sure my realistic opinion will probably be ignored or become flamebait, so with that, I’ll post my response here on my site instead.
Having worked in IT for 9+ years now, going from first level tech to sys admin to engineer, the one thing every good IT guy/department must have is a solid ticketing system. I know it seems stupid, but one application can help you organize projects/requests/problems, show status to management and users, track complaints, track previous troubleshooting, be used for knowledgebase functions. One web based application can provide the backbone to a good IT group’s ability to deliver services that users can find helpful and useful.
To accomplish these tasks though, I believe a good ticketing system should be backed up by solid policies and procedures that ensure all problems and changes go through it, as well as competent managers who can make the most of the system and people using it. The worst helpdesk is the one that no one uses properly. They stop you in the halls, you fix things as you walk back to your desk with your lunch. You need to encourage people to stick to the system. Yes, I know it’s easier for you to bug me about your petty problem and I can probably fix it real quick, but really, there’s a long list of problems (usually) and yours will get the assitance it needs based on the priority of the other problems and what I’ve been told to fix first.
I also get questioned by a few of my peers regarding my ability to whip through tickets quickly. They want to know what the secret is. There is no secret. But I do have a few guidelines I’ve learned over the years that I follow that I think keep things on the path.
1. Everything gets a ticket.
2. Managers set priorities for a reason, and only upper managers can override them.
3. Every ticket will get assigned to someone ASAP, no more than 24 hours.
4. Every ticket will get a response ASP, no more than 24 hours, even if it’s to say “we are loooking into it”.
5. Looking at the list, any issue that requires less than 15 minutes will be fixed immediately.
6. Using the “this is critical to the customer” doesn’t work on me. Everyone uses that line.
7. Don’t call me with your problems, use the ticket system. I’ll call you.
8. When filling out a ticket, please include every piece of information you think might be relavent to fixing the problem. Including stuff like server name, ip address, and/or include things like error messages, screenshots, steps to reproduce the problem.
That should be all for now. Hope that helps clarify how to have an IT department people don’t despise!