234 replies
by salamander
I did a couple of things. First, I set up a simple database to log and track issue reporting. This covers the bases in the event that anyone ever has issues about responsiveness. It's tedious at times, but it has come in handy.
You might also ask the person directly. I recommend that this be done in person, but handle it in a very neutral manner: "I understand that you are having issues with x,y,z, but you haven't brought these to my attention directly. Why is that?" Then, just leave some silence, which most people will feel compelled to fill. If she says that she called you on a specific day, just look at your database printout, frown, and say: "That's not included in my log, and I would really like to help you with that. Do you have records of when you called? That would really help my troubleshooting."
I also made a written request that the user come in for remedial training for x, y, and z to the supervisor and copied the user on it. The word "remedial" provokes interesting reactions, so keep your tone very neutral, helpful, and non-accusatory in all other respects. Think hard on whether you want to use that word in your situation. If your user won't go for outside training, offer to do it yourself and have her come in for one-on-one training with you, at your convenience, in your office. Yes, this takes time. But, that gets the point across, resolves any honest issues that the user might have, and also demonstrates to management that you are going the extra mile to resolve the problem. The user will probably decline, but you have made the point that you are being aggressively helpful and have documented it.
You will probably never win this person over, but take heart in the thought that you are probably not the first target of this sort of behavior from this person. Others around you probably know the score more than you think.
by ddissent
by maineit
by sboivin
I have a service request form setup on the Inranet. It is simple the user goes to the page and fills the form out and then submits it. My IT department then recieves an email and completes the service request. If you set something like this up you can require its use by the company. So now the person cannot make such claims. It will also give you a method of metrix tracking as well... Hope this helps....
Shannon
by delbertpgh
by jimhm
Start if you don't already a call / break / fix tracking database. If you don't have one build one (I hate to say this) in Access and start logging all your support calls and response out comes -
Include an Blob area for Email and document attachments on each call. Create a Email account for the users to report trouble calls - along with a specific phone line - (have that phone line logged for incoming calls)
Document - document - document - otherwise its your word against her's - and guess who is going to lose .... it isn't her.
Best of luck ... once burnt twice learnt ... been there a long time ago - never will happen again ..
by jalhan
by navaneetham
Being a only person for call handling, it may be easy to form a call logging procedure. Announce this as a policy. Use a browser based solution( there are many freeware on the net), so that all users can use it with a minimal effort. This will avoid most of the talk behind you, even if they are done intentionaly.
Make a daily call to that lady for a week and ask about her problem. If possible visit her for week for this purpose and discuss it in front of others, to show you care. This will automatically put her off. Then you will see a change in her attitude.
Hope that helps.
Navaneetham, System Engineer, PSC, Muscat
navaneetham@hotmail.com
by corrielein
by raul62
Hello Corrielein,
from your comments, your are in a small organization (related to the number of employees). As you'd have realized, things become very personal in small groups. The point from the previous answers is very important: Try to be professional in your request, don't go into acusations, allow your internal customers to document their own actions (requests), document all your actions (answers, phone-calls, on-site assistance).
Beyond the "Problems-Solutions database", a good point is to open and close your work on a problem with an e-mail. Open asking for details, close with your solution, if the customer can follow some step, or describe what you did. This is not usefull only as a basic CRM, but as work-log for your boss.
Good luck,
Raul
by rene.klomp
What i meanby this, write a paper where ppl who wants support should act like and log it, so if he doesnt report something u can automatically say
No support needed today
keep that log and afterwards he cant say he you didnt help, you show the log and you show the procedure he should follow to get the desired support if not used no assist given
Try going to lunch or for an after work drink with her, get her alone on neutral ground where you are equals. Send her an invitation saying something like "to discuss the reoccuring difficulties you are experiencing". Make it clear that you are taking time just for her...
Make sure you go there with a listening and understanding attitude but don't hold her hand too much. Then sit down and let her pour it out. Most likely she has tons of problems which are not IT related e.g.pressure etc but which she can't spell out in the company, and therefore she is blaming you.
Maybe she doesn't want training because she has bad experiences of not understanding the trainings she was sent to? Maybe you have to start with raw basics with her...(ECDL could be a good idea...it's certication for her and you can be sure she knows what a floppy drive is etc..)
find out what the real problem is, there is a real problem behind it and you are gonna have to wade through the pseudo-problems till you find it. In my experience people tend to say it clearer than they think it, simply reflecting what they said often changes their impression of their situation considerably.
Even if she doesn't give you the clue you need to get her off your back you will find that you go up mighty high on her list for having listened for an hour and she will probably stop slagging you off even if she still claims to have those hundreds of problems which you don't solve...she'll probably start to claim that you can't solve her incredibly special problems...but maybe she'll jump in on the training if it's not presented as the problem solution but simply a certification course....
by ljnoyes
by thatboy
"Try going to lunch or for an after work drink with her, get her alone..."
There's a sexual harassment law suit waiting to happen.
Follow this link... I make all my trainees read this before I start training them!
http://members.iinet.net.au/~bofh/
-Joshua Leisk
I tried to follow your link but received a message that the page had moved. Can you provide a new link?
Thanks
by bangalang
I work in a school, and can totally understand where you are coming from with this. 90% of the problem is usually that people think they are an expert on the computer, when actually they have no idea. This just causes more aggro and tension. We had to invest in a HelpDesk to resolve the issue, and every user on the system has to log calls (even down to requests for printer cartridges) for each and every problem, and we respond to them accordingly. This eliminates the old "But I told you about it in the corridor ages ago" or the "But I phoned you on tuesday" type scenario. Unfotunately a HelpDesk that has individual users on it is not viable for everyone as they are not cheap.
Other than that just keep smiling and stay cheerful whenever you deal with this specific person.
This is not an easy task, if you do not have an issues tracking DB, you should invest you time in creating one.
Log all email and voice correspondence in this.
When you receive a phone call from the user, email back immediately confirming your conversation, this is painful, but it shows that you are been professional and want to ensure that you have captured their issues and concerns accurately.
Remember, a voice acknowledgement from a user is not worth the paper it is written on, hence follow-up email.
Offer your help in training, but remember to cc your manager and their manager, be flexible, but most important, write all your email in a neutral manner, and before you send any email on this subject, save it as draft (do not put their email address in either, just in case you click send by mistake) and take a break for 10-15 minutes away from your desk, when you get back, you should have a fresh perspective on what you are writing.
Good Luck
by wmdcrowder
If you're looking for an inexpensive off the shelf solution look at Wonder Desk. It's a great product and fairly cheap too. Has all the logging you'll need, email notification, etc.
Just in case you don't want to spend the time developing your own.
http://www.wonderdesk.com/
by dubjwalker
Hi Corrielein,
I had a very similar but there is a perfectly simple solution. Each time this user contacts you you should make a note of the date, time, problem and how you resolved it. The more detailed the better. This way you have a record of her problems (perhaps there's a recurring theme that will stand out?) and if it comes to the crunch you have detailed backup that she did not have such and such a problem on such and such a day. If it gets too much then you should bring your logs to the attention of her manager - particularly if she is bad-mouthing you to her own manager.
Hope this helps and don't feel like you are being sneaky by doing this because you are doing nothing wrong by logging your work.
Good luck,
Joanne
by donovanp
create a helpdesk (e.g Outlook) for reporting IT faults, including a FAQ section.
So doing you can have peace of mind that cals/requests are filed as well as users being able to help themselves re FAQ.
Set up a simple help-desk logging system (e.g. in XL or Access) and assign unique numbers to your calls. When a user logs a fault quote them back a ref number relating to the fault.
You can then request that all correspondance re reported problems should include this ref number to ' help you provide a more efficient service to your beloved users' ;-)
If the user has no Ref number then they can't complain.
It'll also give you some documentary evidence should things come to a head.
by amo
by nmaryn9
The suggestions for documentation, help desk, socializing, copy her supervisor, training, etc. are all good ones.
I suggest a more proactive, and somewhat drastic approach. She probably has not only outside stress or other problems at work here too (as suggested by some) but also may be using IT as the scapegoat for marginal or poor perormance not related to the PC, but it's a good place to divert atention. Here's my recommendation:
Take her PC away for at least 2 work days! During this period, clean the PC (make sure to vaccum her food crumbs out of the keyboard, wash the screen and scase, etc. Also, run a defragger on the HD. Look over her files - I'll bet she has data in several places, not well organized, and spends a great deal of time just finding work she needs to complete or follow up on - this may provide a good topic for training (file organization) that usually doesn't come up in other training.
E-mail her supervisor twice a day while ou have her PC to report that you are making good progress on clearing up some problems (unspecified) with the computer. In fact, you probably won't really spend more than 30 minutes of your valuable time actually working on her PC.
By the time you return the PC to her, she'll be so glad to have it back, she'll have to spend her time on catching up (unless ou give her a loaner machine while you have hers.) When you return it, make a point of getting her to see how nice and clean it is, and that you cleaned it up internally, as well as externally.
Follow the experience up with an e-mail to her, copy to her supervisor, enumerating that you cleaned the machine, checked the software, did "special" file and virus checking, etc. and make any recommendations about file structures and training in that e-mail.
Make it a point to be cheerful when you work with her and return the machine, making the point that you went above a beyond normal maintenance specially for her, because she's such a good person, she deserved your special attention.
I'll bet the shock of the experience will turn her in a new direction, since you have preempted most of the possible areas of complaint. Make sure her co-workers know that you went above and beyond, so she'll have no audience for future complaints, etc.
Good luck.
by imitra
Corrielein,
Create logger for all the internal calls that originate from the telephone of this lady.
Create a excel sheet about reports of IT breakdown reporting and your action.
Send all concerned the excelsheet which they should fill in and send you via email.
No Calls except from people you can trust.
Just document.
Best Regards
by pierre
Create system where calls are logged via e-mail and a reference number is returned to then stating that there call was logged. This work a 100% at our company.
Eg. Your ref: Deparment-log001/user
by jashburn
This is one of the cases where technology can lend a helping hand.
Just as it is with pierre, this system works at the company I work for.
Some benefits:
- Helpdesk calls are logged and updated, therefore no dispute over unresolved calls.
- If you're facing more calls than you can handle, you can ask for additional help from mgmt - the logging system is your proof.
- If you're good at what you do, you're able to publish your call clearance rate by mining the logging system. (Hey, we all need some self-advertisement, don't we? ;-)
Drawback:
- It'll only work if you have mgmt support. Users often find it easier to pick up the phone.
If you're able to get mgmt support, this is the way to go. Hth.
I found myself in a similar situation about 8 years ago, the only IT support person for a group of small companies (about 50-60 desktops, and a few servers). My primary role was that of developer, so I quickly developed an app that was used to log all requests for help and give the user a case #. Since I worked directly for one of the company groups, I had to charge time for the other company groups, which the application helped me track.
The trick was that I advised everyone that only requests made through the newly adopted "procedure" would be honored. It worked great.
by ecoyne
Have her sign-off on a repair form.
Also, make a company-wide announcement about how IT problems are to be reported and documented.
by rkallianpur
Hi Corrielein,
One way of combating this is to create a tracking mechanism for all calls, visits and problem resolutions. This way, you always have a record of calls to the helpdesk and can be shown to your managers if it ever comes up. You could also create a web-based form to report help desk problems. There are many inexpensive Help Desk applications out there which will ease your record-keeping needs. But primarily, you have to create/re-create the culture of logging every call.
Ravi Kallianpur
by bobpr
by brettnelson
I did this once with a troublesome location once. I had a server upgrade to do so it was convenient as well. I planted myself about 5 feet away from the individual in question and went about my work. The server was finished in about two days and I just worked remotely out of the location until the end of the week. You may not be able to do this due to geography or being the only IT person you may be required at the HQ. I don't know but give it some thought.
Strangly enough I only had to troubleshoot a few minor PC issues and answer a couple of questions. I joked around a bit and that "high-touch" method worked. The relationship became much better and I got calls when there really were problems.
Yes, and document everything.
There is always one in every family, so there isn't much you can do, but having a standard operating proceedure for logging incoming trouble tickets and being able to report on them is a definate requirement.
Another tactic that might be helpfull is to try and get inside the head of the person. What is the "pain" that is making them act this way. It is seldom what they are saying. A good example of this is another remote location in which one of the employees was taking upon themselves to by the local IT support person. Without really knowing or understanding the systems and not having the proper tools or permissions this individual turned to blaming the IT department. His frustration led to the fingerpointing, not any real technical problem. The solution was to designate him as the locations SPOC for all things technical, satisfying his desire to be involved but restricting him to user assistance (software) and referring tickets to the support desk. As well as being involved in some of our IT meetings and responsible for equipment requisitions etc. You get the idea. Good luck.
by didikai
There have been many good points and many recurring themes. My observations are:
1. Since you sound like the entire IT staff in your organization, you need to wear all the Helpdesk hats. You probably don't have much time to develop tracking software. One solution: go to http://www.repairwizard.com/ - they have very inexpensive helpdesk software that looks very good.
Set up a special email account called "helpdesk@your-org.com" and funnel all help calls through that. Set up an autoreply to acknowledge the email. Minimize phone call requests. TELL EVERYONE ABOUT YOUR NEW POLICY - several times. Brodcast email, internal memo, etc.
In those instances where a system is down, users can have a co-worker send the email. If the network is down - you should know already...
2. Understand your job. Repairing faulty systems, training users, etc are symptoms of your real problem - someone is unable to do what they need to do. They may be carrying emotional baggage like they really don't understand computers and feel that they can't communicate with technical people. Keep this in mind if you find yourself rolling yoour eyes at some user comment, or asking "What did you do to the computer this time?" There may be a track record of poor support that didn't happen on your watch. You will have to overcome their skepticism before you can find out what is really the problem.
A short war story: I had repeated calls about a new keyboard. Sure enough, a key kept popping off. However, I had no problems with using it. I talked to the user, who complained that the new keyboard just didn't feel right and she liked her old one much better. I scrounged up one of the old type and those trouble reports disappeared...the keyboard was fine, the user had a problem.
3. There is a tendency, particularly in your situation, for the IT staff to be spread too thin. A rule of thumb for a working network is one technician for every 100 systems. Geographic separation lowers this number. With more problems than time, you conduct triage, prioritizing and dealing with those problems that are the most important - IN YOUR MIND. The users who are left out (pushed down in the list) only see other repairs getting done and theirs not. This is a communication issue - directly between you and the user. Explain why. They may not like it but they won't feel out of the loop.
There are many other good points in the responses - go through them and grab the essentials.
You may be reading too much into the user's actions. On the other hand, "just because youare paranoid doesn't mean they aren't out to get you..."
Best of luck,
Samuel Norris
s_norris@email.com
TheFixers@repairman.com
by the moose
Phone the user regularly and ask if their PC is performing as expected. Document the calls and what was discussed.
Email everyone on a regular basis offering handy PC tips / shortcuts / security reminders etc. Have a standard email signature advertising your support services, contact number etc.
That will sort it.
by clemmy
I would suggest creating an IT logging procedure, if you don't already have one. Highlight exactly how to raise an IT query, and make sure that all requests have to be documented. Either only allow all requests to be raised via email or confirm all telephone requests via email.
Make sure everyone in the company has a copy of the procedure, collect a signature to confirm receipt of this.
This way you have a traceable route for everything that is asked of you.
by ej_kramer
1. Build fault reporting into your software
most software allows accees to the error handing routines and you capture the who, when, and the screen at the point of the error. Usres are amazed that you know/solve even before they report.
2. Have her report errors via her line manager.
(on paper) This will stop lying.
by julian.gill
by taurus67
corrielein,
document your IT activities (all) and that it includes the training and PC maintenance, and let the users sign on it for their acknowledgement. i work on our IT dept, i am supportin more that 100 users and this documentation works not only on tracking down my job but also in cases like yours. hope this will work.
good luck!
by commandgce
There are 3 role dimensions to this problem - task, people and power. And there are two ends to each dimension -
For 'task', you can attempt to prove you are the most task-oriented person around = keep records; or you can joke about it - tell everyone she's just trying to needle you and just poke merciless fun at her jibes.
For 'people' you can try to be 'Mr Nice Guy' = listen to everything she says, do whatever she feeds into the gutbucket line that she wants = chief Wuss; or you can start to send 'correctional' jibes about her into the same gutbucket = playing her game; you may even get personal - but you'll lose.
For 'power' you can start to market your skills and achievements to the whole organisation, especially showing that her problems are extremely tiny and hardly worth attention - anybody with half her skills would be solving the problems themselves, already = the pro-active stance; or you can be the total submissive - accept whatever is coming to you, sucker = the reactive stance.
For continued success in your own role, I'ld use a combination of super task-oriented + #1 power marketer. Keep the people role absolutely neutral - neither suck nor blow.
I have dichotomised each role type to its extreme - it is possible to play a little less than full steam - you know the old adage "Only use as much power as is needed to maintain good working relations"
by anobile
by notso
by dayit
by blackman
Dear Sir,
Having the same problem in my work. First Of all In each department we managed to create a list where anyone who has a technical problem writes hes name and derscription of the problem by hand!!! Every morning I collect the list with the problems. Anyone who has not writen a problem cannot complain (Right???). Also send a mail to everybody in your company and inform them for the existanse of the lists. No other job out of the list will be done. If something is very important to be done immediatelly demand to mail it to You, so you can be covered. Talk to your manager and ask him to change the way you work so you can do your work better and also be covered....
Don't worry shit happens.... I have been there...
Good Luck
James Black
My experience with people like your 'problem' user is that nothing you do will make her feel warm and fuzzy toward you; she's probably been slamming people behind their backs and playing innocent to their faces all her life. It's a win-win for her: she gets to play the victim and probably gets out of doing a lot of work in the bargain. All you can do is stop her from ruining your career and wasting your time, and you can do that with some of the excellent logging and tracking suggestions others have made.
I would emphasize that you *must* have the support of your own manager when instituting the tracking and logging. If you can't get the support of your own manager, find another job before she ruins this one for you. (Been there, been done like that.) Obviously, her manager is worthless, either having been taken in by her 'victim' role or having chosen to be supinely ignorant.
If she's smart, she'll stop complaining as soon as you start writing her complaints down...but most of this sort have had too much in life handed to them just for whingeing to think of stopping. When you have a month or six months' log of her petty complaints recorded in excruciating detail marked 'user needed to press Shift key' or 'problem resolved itself' (or even more likely, a blank log but gossip swirling around this office about how poorly you've served her), you and your manager can go to her and her manager and suggest tons of training. This sort hates actually having to take responsibility or do anything, so that will shut her up for good.
Good luck. I was fired from a job because one of these got the ear of my manager and half of my co-workers (the female half). She was very good at what she did, and I didn't see it coming.
Interesting idea...
Maybe someone is using you to mob on her?
Politics and intrigues are common where I work and I have heard of people priming employees from other departments to discredit colleagues with their supervisors. It seems that the false accusations are objective if they are made by a contact in a different team...I have never been involved on it but I hear it's been very nasty in the past and apparently even bosses have been heard to use it to get employees off their backs...
just one more thing helpdesk needs to cover it's back for....*sigh*
by luchomar
I agree with joanne ( posted a few days ago)that all the contacts should be in writting, however my suggestion is to check every single PC under your control from time to time to do "preventive" work, in other words you should be "one step ahead". If any problems occurs then easily you'll detected it.
regards,
Luis
by mlkiely
by bassettsk
by gpartridge
In my experience the best way to deal with a situation like this. Is to use a single point of contact at the company. All users must report problems to an internal contact and they will report the issues to you.
If this is not viable, just make sure that any support calls to you are reported to the contact or carbon copied to the contact.
This way the user cannot lie about reporting issues.
by caldeb
by pelhamc
Hi-
I agree that documenting everything is important. However, if you are a sole resource, you might have trouble shifting time away from the work to administrative tasks. I would go to management with a concern that in the interest of increasing efficiency, you would like to institute a method of problem reporting (whatever works best for your environment), and that you should be able to report some metrics out of your system of choice. Any middle or upper manager probably reads CEO magazine, and metrics is a hot topic.
Unless you are under-scheduled, which I doubt, this should work to yhour advantage.
Good Luck!
by web guru
by vectra-v6
It sounds like you have a person who has:
a. B*****d their way into a job that they cannot actually handle and is blaming the computer system for not being productive to hide this fact. or:
b. a computer phobia - technology now runs the work place and she cannot be honest to herself that she needs to be trained.
Either way you have to confront this person, point out that the PC is not faulty and offer to help her master the situation whichever one it is. But make it clear that you are not going to take flak on your competence by her accusations.
by wrlang
Sounds like the start of a right track-- at least you know someone is complaining.
Phone logs are a must. I would follow up every phone call with an email reply outlining the conversation. My company uses an email "HelpDesk" alert for all matters-- whther computer , housekeeping, maintenance, etc. This is an excellent log-- particulalry if the answer for most requests is, "Submit it through the Helpdesk and we can get working on it!".
It's not foolproof, but, where I come from, "...if it's not in writing it didn't happen...".
by balbino_ph
by richdit
by pete_reeves
Corrielein - I sympathise entirely. I would endorse 90% of the suggestions, especially about documenting the system and what it can/can't do. I'd be a bit hesitant about having to setup a Helpdesk system on a database, especially if the user concerned has to use it to log calls - what if it goes wrong? More ammunition for them to b*tch about IT in general.
If you don't have it already, take a look a Microsoft SharePoint services. It's like an Intranet but very simple to setup and maintain. You can control postings and content and has proven in my company to be an effective way of addressing IT issues.
I would then call a meeting with the department (and others too) and throw it open to any suggestions on what the users would want to see documented and what sort of level of problems they experience with the system. Make sure your user is there, plus her line manager, plus THEIR line manager if possible. Don't accuse her of anything but ask her (along with everyone else) if there are any issues with the system or if they ever have problems that they can't resolve. Odds on she will keep quiet - but if she doesn't then go with it for now. Assure her that her issues will be addressed and document them. By having everyone contribute she will have no excuse to carry on like this, especially as her boss's boss is taking note of what is being said.
It will be a pain, but I'd suggest making it a monthly meeting for the first couple of months. Keep the SharePoint site updated with issues/fixes etc and make sure the whole department can see it.
If she is seen to be making the same tired old routine tirade against you in front of the whole department I would imagine soon (if the management are any good at their job) that she would be offered an "alternative employment opportunity" - and they kick her sorry backside out of the door.
Best of luck from Across The Pond.... :)
by joekool24601
I am the only IT support person in my office (though not in my company), and if I were in your shoes, I would go to the line manager's most direct supervisor if you need to, however I would consider some alternatives first...
First of all, if your company has a digital phone system, then it probably logs every single phone call made- internally or externally, or it have this functionality that may be turned off. Ask whoever administers it to turn it on for a month and print out a weekly log of every call made to your phone. When this employee's extension doesn't show up, you have some proof.
Also, look at this employee's reputation- this sort of personality trait does not usually isolate itself to one area of life- talk to other support people, such as mailroom supervisors, administrative assistants, and members of your company's finance or bookeeping department to see if they have had similar experiences.
With this information, you can go to the line manager (which has so far been ineffectual)- this should force action. If not, go to HR with it and see what they can do. Good luck!
by dneal
by kkellar
by lisboac
by jdaughtry9
You are letting the (ab)user have the initiative. Get it back by implementing "processes to improve service". Here are three that have worked for me, use one or more as you need:
- Take requests by e-mail only, and save all of them with the responses. This automatically creates a log for you.
- Have all requests from one site channeled through a single point of contact. This person then becomes your point of verification.
- Have all phone calls go to a receptionist who logs them for you.
Each of these creates a third-party point of verification for calls and responses
by doug
I think all of us have this issue in some manner. I am the IT guy for a small company (35 employees, 25 workstations). Most of the time the issue arises from those least computer literate. And most to the time it is due to a loose connection between the chair and the keyboard. They don't understand what the system is supposed to do and don't want to admit it.
I'm not a trained IT Manager. Just absorbed it over the years and am the only one in the company that vaguely understands how it works. So, having set the scene, here is what I do, for what it's worth.
Tracking: I put TrackIT into use a year ago. I use the help desk portion of that system to track issues and resolutions. Don't have the time to set up a custom tracking system when there is one available.
Management: I issue a weekly newsletter to the "boss" keeping him apprised of current issues and answers. Those issues include comments on individual users and their habits. This works for me because I have a close relationship with him and may not be suitable for everyone.
Publication: I post a general email periodically about system problems, workarounds, new features, etc. I keep it non-personal but in that email I will address the "rumors" that have surfaced without mentioning names.
Confront the Issue: Not being quite so generous as most of you seem to be, if I've got a complainer on my hands and the anonymous approach does not work, I confront the issue directly. Either by phone (if that's the best I can do) or in person, I go to the complainers worksite. I plainly tell them what I have heard on the grapevine, ask what specific problems they are having, write them down, and either fix them (if they are legitimate complaints), explain how to use the system correcly or workaround the issue, and finally point out that if they don't notify me when they have a problem that is must not be a real problem.
by jimmypi
Make sure you have a tracking system that you use to doccument every call you get. Even if you solve the problem over the phone enter a ticket for it and close it yourself. After the first month you should start sending out a note to all the departments with the stats of open, closed, and pending tickets and give everyone access to even go look at the tracking system and enter in thier own tickets. At the bottom of this not or email you send out encourage people to call you or email you with thier problems and note the "normal" turn around time of your tickets.
A little advertising goes a long way....
I also experienced this only a supervisor complained to her own staff about me. I now require all calls be logged via e-mail and I use Microsoft Sharepoint Services web server to track all IT requests. I document every step of the way including initial call time and date , start time and date and solution end time and many other parameters. Fortunately for me I kept a log of e-mails prior to this so I had back up at the mediation. Good luck but document document document and require some sort of written logs etc and blast her back by showing no records for her problems.
Marc
by perseus
Buddy, tell me something. What's her beef ? Did you yank her chain or what ? Or is it that your predesessor/Boss yanked it ? If its not that then is she or her friend after your job ? This could be the only explanation of why she is bad mouthing you! :)
Well Jokes apart, you need to have a long patient talk with her. Take her to side and ask it up front. Let her pour as many fellow admins have suggested. It could be she's got a beef in which case she'll tell you. Or She's scared of her pc. (believe me people are!) Whatever you do, try not to involve her boss. Anyway he is not doing anything and second no point antagonising her further.
If this does not work out, ask her to give you records of calls made on E-mail. Activate Voice mail or give your Mobile Number to her. Best way is to publish it on some notice board or something. That way you will get a trail of her activities. Keep track and document it to your boss. If she does not want training may be its boring for her. jazz it up a bit if you could.
If all fails then bring it on. Hit back in true BOFH Style!!! :) Oh Yes Brother you need to read BOFH big time!
by hbofinger
Hate to say it - get out of IT. I got so sick of those problems that I dumped the field, 100%, after working in it for 10 years and making 160k a year. I did it all - user support, database development, web design, OOP, etc.
Problem is not really solvable, because it involves human issues and politics, not technology. The two don't rhyme well, and the technologist usually looses (unless you have very very good management at the top, which now rarely happens, at least in the U.S.) The pity is that you're probably the smartest one in the whole outfit, yet you hold no political clout.
by sc132
by help1
If you do not have helpdesk software, purchase some to track problems that arise.
If you do not have voicemail on your phone, ask if you can get it.
These serve as reference to problems for verification, otherwise this is an HR problem and I would approach them to get it solved.
by bob.mcgough
by bill
It's been my experience that to resolve this sort of situation it takes a proactive measure on your part.
Explain the situation to your supervisor, that when ever you check out her PC it seems fine, then obtain permission to 'work from her desk', or next to her desk for the next few days.
Move yourself there and be a constant presence, take notes, watch for problems (there may indeed be some you just haven't been able to reproduce).
After two or three days, possibly less with no problems, you'll have some documentation with which to dispute her claims if they start up again, which, in all likelyhood will stop once she's seen what you're willing to do to resolve the problem (if indeed there is a problem).
Last but not least, if you don't have a formal process, keep a ledger of every call, and I mean every call you receive each day, date, time, person calling and nature of the problem. Then update the ledger each day with your response and results noting yhe date and time it was resolved.
It would be a stretch for any manager to think you're simply ignoring this one individual, when making the effort to record everything else.
I wish you well.
-Bill
by kamotto
Dear Corrielein
The first thing I would do is have a one-on-one talk with this person. I would approach her in a neutral, professional way, and ask her questions geared toward making her aware that you know what's been going on.
Then, if you haven't already, I would keep a log of every phone call you receive with the time and general question/problem. And when you resolve the issue, have the user sign off on it (for those times when it requires you to physically visit their PC).
Hope this helps, and good luck!
CM
by wklogsdon
Hi Corrielein,
I have had a similiar experience in the past. When I wasn't able to resolve the conflict with the person directly, and the next in line with the chain of command, I went to the HR dept. and asked for a meeting with all 3 of us to attend.
Rather than point fingers at the other person and manager, I presented the information in this manner:
There seems to be a problem with a particular PC/ Program and the communication that has arisen as a result. When I have checked it, I found everything to function normally, so perhaps we need a different mode of of communicating problems. I have keep track of all phone calls ( there should be some sort of log you can pull up from a database, and emails are easy to track and printout.) Since I value all coworkers and want to help them, perhaps the two of you (irrate coworker and their manager) can tell me your thoughts and ideas as to how I can best serve you. You have accomplished:
1. A 3rd party (HR Dept) is now aware of the problem, knows that you are trying to improve communications and resolve all problems regardless of the origin.
2. Put the coworker and their manager on the spot to resolve the conflict for you, in front of HR. This will help absolve you of past complaints.
3. Establish a guideline for future problems and will seriously decrease the amount of future complaints.
In the advent, HR does not exist or offer such facilities, I would approach the CEO, President,... and let it be known that there is a serious problem to resolve.
I have found that when push comes to shove, and shove comes to biff, people stop when they are presented with solving their own problems.
At least it has worked for me. I hope this has helped.
by cneale
by mtufts
by mcpack
by matrixcsl
Hi
I think there is only one thing you can do.
Go to your line manager / his/her line manager, or even to the top and report your concerns, detailing any accusations etc, particularly payin attention to how it is making you feel etc. This will show that you care about your job. Perhaps you may also email/print out the fault reporting procedure with contact details, or even get her to complete a fault report log every time she claims to have one. Then there is a record of contact/fault reporting/your actions.
Good luck.
by shraven
by segurajp
by ec_rod
by praisegd
by shuffm1
by johann2_2
This of course depends on how good you are.
Create a situation where there is a definate problem and the user has absolutely no choice but to call you. You appear and run through all the usual procedures and then after the users fellow workers have noticed that you are there troubleshooting, resolve the problem that you yourself setup. Somewhat unethical but it may get the point across, that you do know what you are doing and that the user does not.
I've had a few of these too ..
Assuming you have a corporate PBX, get a report from the call logs on how often & when your user has called your extension, and then challenge the user on the allegations that they have been calling, and when. If you catch them out, then you can challenge them with evidence that they are not being truthful.
If this does not resolve the issue, you have a case (with the evidence above) to take the case to HR as a potential case of 'creation of a hostile workplace environment' which will make everyone sit up and take notice. Trust me on this, it's a hot button.
HOWEVER:
Basic rules:
1. Never lose your temper
2. Always, always, act professionally
3. Keep everything - emails, voicemails, notes of conversations and witnesses.
I know it may seem a little drastic, but these things can be exceptionally damaging to your career and you do not have to sit and take it. In fact *not* doing anything could be seen as an admission of incompetence.
Just my humble opinion.
Andy
by gdekhayser
1) Create an email officially requesting a list of problems that the user is having. Send a CC to her boss, and your boss. Make sure that the user SEES this CC, do NOT BCC. Put a read receipt request on it.
2) Most likely you will not get an answer to this- in which case problem solved.
3) If you DO get a list back, make sure that everyone in the CC list gets a copy. Acknowledge receipt the list IMMEDIATELY.
4) Make this list TOP priority and communicate often with the user (via this ad hoc mailing list) and get the user to confirm that each problem is solved. If the user never responds, again, problem solved.
Essentially, make sure that you go the extra mile to communicate with this user, and go just as far to demonstrate that user's lack of communication and you will look great, AND/OR you will actually solve this user's problems and make a believer out of her.
by beyondyu
Put a proposal forward to your management that, for
professional reasons, to install a system of logged reports of all
faults and for all staff under your aegis to log phone calls and to
fill in a fault report, (design a fault report form), so that you have
a good idea of the problem when you reach the location.
management will support any professional assist and it will look
good on your record. It will also make your 'bad-mouther' more
truthful
Try the BOFH section at www.theregister.co.uk
They carry the new columns, as well as archives.
by ken
I had a similar problem - it turned out that she heard that somebody said that they had overheard a conversation that somebody said that I had said something about her friend. (The gossip mill at that office worked overtime and was rarely accurate - but it did cause that user to become antagonistic with me.)
I attempted to solve the problem by talking directly to the user, and by offering to talk to the person I supposedly offended. Nothing worked and she continued to badmouth my work without informing me that there was a problem.
After two weeks of trying to resolve the problem, I created an Exchange form that would be used as a help ticket. I sent a memo to all departments stating that I was attempting to solve a problem with "lost help requests" and asked all users to submit help requests using that form.
This form solved a number of problems:
1 It helped me organize my work.
2 The form was later used to inform the user as to the status of that help ticket
3 It gave me the ability to document the work I had to do resulting in a larger IT budget the next year
4 It gave me an out with that user. All help tickets were viewable by all users (modifiable by me or the originator.)
A week later, she again attempted to tell office staff that I was unresponsive to her help request. Everybody could see that she had not submitted any such request. She is still antagonistic to me, but I don't have to put up with her bad-mouthing my work.
by lmnogoldfish
Sometimes an employee has performance problems in general. I.T. seems to be an easy place to blame to a lot of people because of the 'black hole' appearance people perceive about tech.
We have users just go and sit down if they get any message on the screen. Hours later someone will ask what's going on, and they'll have a 'press any key to continue' or some such and that's good enough to quit for some users.
We'll get 'my computer isn't working, there's some message' etc. etc.
If the complaints are really coming from the user ( i.e. not being slagged by the others reporting the user's complaints ), then a quiet meeting with the user's boss is neccessary.
Often, they'll know what's up, and you can form a strategy together.
Hope this helps, and here's to a positive outcome.
--Les
Next time she calls, have her Supervisor accompany/meet you at her desk, to see (In Person) that the problem is "Reporting Person's" error/Needs more training.
charletshew
by west4
by aogayar
If her computer works Ok when you check it, use Windows remote control to check remotely, and _send_ an e-mail to her, her manager and coworkers informing of this posibility.
Furthermore, establish a suppor policy with ticket support numbers who can be followed, and make this user's manager aware of the lackness of tickets from the user.
Be kind, smile to her, and have good luck
by glauer1
by tomsal
I feel your pain - I've had the same done to me over the years. However the problem is solved now -- we (myself and other IT associates) basically had enough of this stuff going on so we more or less said "ok everyone wants to play that game...fine...we'll play back."
Now its company policy that if you need IT assistance you are *REQUIRED* to submit it to a little request system we made using email.
The request is routed to the appropriate employee with the most relative skillset (database, programming, network, hardware, etc)...if its not sent through this request system you simply don't get help. Its that easy.
There are two exceptions to this however...
1) It doesn't apply to the top execs (yes its politics, yes its not totally right, but yes it is LIFE)
2) If its a situation classified as an emergency and this classification is based on IT discretion with a quick talk to the employees manager on the impact to departmental projects and / or priorities; but if its classified as an emergency that person gets priority support right then and there without a need for a request. But even then, after the work is done -- it has been documented.
A bit of a pain, yep. Do I like keeping logs of everything over doing things I enjoy like fixing PC, Server and Network issues - nope. But has the work paid off in the long run..you bet your arse!
Its amazing how much you can change a person's "mean or PO'd demeanor" on a issue when you have overwhelming facts on your side -- its a beautiful thing.
Always remember in both your professional and personal life...people will BS at every chance they get...BUT you can't BS fact!
later.
by dklandry
I can't stress enough the importance of IT policy in this situation. If you don't have one to address this particular matter you should create it now. Outline the Helpdesk process you want followed by any user. Have your manager approve the policy, circulate it to your users, and have them sign and return it. Keep them on file. Then make sure you follow the policy for EVERYONE all the time. No Exceptions!
The other posts suggested you document to CYA, and those are excellent recommendations to follow. In a one person shop it will always be your word against their's. Document the date/time called, a brief description of the problem, notes on resolution of the problem, and then close the work order only when the user indicates the problem is solved not when you believe it is. After that send an e-mail summarizing the problem and resolution to the problem user, their manager, and yours just to cover all bases.
Trending IT Employment posts
Sort by Trending