Discussion Locked

IT faults not being reported to department

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

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

234 replies

by longbeer

'Kin oath, mate! Confronting the person directly should be your last resort. If you're not very careful and lucky it will end in a he-said-she-said bunfight that you cannot win (no ever does), adds thin skinned and agressive to whatever has already been said about you and, assuming you work for decent management, you will both get a bollocking - you twice (by her boss AND yours).

Dealing with such problems is part and parcel of working in any service job and, let's face it, IT is a service unit for most businesses. You should:

Have a job/call/problem logging system in place. This is a general CYA issue for any IT dept (doubly so if you are contractors).

Make sure your boss knows about it. Not the other person's boss - that's your boss's perogative. If you go direct to her boss, it looks like you're trying to go over her head and that will get you nowhere pleasant. Coming from your boss it's a meeting of equals. See Mike's post above.

Make it obvious to the person complaining (and her workmates) that you are there to help. Stick your head in when you are at her site and say "hey, I heard you're having issues with such-and-such, I haven't seen the job ticket/report/etc, but since I'm down here..." My experience is that these people are either insecure or semi-competent and won't call for help because it might make them look dumb. Nine times out of ten, dealing with their problems face to face (and giving the IT dept a face to match the voice on the phone while you are at it) you find they are quite pleasant because it'e much harder to blag someone when they are in the room. The tenth time you'll get some a***hole who gives you an earful, but he was going to do it anyway - nothing you can do. You don't normally get that sort of behavior outside of junior management. Remain calm, explain you haven't seen their reports and that you are here to solve their problem. You'll come out smelling or roses and they look like a tool. This works every time, even when it's your fault, by the way.

Don't worry that being bad mouthed behind your back is hurting your image at work. If you are doing your job and other people will just put it down to a "personality clash". After all, there's only one person complaing, right? Besides, odds are you're not the only being complained about - her workmates probably know her as a whiner.

Executive summary - stay calm, maintain your professionalim (getting upset just validates the other person's statements), document everything (with a copy into the departmental Perl Harbour file), and keep your superiors in the loop 'cause it's actually their problem.

Laurie

by raghu

this is fairly routine problem for most of the support people.

U can send a group mail stating common problems that u have
solved in a recent week. U can also mention latest worms,
viruses etc that have been floating around. keep it short and
interesting.

At the end serve ur self for assistant for the group.

During ur second or third week, when people know that u are
going to make this a standard practice. Ask them, what more u
can add to help them. In this process include this person with a
little more attention.

hope this works for u too.

by lli

We know we are so talent, so patient and so
whatsoever for our jobs as IT staff, and
I think most people appreciate to our efforts.
Do not worry someone's "bad mouthing", she
will "kill" her reputation for sure, sooner or
later...

by dalin

this is a great idea. when i ask users why they don't report problems, they say they don't want to bother me or assume it's already been reported. having an online program with shared database, can easily create new workorders, search current workorders for the same or similar problems, show w/o priority, status, and maybe w/o ETA. this would make reporting problems much easier and help me better organize my to-do list with an easy to change priority number or date.

by bader_almahayni

For any system work or troubleshooting force the user to send you an email with a detailed description of the problem that they may have..

After troubleshooting or/and solving the issue reply to the email with the summery of the issue and how it was solved or what it should be done next, But, make sure you copy her/his supervisor to the reply.

by rsalucci

Is it important to be aggrivated over this if everyone else knows that you use due diligence in getting the job done? Especially your boss.
In other words, unless the complainer signs your paycheck and you are doing your job otherwise, I say to h*** with the complainer.
And when she really has a computer problem, she is not to be a priority. Let's see how long she plays the game now. (time to play hardball).

Another tact would be to send out an e-mail to Everyone reminding them that you are not clairvoyant or have a crystal ball and if anyone has computer problems, they need to bring it to your attention ASAP.

I think the important thing is to make the people that matter the most, the happiest.
When in doubt, refer to the food chain at your place of work.

Robert

by hairymick

First don't take it personal.
Second ask her what her problem is with communicating a problem.
Third point out that you are only able to address problems you know about.
Fourth point out you can track communications
Fifth Create an IT support form either paper or intranet and refuse to accept any other form of problem reporting.
Hope this help

by joew

I had a similiar situation and my solution was I took her manager and my director to her workstation and confronter her with all the rumor and reports that we are hearing. I called her on the spot and let her know that my logs show that she doesn't call me with issues and that she is undermining the IT Department. This is aggressive, but I was tired of her attacking IT at every opportunity.

by joels

I previously worked at a local computer store as the head repair tech., We had a contract with the local community college repairing PC's & Mac's for them.

When a problem occurred, the college required all of the employees fill out a repair request form stating, the model & serial # of the machine, the OS, the problem, the date, whether the problem was continuous or intermittent, severity of the problem, what software programs were open when the problem occurred.

All requests for repair were to be submitted after the same problem had occurred a minimum of 3 times.

The request for repair was handed in to the head of the IT department where it was signed & dated upon receipt. The request for repair was then given a #. It was then routed to the appropriate technician (computer or printer, PC or Mac, software or hardware).

The technician initialed & dated the time when the request for repair was received by them. The technician filled out the following blanks, could tech repeat problem (yes or no), analysis of problem, notes, parts required, time when request for repair completed.

The completed request for repair form was then handed back to the head of the IT department, the department head notified that person as to what had been found. The form was held onto for 3 weeks (in case the problem was not fixed correctly or reappeared), before it was filed.

This created a paper trail that could be followed from start to finish. It also gave the head of the IT department an insight into what was causing the problems (hardware, software, user ignorance).

by edtrimm

Rat Poison in her coffee? No? I go for the Direct Confrontation account in the presence of her line manager... than on up the line of protocol. You can't do your job if she's constantly having you come fix something that "ain't broke."

by try_hs

hi
1. You should record all activities
2. Create ticket and everytime you come & fix her computer, ask for signature
3. Create smal database about everyone's call and your action.

These activities will show actually about your activities.

Hope it helps

by Former member

i produce a full audit on his/her event Viewer
then every two hours i was exporting the event list . then i print it out ,and the next time that he/her says everything about me i went to my manager to the person that i report ,and i show how he/she use the pc ,and also i speak to the person who looks after the telephone center to filtering the report about the calls and for internal .and last i intsall on my pc and a his/her pc a remote administrating programm ,and i inform everybody about that so every one to know that i am online on he/her every time .and put a very larg book ,so them who says that they cannot find me ,to wright down every day the problems that they have ,and i was cheking the time of the report and the event viewer ,if the time is the wright one and no a day before or after ,and if the problem is real and appears in the event log .
and finaly hide from the users the event viewer .

by dougt

In an ideal world:
You should be able to explain this problem to your boss. This will acieve two things:
1) he/she might have an idea on how to deal with it
2) you've alerted him/her so if they hear about your alleged poor support via the grapevine, they'll know which pigeonhole of 'truth' to put it in straight away.

In the real world:
Not all managers are so supportive, and not all companies are formal enough to have line managers do battle on behalf of their employees. If this is the case, maybe you should still tell your boss, just to alert them, but go for one of the other ideas here like logging the calls.. maybe keep a diary so that you can say what you were doing when the person allegedly called you for support, etc?
I had one of these once. The whining user got her boss onto my boss before I realised what was happening. When my boss found out how it had happened, she was furious with the whiner.
Hope your guys are as supportive!

by donofry

If she's your only "bad-mouth" and everyone else KNOWS you're the "stuff" that gets the job done, I'd treat her like I treat everyone else and sooner or later all users/managers will know she's full of it. Chances are if she's complaining about you, someone else is also taking a hit without merit.

If all other users are happy, and you treat ALL users the same, you're good to go. Only you know THAT for sure.

Stay Well

by fvrba

If you don't make mistakes and you do your best to accommodate her, you have only two people to worry about. Yourself and whoever you report to. Everyone else knows what she's like and won't put any stock in what she's whinning about. Of course, she may have a friend or two but the vast majority know the truth.

by win0

For people as well as infrastrucute ! Develop, Publicise, and launch a Call Management Scheme within your organisation ! You can include a brief description of the requirement for such a scheme such as: "To avoid the problems that arise when staff "believe" they have logged a support issue but where there is no record of such, as has occurred at certain times". Initially, for small numbers of users, you could use an email logging system to a "dedicated" mailbox for instance. What ever you decide you must insist that calls are logged with accurate descriptions and once this is done, send the user a call or issue ID which they must refer to when discussing the particular issue on subsequent occassions. Its not worth confronting individuals such as the one mentioned. As a true IT person...render them ineffectual in their attempt to denigrate your good work by resorting to good service and a foolproof tracking system ! I've seen this situation arise many times, the cause is usually that the person is attempting to blame "IT" for the own ineptitude. Good Luck

by mluff

Corrielein,
Having worked for a large corp I have experience this problem and it was quelled by our Help Desk Ticket tracking system. We created a ticket, a copy was sent to the IT Manager, the user reporting the problem, and a copy to the Tech assigned to the problem. The ticket would show how many days it was open before the issue was resolved. Tickets could not be open longer than 30 days max. Generally they were resolved within 2 to 3 days , or you had some serious explaining to do. Any actions taken were updated in the ticket for reference to future problems. That way you can track if it is a "User Issue, or a Computer Issue." When management sees it is a user issue they will either have them re-trained or replaced. C.Y.A. and you will have no worries.
Good Luck,
MLUFF

by mansurk

Although I agree with the concept of documenting everything and Bcc your boss about it. In my experience, I have seen that some people try to look important as if they are the one running the show. The best approach I have seen is that one should avoid direct confrontation, rather keeping your direct management abreast with the situations is a good policy.

by jtfloors

After this person leaves to go home,replace there PC with another.and say nothing.See if this helps.If this does not work.Carry them to a office and have a hart to hart talk.and tell them they are slowing down other workers production.
if this does not come to a halt don't let the door hit there back side.

by corrielein

I've been out of the office all week on a course and have just come back to see all these replies. Thank you all very much for your input - I'll read them all through and use what I can.

by lmoose1

I have sometimes found that the person reported to have a problem was the problem person at all -- it was the one doing the reporting. Some enjoy 'drama' and manufacture it for others if they don't have enough of their own. Step back and take a look at who is passing on the complaints to you. Does that person tend to focus on imperfections or past woes? Do they have something against the other person? If several individuals confirm that one is complaining without reporting the problems, then that's more legitimate. If only one is, check that source as well as the reported complainer.

by matthew.chan

1. Use the email as communication evidence.
2. Treat her as a VIP users. Do a health check on her PC and its applicaiton to ensure it running smoothly. Then, send her the healthly status report. Ask her if any poblem find, report to you immediately.

by becker-2004

get documentation. as much as you can. email, paper, whatever. if it's not in writing, it doesnt exist.

log you work for her. problem. resolution. time spent. after 2 or 3 months you can take it to the next level if needed. most users calm down after a while.

by alamuru

If a user has got a problem,give him/her a form on which he/she fully describes the nature of her/his problem,date,name of user and the form must be signed by his/her line manager.After the IT department has resolved the problem the user must sign again the form as an indication that his/her problem has been resolved and return back the form to IT department for filing,this keeps a track record of faults per user and the IT department will know easily who needs training in which areas.This is also makes it easier to see who is not doing his/her job in the IT department.

Regards alamuru@natfood.co.zw
EDS Africa

by hal 9000

The first thing you have to understand is that the end user always knows it all even though they might be incapable of even turning on the unit in question.

Secondly just telling people that they have made a fault complaint to the IT department means the IT department should know as we are all physic.

Being in IT means you are responsible no matter what so get used to it no matter how unfair it is.

The only way to correct this particular problem is to keep an accurate phone log of all reports that come your way {I know it's a pain in the but but you are only covering yourself anyway} When you can show that you have received no complaints from either her or that section HR should go out and ask exactly what is going on here as the person in question is obviously not performing at peek efficiency and maybe even goofing off while supposedly working.

Of course there is always the other side of the coin as well once a long time ago in a Galaxy far far away I worked for IBM back in the mainframe days and the Social Security Department in a rural town had continual crashes which I could never understand until one day many months latter when I ran across one input operator who could enter data faster than the machine could handle it so it would just crash. When ever this woman wanted a break she deliberately crashed the entire system and brought everyone to a standstill but she had her smoke or cup of tea or whatever and the IT guys there where left to tear their hair out in an attempt to understand what was going on.

Col

by ppatel

Create a Job completion form. Whenenver you visit each user to resolve issues get their signature on their to make sure the issues are resolved. Approach this user, (be sugary sweet if you have to) ask her what her problem is and get her to sign the form. Once she signs, nobody can fault you. By the way watch your back. She sounds bitchy. Hope this helps.

by sysadmintech

Everyone has answer to your problem. but when I approch the techies with real technical question it takes weeks before someone tries to answer it.

I have given up on these easy to solve questions Im mean theres nothing wrong with a bit of advise, but this is what seperates the boys from the men. I have real technical issues and it seem like no one has an answer at this time. This is not the first time this happens it seems like people are afraid to answer the real tech questions. However when I find my answer I will post it for everyone just like I did last time and just for the record I usally end up solving the problem myself.

Just to answer your question you need to ignor this person and you will see it all go away. Dont add wood to the fire and eventually it will burn out. In addition when you communicate with this person you might want to communicate by email and cc: Her manager. You are so much better off with written documention in lieu of verbal communication. Like I always say (C.Y.A) Cover Your Ass

Good Luck

by west4

Old business addage is "Avoid Verbal Orders" same holds true in IT - Don't accept verbal requests otherwise you have no history to show your support. Lazy IT Users place the responsibility on you to do their paper trail and when your it how can you manage it? Don't accept verbals - require written notice and use Task Manager in Outlook if you lack a Help Desk Service. Crow Canyon makes a very affordable nice Help Desk System that integrates within Outlook. My IT Policy prohibits verbal requests period - I want a history and I do not care to type it in for them. Cannot bad mouth you if in fact verbal isn't permitted and you have your paper trail demonstarting support. A little CYA to support your end if you ever get challenged by a PITA such as this person.

by orso

When a user does not REPORT the problem, there is nothing to track.
Point is the user needs to call IT for help. I have found that users use IT as the "dog who ate my homework" when there really isn't anything wrong. Also, users have been embarassed to call for help.

be proactive, call and ask if anything is wrong. and document that. also, let the person's manager know. going above someone's head never gets respect, but it does cover your ass and reputaion.

This discussion is closed to new replies.