IT faults not being reported to department
This is page 2 of the discussion. Read the opening post
IT Employment
This is page 2 of the discussion. Read the opening post
by dr_andy
by glamaster
by km8295
Bad-mouthing is so often a symptom of a deeper disease. Sadly, most people aren't honest enough with themselves to admit what is the real problem. When this co-worker isn't clicking with you or has a bad feeling towards you, she may re-direct that into slander. This is hard for I/T types to hear. Take a look at how the overall relationship is going next time you work with her. Ask questions that show an interest in the problems she is having, how she uses her computer, and what unmet business needs she has that the computer might address. If you do this well enough, you may even cause her to support you even if you mess up sometime -- the opposite of what you experience now.
People are fickle. Human nature is a strange and perverted animal, and you must deal with it as it is. People often don't know themselves or what is really bothering them. Dare I say, this goes even more for women! Be a bit of a friend and you may turn an enemy into a fan. Same goes for her line manager -- if that person sees you as both capable and helpful, low-level complaints just won't get anywhere.
by jim finn
by ct670
I agree with this.
As I' was reading through, I was hoping someone wouldI agree with this.
As I' was reading through, I was hoping someone would mention this side. How do you know for an absolute fact that she is saying all these things.
Also what your colleagues are telling you of this lady?s behavior is gossip (whether it is true or not). The best way to deal with gossip is to take precaution regarding what you are being told is happening, by documenting, logging, or the many good suggestions given here.
After that whenever someone reports what she says, be very neutral, do not let yourself be drawn into bad-mouthing her, just tell whoever it reporting her that your sure that now that you have a system for reporting faults, that if she has a problem you have no doubt she will have put a request in.
The problem with mad-mouthing is that no-one ever wins.
Take heart, many of us have been in similar situations
by bhwow
It is possible this person may genuinely have a problem with her computer (unlikely), or even her computer skills, or lack there of (more than likely). None the less I am reading that your problem is more office politics and not technical, your question is directed more toward "how do I handle personnel" especially the ones that are attacking my reputation and job standing.
So to that side of the problem - here is some hard earned advice.
1. First and foremost you must change your own self image! "Power Perceived is Power Received" In short re-examine your job role/duties/status as IT support 'person' (almost demeaning) try using IT Support PROFESSIONAL or TECHNICIAN. You say you spoke to her line-leader - this is how a co-worker and equal would handle a bad mouthing problem - and it definitely puts you in a he said she said situation. Besides managers are somewhat immune to disputes among co-workers (for good reason!). Being an equal gives others the choice whether to co-operate with you, even over computer matters. So you MUST decide what authority is reasonable for you to exert relevant to carrying out and achieving your job responsibilities and position, then incorporate this into your demeanor and project this image to others with the expectation that they treat you accordingly (including management - and line-leaders). This is the most powerful tool you have. **I am guessing that as the only IT ?Manager? your job has never really been defined beyond what you are responsible for, if this is true and you are worried how management will react - then, once you?ve decided what authority you need , have a meeting with the person or department head that hired you, gave you your job duties or your boss (the higher up the better). Keep it as casual as possible, present your concerns toward how the company will benefit by or lose from your action or inaction, all the while do not act or talk like you are asking for permission but rather looking for additional input/thoughts/ideas that might expand upon or uncover missed areas of concern from those higher up (this action has the added benefit that you will have outlined your ability to perform your job and stated your commitment in carrying it out in the best manner possible within the confounds of company policy.
2. Document - Document - Document, but also do it the way other department heads or managers would! You covered first base, ask the individual directly. Next write a brief but to the point letter/note for everyone in that job group, be specific ?if you experience computer? please do this? & ?I am available to discuss software programs?(by appointment - on ?day? am/pm - anytime, etc)? feel free to check with me regarding new software, or if you think a program is not responding the way you think it should? and so on. Adding boldly in a hard to miss location (like under their name or position) ?Copy to the all managers?. Then write a different letter for managers? outlining what was stated in the first and of course extending the same services/support to them, also ask them to encourage their staff/department to communicate with you regarding any questions they might have. Adding , that it would be greatly appreciated if they (as managers) would let you know if they notice anyone having continued difficulties or problems with their computers. Maybe adding - would they please remind people that it is easy to forget to report small problems - that are easy to fix and that usually don?t affect productivity - but the consequences of this type of inaction can be ??? Serious ??? Ask them to stress that reporting problems is every ones responsibility. (this action should have the added benefit of stating ?shared blame? and also get managers to discuss YOU with their employees in an authoritative role, and more as their equal with their authority behind you.
3. Do everything else IT related as well - don?t crowd yourself, or tell others you will be doing this or that until you are sure that you can complete and deliver - no need in making yourself look bad too!
Hope this helps.
Open computer management
double click logical drives
right click the drive you want to log
properties
security
advanced
audit
From here you can set who to audit.
The next time she starts bad mouthing you, get her supervisor and the user and review the audit.
This will tell no lies.
by pipe guy
Documentation is great but only if someone else knows you're doing it and sees it before you reach crisis stage.
1.Use your logging system to produce and inventory of the problems reported to date for her and her alone.
2. Set up a meeting with her to review the list and, most important, add to it anything that is not working, that doesn't work sometimes etc. that is not already on your list.
Make sure that she knows you take her situation so seriously that you are committed to doing this as long and as often as it takes.
3. Regardless of the length of the list, have her triage for you - what are the most important ones to resolve first from HER perspective.
a. If the list is really long, you may want to take the PC for a tune-up as another post suggested but be sure to schedule the time around her work - no sense letting her blame you for missed deadlines.
b. When we suspect user error and need to train, we use a 'procedural review' session - where we just sit and watch the user execute the task/software in question. We can then offer "helpful hints" or refresher training if the problems are chronic. We never say 'remedial' as it is so loaded and reporting that someone has repeatedly taken refresher training makes the same point but less, err.. pointedly.
5. When you have a final list, email it to her and both your bosses "Jane's Problem Punch list as of mm/dd/yyyy).
a. If a tune up of the pc or one-on-one sessions are indicated as resolution for certain problems note it (schedule it before you leave the meeting or indicate that you are 'waiting to hear from Jane on a good date'
b. indicate priority/work sequence
c. Where you can sensibly do so, commit to a delivery date (will install version 7.2 by 08 June)
6. At least 2x week initially send regular updates as you resolve problems. Highlight additions (recurrences or new) as well as resolutions. You can back of to weekly if/as things improve.
7.DO NOT close the call until you have her sign off; just indicating that you believe there is resolution and you are awaiting her sign off - via email, individually on each problem.
7. If something happens "sometimes" and you cannot replicate, leave it open for monitoring. Ask her to email (better documentation)as soon as it happens again. Better to leave it open and unresolved (because it hasn't happened again) for a long time than to close it at your discretion. Once something has been on the list for >3 mos. ask her if she wants you to continue to monitor it actively. It's her decision - it's her list.
8.Meet with her, in person, to review the list every week (move to every other week, once a month) so that you can both review progress and triage. Even if there is nothing on the list, send a copy of the finalized version to her and your bosses - so that everyone knows status.
Note: The list must include (at this point) both open calls (including those awaiting her sign off and those you are monitoring) but esp. anything that came in since the last review that you BOTH agreed to close out.
We have used this approach for 3 years in my org. with great success. We've done it with entire units and their boss, just the boss, just an individual (always copying the bosses (theirs and ours)).
Invariably the list starts much longer and ends empty/nearly empty. After awhile, the users no longer want to take the time for the meetings and review and ask to stop. We always make it clear we can reinstitute this if they ever feel that their support from us is "slipping."
by cad
I would start giving her a courtesy call every day letting her know that you do care how things are running for her.
I would then document each and every call.
by glyn_canada
You waste your time, achieve nothing but making the person feel like they have a new friend and document a bunch of calls.
This does not solve the problem, just records it and boosts an already overinflated ego
glyn
by ppclark3
There are also some shareware and opensource helpdesk tracking tools. Have used RT Request Tracker which is an open source and works very well. We require ALL requests to be submitted to the helpdesk via email (unless computer or network is down, which they can phone in and the helpdesk staff has to enter).
This way for this exact reason we have the history or how many calls, what has happened and who said what! While there is still some griping the question is almost always asked "did you put it in the helpdesk?" Now this will take support from the management but is well worth it and RT is a great tool. Whatever tracking tool you use, get one and use it. Not only does it address this specific issue it helps build a knowledge base of problems/solutions.
by t-cally
In most cases these are employees that aren't being productive so blaming the computer which they feel can't be track because "computers are known for having mysterious problems". So how do you shut up a lazy employee, fire them. But since you don't have the power, put a case together for the manager to do so or at least to clear your IT commitment. And if her management is blaming the computer then they need to prove to you that it is malfunctioning and let them know that you can't fix what is not broken. Often managers are scared of employees and so they will let it go as a computer problem to avoid their real issue, the lazy and or manipulating employee.
1. Track and print the event logs (assuming windows environment), this will let you and management know weather or not there are problems.
2. Lock the employee privileges down to power user if at admin or to user if at power. Note the number of internet "free software" and games installed on the pc. Check the favorite and cookie log to see where the employee goes to. A streaming music or video will of course bog down a pc. Also, check for active desktop or third party screen saver which can become a problem.
3. If possible set up a new pc as a backup to switch over to when her current pc is having problems or offer it up now as a solution to see if "the mysterious problems continue". Have the employee print any error messages or simply not touch the pc and go to the backup and leave the error message up when it happens. If you can use pc anywhere or compatible software you could monitor the desktop as it happens.
4. Talk to the others employees or management to see if the are performance issues with the employee.
5. If you don?t think it is an employee issue, check and or change the physical memory. Faulty memory can have its ghostly problems.
6. Pray.
by glyn_canada
"Check the favorite and cookie log to see where the employee goes to."
You must be the most senior technically minded person in your organization. If I found anyone doing this unsanctioned, then they'd get in more trouble than the user. I have had to defend "big brother" actions in the past and almost got fired.
"4. Talk to the others employees or management to see if the are performance issues with the employee."
Explain the difference between this and the initial problem the user has caused in the first place. It sounds like whining about a co-worker to me.
Yes, talk to your Manager about the whole situation and mention this to them at this point.
Do not gossip to others.
Do not go to your Manager saying "So-and-so said nasty things about me, does she do this to everyone?"
by t-cally
Hi Glyn,
I'm not suggesting that our comrade go postal, in all things you are to stay professional and calm. But that doesn't mean to be someone?s escape goat. It the company hired you to do this job let them define it and define your authority. Now that being said, yes she should let management know what her intention are and get approval to be "big brother" but don't be manipulated.
If a company will not stand by you now, get to packing when it hits the fan because you are going to be the problem. One replier suggested taking her out to lunch, your are to pray for your enemy not wine and dine them, you aren't a social worker unless that's the field you choose to be in.
Corrielein said that this was an off site and my suggestion to talk to others is not for gossiping, merely to get information to know what you are dealing with. I?m sorry I didn?t better explain that. By simply engaging in conversation with other employees there, see if that are having similar problems as the problem child is. People will offer up information or even body gesture without you asking. I'll beat they are tried of hearing her problems too. She could sit with the employee and the line manager from log on until about an hour into the day but I'll beat you the employee would have a problem with that or nothing would happen.
In the matter of big brother, if the employee owns the computer then there could be a problem. However, if the company owns the computer then they need to establish the rules and by-laws governing the use of company equipment (not compromising any federal and state laws which aren?t address in a company?s by-law that should have been read and understood by the employee just before the sign here signature block). Corrielein should not have to go home with a headache because of one employee who continues to have undocumented and or unreported problems and a line manager who does nothing.
by cableguy414
The biggest way to prevent this problem from coming back to bite you is to start documenting your support calls. Currently, where I work, we have a web based "trouble ticket" system. It is very crude, but it works to track IT issues. When someone calls us directly, we either ask them to please open up a trouble ticket, or we open one ourselves for the call. This way our butts are covered when someone complains about our responsiveness, we can track issues and our response time.
You can begin to build one yourself with Access were you would need to log all issues manually, but this can still cause you a problem because your problem user could then claim that they called but you just never entered it into your DB. There a many boxed trouble ticket software packages out there that will help you track your IT related issues and how and when you responded. This way, when the person says that she called you and you didn't do anything, you can ask her if she "opened up a ticket".
by nagelpg
I see the issue as a perceived problem on the end user's side. Remember IT support is more about dealing with people than with hardware and software.
Ask the user to leave everything as is next time she experience the "problem" and give you a call to which you must respond immidiately.
It might also help your cause to give the workstation a once-over, after hours, to ensure that the issue resides on the user's end.
You must win this person over or hope she resigns,
working in "an atmosphere" does not contribute to your well being or best performance.
A timesheet / callout log are for your use to show what you have been doing and which systems are nearing end of life. This will only prove you right - it will not make the perceived problem go away.
by glyn_canada
Hi Corrielein,
to sum up what I have read so far:
1. Get your boss on board
2. Suggest a help desk policy if one is not already in place - and follow through until it gets written, approved and signed.
3. Set up a calls database or if you use Outlook, then a automated form for all break/fix calls.
4. Document the situation up to your ying yang (like the alliteration?)
5. Fix the problems when they actually occur, in a timely manner. NOTE: Do not jump when she says so. Treat her in the same way that you would treat a call from the human part of the workforce. If you do jump, then she has won her little passive aggressive struggle and will stop whining, but start boasting that you are her tech-bitch.
6. Follow up at job close via e-mail and request a response "for your helpdesk database", but it is actually to CYA.
7. Review the new helpdek system with your boss after a month, so as they can see the stats.
8. Use the same system for everyone, because if she gets wind that this is special treatment then she will have cause to complain
NOTES:
a) Always be professional. It is OK to ask for assistance to help sort out a problem, but not to stoop to her level and whine all day long to anyone who will listen. (BTW on this forum you have handled this well.)
b) Don't take her out for beers. You have a job to do and it is HR's job to find out what her problems are. Repeat the Sysadmin Mantra - "My job is to ensure that the users can access network resources and use the applications they need to do their job". You don't need to take her monkeys on your back as well as your own. (Read "the one minute manager meets the monkey" to understand about monkeys)
LINK: http://www.amazon.com/exec/obidos/tg/detail/-/0688103804/002-5561641-9148026?v=glance
c) Suggest to your manager about a remedial training program and suggest to him/her that you have an ideal test candidate. Do not go to the person and suggest it as she is 95% likely to get even more obnoxious if you point out a fault (whether it is there or not)
d) Read the BOFH at www.theregister.co.uk for fun. Don't take it too seriously as everyone hates a self-righteous network nazi.
by maudelin
I have not had experience with this type of situation but I think that the solutions outlined here are professional and will provide results.
Obviously, if this user is being malicious, then it is up to the IT Support person to disprove her claim? It might be useful for the IT Support to implement some type of evaluation of service request so that user can supply feedback on how timely the response was, how professional the support staff, etc. etc. If this user is the only one with a problem, it should speak volumes to management.
by maudelin
I have not had experience with this type of situation but I think that the solutions outlined here are professional and will provide results.
Obviously, if this user is being malicious, then it is up to the IT Support person to disprove her claim? It might be useful for the IT Support to implement some type of evaluation of service request so that user can supply feedback on how timely the response was, how professional the support staff, etc. etc. If this user is the only one with a problem, it should speak volumes to management.
by turnthepage
by dracowiz
by mek804
I implemented Web Help Desk for $4000, ten technician seats
plus hardware. It tracks what we do, e-mails clients about what
we do, and is *truly* platform-independent via web browser
(NOT windows only or MSIE only).
It's been a big help, and it has helped me with the very situation
that started this thread--we log EVERY call and message we get,
and when we hear "I.T. never responds to...", our response is "we
have no record of you contacting us about that. Did you get a
help desk ticket number?"... they shut up every time...
Web Help Desk works on Windows, Mac OS X, or Solaris servers
and uses just about any major database.
(no, I don't get kickbacks, either, darn it)
by eatimms
Schedule a meeting with her, your supervisor (unless you are the supervisor), if you are the supervisor, have a member of Human Resources, her supervisor.
Explain to her that you have heard she has had numerous problems, however, you've not been informed. Let her know you'd like to help her resolve these issues, but she needs to communicate with you. We use a system called Track IT and this has helped us tremendously.
If you communicate via email, have all correspondence marked with the option of letting you know when they were delivered and read (or deleted without being read). A paper trail is sometimes the best method, but when supervisors get involved, that also tends to lend some weight to the matter.
by techlizard
by steveplante
Rather than seeking revenge or retribution, seek to involve that 'Trouble Person' in the solution.
(with management approval) Create a monthly contest to engage all of the users in a program to improve the quality of the network and installed applications for the good of all. Simply establish a mailbox or a webpage to collect the input (a database to collect and tally suggestions and an autoresponder function would be nice add-ons).
It is likely that if a person desires the attention gained by crying, they may also be driven to participate.
Good Luck
by is1
I've had issues like this but luckily we were already implementing a helpdesk, if you can swing it in your budget a helpdesk can help you with this type of issue's.
Since it?s an outside program one you didn't create to catch these people in a lie it's viewed in a friendlier manner, and the history of service calls is invaluable when showing a need for additional training.
by scriggly
In my case, the person who was blaming IT for all their computer problems was using it as an excuse for not getting their work finished. It's especially easy to blame IT when you haven't got something done "My computer kept crashing". She eventually got caught, but in the meantime, I agree with everyone...CYA (Cover Your Ass) Policy wherever you go. I also agree that confrontation is good...I'd ask her why she hasn't reported the problems and let her know that it's company policy.
Then again, she just might have a bone to pick with the company, and you are a convenient scapegoat.
Hope this helps.
by tkendr01
It appears as though you are a combined helpdesk/call center, troubleshooter and department interface. Too many hats!
One way to split this out without increasing headcount is to ask for an e-mail record from the problem reporter (any of them). It may be a form (desirable) or just freeform text.
Currently, it's all verbal - no audit trail - for existent and non-existent problems. It's not too hard to see why this person's manager fails to act: no problem records created by the problem reporter. Just your word against hers.
The problem tickets MUST somehow be the responsibility of the problem reporter. Either phone logs or e-mail.
Another angle would be to enlist the support of just one of her co-workers to call you when she starts complaining. You take it from there.
"It appears as though you are a combined helpdesk/call center, troubleshooter and department interface. Too many hats!
" Take a look at my username. :)
I also am the only "Computer Guy" at a small company. From my experience this is normal behaviour. Why? Because if the problem user actually makes a documented request to have the "problem" taken care of they lose their "out" in the process. The "out" is the constant *itching that computer users use to blame/scapegoat problems on some unknown "computer problem". In my experience it very often turns out to be lack of knowledge or understanding in using a computer on the part of the user. Pointing that out in any sort of public way is not a good idea.
Talk directly to this person and get exact details about what is wrong. Make it clear that you know they have not been reporting these problems to you. Ask them why. Take steps to solve any problems they identify to you and document those efforts.
I also developed my own problem tracking database, more to cover my own butt than anything else. Certain problems still go unreported. When you are the only one performing a job it is easy for others to blame you. Get a manager in on this and outline the details in full.
by jcostac69
1.- Design a form to report faults. Everybody should report faults using this new form. Or/and fill yourself a report for each call you receive and make the user sign after you fix it. Together with...
2.- Publish statistics of how many reports you have each day, week, month, how many you solve by department. Include in this statistic some column telling recurring problems. This will put this user in evidence and keep you safe.
Regards,
by randy2163
by gfawcett3
Institute an 'Approved" mechanism for requesting assistance and disallow deviations.
1-ALL requests for IT assistance must be sent by email DIRECTLY TO THE INDIVIDUALS manager (If they phone you, report them to HR.)
2-These requests must be forwarded from their managers email to your managers email and must be forwarded from your manager to you.
3-You reply by email (which should automatically generate 'hidden' emails to be sent to each manager in turn. (Or hit 'Reply All')
4-In your email state when you will be there and be on time.
5-When you get to their machine, log into your trouble-ticket database remotely and say something like "commencing diagnostics."
6-Have your bucket capture MachineID, date and Time.
7-Log back in when done and say "Problem was/is and 'Completed" or "Awaiting parts" or whatever.
8-Cause your trouble bucket to dump an email to you, your manager, their manager and the motor-mouth stating 'Completed" or "Awaiting parts" or whatever.
9-Require ALL personnell to physically sign a pre-printed document with the ticket number that says "DONE" or whatever. - Keep them in a LOCKED drawer.
10-Cut and paste this entry to an email that is sent to your Manager, their manager etc until the President of the company receives it.
11-Have the President of the Company forward it to all employees and all Contractors with a forward that says: APPROVED!
Persons attempting to submit IT requests through any other means will be subject to reprimand and or dismissal.
12-Include this policy in the Employee Handbook.
13-Have the Company pay for your lunch today and pat you on the back.
I hope this isn't a repeat of whatever was posted above but there were so many of them I quit reading.
Good Luck
by kjc
I have several issues with this proposed solution:
1. What if you have managers like mine...That only check their email once a day? What if there is a true emergency (The only program I use is broken), and is not reported until the next day? An entire day's work is lost, because the issue was not reported in a timely manner.
2. What if this is a problem with their email client? Or Keyboard? Or monitor? How is the user supposed to email their request to their supervisor if they can't get to email.
3. This seems like a waste of the manager's time, to have to "approve" IT requests. We have a department where 99% of that department's requests come from the manager, but only because she has tried to fix the problem before reporting the issue (She knows her limits, and generally does not make things worse.)
Maybe I work in a company that provides more autonomy than most, but for the most part, users properly submit their requests, without involving supervisors. This has taken quite a bit of user education, but most of them get it.
We have separate phone and email to report issues, and emphasize that unless it is an absolute emergency (the network is down), requests go to Help Desk email.
by robotech
Excellent points, but not all places may be so formal or have the necessary infrastructure to do all that you have suggested. Most managers/supervisors are so busy, they don't want to get caught up in this sort of thing. That's why they hired us in the first place.
Maybe this person has vile intentions, or maybe he/she likes you and is too immature/proud to express him/herself appropriately. Whatever the reason, the two things you don't want to do are:
1. Waste your time and the time of others.
2. Uneccesarily hurt that person, physically or emotionally.
That being the case I would send an e-mail to everyone in the company with the following message:
'Good morning, I just wanted to seize the opportunity to remind everyone of the procedure to follow when help is needed to resolve an IT issue. The first step is to close all programs, restart your computer, and then log in again. If the problem was not just a one time glitch, it should reappear. In that case, send me an e-mail if you can and I will reply with a solution, or a time for a scheduled visit. Please do not change the subject line or the body of the e-mail when replying, as this will help in the troubleshooting process.
If I do not respond within thirty minutes, or if your computer is sufficiently affected so as to prevent you from carrying out vital job tasks, then feel free to contact my Supervisor at Extension xxx. He/She will then be able to contact me or take the neccesary action to restore your computer.'
With this reply, you are respecting the person's dignity (and even though they might not deserve it, do it anyway). You are also giving them a chance to change their ways, letting them know that you are aware of the problem, and since everyone is copied on this they will think twice about running their mouth. If they continue to bad-mouth you, then people will begin to realize that this person is the only one with a problem. Soon enough there will be enough complaints (from fellow employees)about that person, for senior management to send them a letter/reprimand etc.
And of course you wouldn't have to lift a finger, all your precious time would now be spent reading TechRepublic. :-)
by lamersek
by mr_mel_h
I think every tech has one know everything end user that seems to give them the same type grief from time to time. More often then not it is an end user training issue.
We (our IS staff) pushed the upper management to include computer knowledge in all employees evaluations. We put together, and made available to all supervisors on the network, some short test to help with the computer knowledge portion of the evaluations. These test are changed ever three months so the end user can?t fake their way throw it.
We also send a report to all department heads of how and who the I.S. Staff helped each month. This will show the department heads just witch of their staff is or isn?t asking for help. If they are asking for help the report will show how much and for what. If their staff is isn?t asking for help the test will show if they should setup some training time with the I.S. staff.
by mlayton
by jlopez_ortiz
by dblaylock
Our firm is not quite large enough to justify an elaborate helpdesk setup. Just 1 person - me. After having run into these situations repeatedly, the CYA rule became real important.
My solution -- POLICIES. All PC problem requests must be emailed to me with a cc to the office administrator -- only exception being a total system meltdown. Theory here ... no email message -- it didn't happen. No exceptions. Getting the support of administration is the key. I have found that confronting professionals no matter how well you handle the conversation always seems to goes badly.
by geeen
Everyone has put in great suggestions, I didn't read through all of them of course, but if someone mentioned this, Great -
I had a problem like this, working in a Mid Sized Company with an IT budget of almost next to nothing, I had to do a couple of things manually. When this happened to me, the first thing I did was went directly to the person and said, 'Heard you were having some problems - what can I do to help you.' Going through everything they claimed wasn't working - after that, give them a call once a day or once every other day - Keep it simple, "Hi, how's everything going with your system? Are you still running into any problems?"
When they see you are watching them - They tend to stand down......
by john
I have walked in on a situation like this, sweeping up after one of my junior's hastle.
It turned out the complainer did have real problems of the intermittant kind.
The engineer swore there was nothing wrong - it had been checked numerous times - client said there was etc etc. It has gone on for weeks.
Only after a suppling a longer network cable that didn't get in the way of the user's feet (the engineer was short) was it all resolved.
by thumper1
Respond to everything concerning her problems in writing, including all conversations, forwarding copies to appropriate management. You might want to take time to check on her once or twice daily in person. (A little hand holding, besides, it?s tough to bad mouth you if you show your face in her department on a daily basis) Be extremely tactful. Document everything. I manage networks in two law firms for the past seven years. Run into this occasionally. It?s a situation where you have to win, but you can do yourself a lot of damage if you don?t do it right.
Three undeniable laws of computer service:
1) No good deed goes unpunished.
2) He who touches it last loses.
3) The truth, while amusing and interesting, it totally irrelevant. Perception is the only thing that counts.
Good Luck
Bill
...is what I feel like throwing on these people. Basically these types of folks are somehow maladjusted socially, have problems at home, or some other problem where they learned to make others' lives miserable. All the way from middle management to a scanner admin.
What I read from most of these seems really good. Documentation, logs, anything to keep track of discourse. Thank goodness that they are in the minority.
by hal.potter
by pcitech
create an e-mail account to receive all support requests. That means that you will no receive any phone call for that pourpose. In case of an emergency, users can phone you only to ask you to give high priority to a previously mailed request. When you finish a request you send a mail to the user just to document and close the report.
There is another point to take into account: the level of help asked. Some times users call to report they can not print, when the only problem is that the printer is offline. In that very trivial situations, users should be capable of resolving the problem. If you have problems like that, you should train people in massive form. The strategy is as follows: ALL personnel must attend a general course (3 hours aprox length) but they get out with a manual that exemplifies all that simple problems. If you do that, when you receive a trivial request your response could be as simple as "Follow the steps showed in page 20 to solve that problem"
by dcox
Whenever necessary, document communications with problematic users via email and use the receive and read receipt feature. This will show you did follow up.
In addition, since the person is claiming they informed you when they did not; I would suggest sending out an email to the user with bcc to your boss stating that you heard from other users (don't mention names!) that they (the problem child) is experiencing problems and they never informed you. Then proceed to ask for details of the problems experienced.
Do this enough times and they will stop.
by jupiter9
I have twice seen a suggestion to send a copy of an email discussion to a third party as a BCC. I think this is a bad idea.
Yes, company email belongs to the company. Technically an email you get from the complainer and your reply are perfectly okay to share with your boss. But if it is okay to share it, why do you want to hide the fact that you're sharing it?
How much would you trust someone who did this to other people? How would you know they wouldn't do it to you, too? I had a co-worker who made a habit of replying defensively to people who complained about him (or even asked him for help) and putting the names of everyone he could think of in the BCC line. This only made him look bad.
By using CC instead, and explicitly letting the other parties know there is someone else included in the discussion, a professional attitude is encouraged. It's tempting to try to trick people into "revealing themselves," but trickery breeds trickery, distrust breeds distrust.
by kurt.saenz
Although it causes more work for others and your self, you may find the old Cover Your Ass With Paper approach to work. It will not point fingers at anyone. Since her supervisor has done nothing, this will give you ammunition for you to then go to HR. If it is possible require that any problems be reported via email, fax, or hand delivered to you (date stamp with them and have them sign it). Have them outline the problem, the time, date, how to contact them, etc.
Then if the complaints continue about your performance you have the performance documentation proof that you need to protect yourself. This person is causing a hazardous and hostile working environment for you--file a complaint. It will then be up to your HR and her supervisor to deal with her.
by tammy
Corrielein,
I have found in my experience that if your customers are happy with your work and their experience from their time with you, the bad mouther is nothing more than making a bad reputation for herself. Happy customers will listen but give no merrit to the bad mouther. I would not worry much about her, but one way to stop this if it really bothers you, is to "befriend" her sort of say. Call her once a day and be real nice and just say you are checking to see if she is haveing any trouble or anything not working the way it should. This will give her nothing to talk about. Also, I hope you are tracking all your calls and finished work orders, this way you cover your back incase it ever goes up to mgt. I know it will be a strain on you being the only tech. person, it will take time you just don't have to waste, but it will work. Feel free to e-mail me if you want more ideas.
by mjsanner
The easiest way to prevent this is by creating a web based trouble ticket system. I was having similar problems. Once I set it up and informed all users on a weekely basis where to go to create a trouble ticket, the tide changed. The user still kept complaining, but as I pointed out They never used the system. So i created a way to track my "work product" and was able to CYA at the same time...
I know it sucks to have to CYA but as we all know IT can be a thankless job and some users are so unhappy at their job they will resort to tactics like this to mask the real reason for their poor job performance!
by georgemair
by not again
I agree with the folks who recommended logging calls/emails/verbals re issues. My experience suggests that any record should include the following:
1.Sequential ticket number.
2.Description of issue.
3.Who reported it.
4.Time and date of report.
5.Cause of issue and corrective action taken.
6.Time and date of resolution.
7.User sign off for acceptance of resolution.
Keep these records and archive them to non-perishable media. Not only does this system keep things from dropping through the cracks, it also gives you ammunition at review time and for those "What have you done for us lately?" discussions. If you need another body the records can add substantial weight to your arguments.
by lou
If you are being 'falsely accused' of not providing proactive customer support, you should look at Reflectent Edgesight. We enable you to understand the end user's perspective of IT.
by crake
or a plug in the middle of a discussion thread.
Very bush-league.
by realgem
Well, you could break her computer so badly that you will *have* to fix it. Then, you'll look like a hero(ine).
Seriously, though, your choices are to lump it or take action. The first step is always to approach the individual. This is the hardest thing to do, but you HAVE to do this first.
If what you say is true, then this is workplace harassment. If you have a company policy addressing this, follow the policy. If not, notify the manager *in writing* that this is still happening and that you wish to report harassment. That will more than likely be enough to get the manager moving because he/she becomes liable when they're made aware of the problem. Maybe that incentive will do the job.
Keep in mind that, if all this fails (i.e. the company you work for does not support it's employees), you can either quit or go tit for tat and bad mouth her right back.
by waynewill
I would log every call you get for support, no matter how small or large the problem. In reporting, include the location or department information, problem, resolution and of course who placed the call(The more information the better.) This will protect you from those that state you are not doing your job, and you can provide a report to each department stating how many calls they have made for support, or even post the report at that location on the wall.
If you can log a great amount of calls to a department you can then justify a training class to cover common problems.
by -loanman
Someone who would lie about calling every day would probably also accuse you of deleting records from a database, or of never entering the records in the first place (not that it's ever happened to me, he said through gritted teeth).
I initiated a new policy of sending a confirmation e-mail with a sequential ticket ID for each help request received. Make sure the users know about it and don't let them off the phone until they have received their e-mail (unless it is an e-mail problem, of course). Encourage them to save the e-mails "for auditing purposes" (most users with any sense are afraid to delete anything related to auditing). Then, when they come up with these outrageous claims, ask the user to produce the e-mail confirmation so you can "verify the ticket ID." You will also have, in your Sent Items, all the tickets you actually sent out, numbered sequentially so any gaps (or lack thereof) will be readily apparent.
At our company, as we grew we have had to automated this; we built a a home-grown help-desk application that allows users to enter their own requests via a web page. It generates a sequential ticket ID, creates a record in the SQL database, and sends the user a confirmation e-mail. All IT workstations have a client app that pops up a message when a new ticket is entered. Due to the sequential nature of the ticket ID generation, any record deletion is immediately apparent by the gap in the sequence. Also, because we use SQL 2000, we have a log of any record deletions; there is also the e-mail trail.
Technology is on your side; use it. Don't let these bozos get the best of you.
by saggums
Keep in mind that Windows 2000, XP, etc., have tools built in that can be "turned on" to log problems. These in turn can be saved or printed to provide "proof" of her claims that the computer is misbehaving.
Another nice tool that I have very helpful (in XP) is at Programs - Accessories - System Tools - System Information
by dseeger
by johna_smith
by donw
by salamander
...but a governmental one. I wish it was an academic setting. Judging by the number of posts, Corrielein's experience seems nearly universal.
Thanks for your kind comment.
by service
by beninsyd
Hi
I believe that most I.T. people in our position face this situation in one form or another - it is often a fear of appearing to be inadequate in one area of their role - so they shift the blame etc. I have overcome some of these situations by using Group Policies to lock down systems and present users with a uniform environment and conditions. Then, if one person complains of 'issues' that are unexplainable, I move the person to another system and see if the 'problem' follows them. Of course, if it does then it is highly unlikely to be a workstation issue.
Also, we have created a helpdesk/log via Outlook that is the ONLY way that we respond to questions and issues - this ensures that all issues are logged and reportable etc.
by bigwazza
I was wondering if there were any specifics. Taking the computer away shows you're serious in a number of ways. I get users complaining about their computers at times. If I offer to take the computer away, with no replacement, they reconsider carefully. If I offer a replacement, they know it adds to the total support time as I've got to move and set up the replacement for them.
Here's what one technician/support person did for a person complaining her monitor stopped working (for the "umpteenth" time)...
After replacing the monitor he left a note to that effect and walked away. He stayed within visual contact of the workstation until the person returned. When she did, she put her pot plant back on top of the monitor and watered it to overflowing. Problem solved, and no more new monitors.
Not the same problem with you, but I suggest next time you're off-site, the extra time subtly watching her work habits could be well worth it. If there is a mysterious problem, you materialise out of the blue and fix it. If not, escalate the problem as high in the company as you can.
A little bit of training each time you see her could also help - people have often complained about equipment when all they really want is a bit of training.
by cheyra
by gsancataldo
by sysadmintech
Hi Corrielein !
Just want to let you know that I once was in your situation. The best way to handle this type of situation is to approach the end user as I did in a friendly way and confront them about the rumors.
In addition you should create a rule with all your end users and have them send you an email describing their issue. Once you resolve their problem or problems reply to the user with the same email that was sent to you by them with high importance, stating the problem has been fixed and the call will be closed.
Best to have some kind of documentation to cover your ass. Better safe than sorry.
It seems to me that she is spending most of her time doing nothing and she's trying to find someone to blame.
Another way to put a stop to this conieving little liar is by swaping out her PC with a spare."if you have a spare"
Good Luck !
by butterpot
by tundraroamer
Plan to talk to your supervisor with the information and that you will resolve it. This is to protect yourself in case of attack by her supervisor.
Act by cutting of her login access. This will force her to contact you directly.
Now you can be sure she has called and can take this time to discuss the current problem and any others she may have. Resolve them (if true)and reconnect the login.
Pass the information along to your supervisor that all the problems have been resolved.
In the future, if the problem starts up again, have your supervisor contact hers and resolve it from that side and not yours.
by pammms
Don't you just love people who follow the correct avenues to get something done?
Get your boss to approve a new procedure. Make people fill out a form and sign them. Make the form easy...like...what's your tech problem today? I used to work in such an environment and I had to create a form that asked questions such as: is the computer on? is the printer ON?
If staff has to fill out a form, it seems they feel more important and that their problem is important to you...make them explain everything and then visit them with the answer...Many people are still intimidated by pc's even copiers and fax machines....if this person were in my company I would visit them with a donut and a coffee and sit down to have a little tete a tete...but I am one to tackle things head on....
good luck let us know what you ended up doing
Pam lindsay, previously IT manager at Burton Public Library in Ohio......my email is pammms@yahoo.com
by judy62
by betelguese
by ptorr
If you don't already have a Helpdesk Ticket Tracking Software and Policies approved by Management requiring that all Computer Systems Issues be either called in or emailed in and Logged and Tracked manually or by software which Tags and Numbers each and every Incident. Every user whom reports a IT Incident will be issued an Incident Resolution Ticket Number. Also, I suggest that you have good and constructive conversation with your Human Resource Manager about the individual whom is making all inflamatory comments ( Lies ) about the type of service that you provide and demand that she have real proof of her claims ( Put Up or Shut Up )!!!! Also, document everything that has occurred to present with date, times, names and exact statements made to whom etc...
Good Luck and Hang Tough !!!!
PT
by buschman_007
In life that's the way to handle your issues, but in a professional environment that sort of situation, especially when you're already upset, can easily get out of hand and go in a direction you did not intend. I would probably let YOUR boss know about the situation. Because frankly he's the one you should be worried about. Then you should bcc him on every interaction you have with that person. That way, if and when she complains and her manager brings the issue up in the next management meeting, your boss can slam dunk the issue in front of the complainers boss and her bosses boss. That's an effective way of smoking the rat out. Everyone in that meeting will now know who the troublemaker is.
A confrontation can make you look bad and give further credit to the assertion the complainer is making.
If you don't have a supportive management structure then you might have to resort to a very level headed confrontation. I'd consider that a last resort.
JMHO,
Mike
by gometrics
by jrockwell
Hi Corrielein,
I used to have the same problem. What I have done is as soon as I hear that their is a problem or any IT requests that I receive I send a reply email stating what the problem is that I have either heard or have been requested and listing what I am going to do about fixing it. I send this to the person who has the so called problem plus CC and sometimes BCC it to their manager. If the manager won't pay attention I will CC or BCC it to the Managers manager. I then send a follow-up email stating if the problem was fixed, when, where, how and CC that also. If the problem wasn't there or couldn't be fixed for some reason I email that too. Whatever happens or if I hear any whinging I email a reply. I keep a copy of all my sent emails. If you get pulled in to get your butt kicked because of the whinger, all you have to do is lay a printed copy of all the sent emails on the desk of the person trying to kick your butt. Then sit back and watch who's butt gets kicked.
by elwoos
by schetty
I am an administrator at a large educational institution, and the scenario depicted here is very prevalent.
Quarterly meetings with users are held and various gripes that were never reported are brought up and the administrators are bad mouthed.
I have on every occassion engaged the persons who have brought up gripes and issues, and in 90% of the cases have found that users complain due to the lack of proper knowledge of the product they use or operate.
I have also incorporated engaging the users by writing to them and requesting that they reply to any issues that they raised in the interests of a better experience in using technology.
Not only do I have documented proff but statistics to show management of areas that need addressing with regards tp training and motivation for hardware software replacements or upgrades.
by starat300
by riptaurus
IF you are the only IT person in the company and top management doesn't make sure that your word comes first, you need to find a better job. It is bad enough trying to do that job as it is without knowing that even the people you work for won't back you up. Listen close - there are better jobs out there for us - your life is too short to work hard and be spat on for it.
Ron (P.S. I am 61. I programmed computers for 36 years and as a consultant for many of those years. I have been in situations like you are but I never stuck around if I wasn't being supported by top management.
Good Luck
by aamontalto
May I suggest that you introduce a "formal" Fault/Incident Reporting Form/Log that users get to fill in and send over to you. I have lived through problems of a similar type you are experiencing (users are the same everywhere: they also resort to the same tactics) and frivolous claims disappeared soon after such a formal reporting structure was introduced. No one can claim that you never attended to a problem you were not informed about (the presence or absence of such a report quickly resolves such issues)! Moreover there is a plus side: you can actually work out statistics as to problems by OS/applications/hardware/users; no of problems by day, week and so on. NUMBER OF PROBLEMS BY USER (some report a lot others hardly any).
Keep the incident reporting log SHORT and UNCOMPLICATED so that you cannot be accused of creating a form which is to "intimidating" to fill in.
Good Luck.
by sunburst01
I was hired as director for a very large dairy company who did not have a networked environment. So, I set up a full network, got rid of the wyse terminals and gave all the workers PC's, removed the DSL and installed a T-1, etc. The secretary for the owner of this company was real excited and gave me kudos for every change I made,....until 1 day.
I set up a data cluster and the log file got corrupt, which wasn't such a disaster due to the fact that I only had 4 people at that time logged onto the domain, unfortunatley she was one of them. Well, the owner was there that afternoon asking his secretary to retrieve a photo that she had on her computer, which I moved all the documents for the 4 users to the server. Because the log got corrupt that morning, the system was a little slow retrieving the documents. She never called me to ask for help, all she did was tell the owner that "All my stuff isn't here anymore, it was all moved on me. This new network is so slow...etc." So, after slamming me to the owner, now he starts walking around saying how stupid the network is, etc. She, still doesn't say anything to me letting me know what happened, I find out a week later from the General manager who says to me, " I hear you made an enemy." Not sure what he meant, I asked him to explain, and he repeated the story to me. So, I went upstairs to talk to the secretary, who, by the way had such an attitude when I walked in the room, and asked her why she didn't call me. She freaked and started with this system is so slow, I can't get anything and kept going. So I said, let me look at what is happening. As I started to look at her screen, she said, "and I can't get on the internet either!". Ok...I look at the taskbar, the lan is disconnected, so I go behind the computer and notice the lan line is out. I asked her why...she said, and I quote "that plug was never in my system before, so I took it out". Hence, the missing internet. Then I look at her desktop. The icons I put there for her are gone, (now, this was before I set up policys and she needed to be able to install programs by herself on her system), the links to the data for some of the software are gone...I asked what happened to them. She deleted them. She couldn't see the wallpaper of her daughter so she deleted all the icons. IT was a mess.
After the cleanup...and a few weeks later I was ready to throw some more users on the domain, and I start hearing, "I don't want to go on the domain, yvette (oops, did I say her name)says its slow." I freaked, and told them in order to use the company software, they had to go on the domain.
A year later, everyone is now part of a company wide network, loving every second of it, except for yvette. Who still calls me in her office because she can't figure out what is wrong with her computer. I tell her all the time its an ID10T error, and to be careful, for it can spread to other systems so its better off that shes not on the domain.
by rohmranch
by equintieri
My team uses a Call Tracking system, which logs every call and its pertinent information. It also provides a history of the users call. When we have a Dynamic use, my team and I take special care to note everything in the worklog and follow-up with emails and phone calls. These are all noted within the CTS.
When there is a compliant, I review the history and send the user a brief summary. I may also follow-up with a personal visit. My team and I will extend every courtesy to the user, even if they are rude. Why? Because we are in the SERVICE INDUSTRY. If you do not realize this then you may need to rethink your calling.
One last thing is, most dynamic users will realize their failings once you show them the facts. If they do not, then you supervisor will understand that the issue is not with you. Some user you will never win over. With them, you need to be very professional and pleasant and document, document, document??
by -loanman
You are not alone;
Some Users who can not meet there deadlines or operate the equipment or become frustrated with there equipment they have been issued with, always use there IT technical support as the scape goats for there own lack of expertise. They don?t want to look stupid so they refuse to be placed on any form of remedial IT training. Unfortunately their line Managers will back them up because most of them, can just about cope with there own It skills and don?t want to loose face with the workforce,and when they can not manage will blame equipment for there lack of production.
All we can do is support them and take the flack,could I suggest something we do and that is keep a record of repeat complaints, this does give you some ammunition to fight back when your dragged in front of your IT manager, we have used it to great effect and have shown time of call and the problems, and who had them so there is no comebacks when the persons say they have had no IT support.
Keep up the good Fight
Malcolm
by aikimark
1. get one of her co-workers to pass her commplaints to you. You then show up to investigate the problem for which she hasn't called for help.
2a. start collecting a list of PC problems within their department. Check the list daily.
2b. post a suggestion and complaint list on the wall of their department for anonymous complaints.
3. create a reward system for prompt complaint submission, whether the complaint is for their PC or someone else's PC. This might set up a competition between the complainer and her co-workers.
4. enlist the help of your mananager to cut across the management layers of the two departments.
5. (SWAP OFF) let one of your co-workers handle her problems. See if the PC complaints move to the new person or cease. If they cease, then it is an interpersonal problem. At least the complaints won't be a hinderance to your performance reviews.
6a. install a (silent) performance monitor on her PC. Record all activity.
6b. tell her that you have installed a stealth performance monitor on her PC so that you can keep an eye on her 'problems'. stress that you aren't paying any attention to her keystrokes (but say it in the manner that leaves her some doubt).
7. find out if she is complaining through the company email system and have those complaints copied to you, your manager, and her manager. You can respond to her problems without a direct complaint from her.
8. break her system and replace it with one known to have no problems.
9. be sure to lock down her system, so that she can't do any damage with her login ID.
10. break her system on a regular basis and see if she complains to you. You know what's wrong, so you should be able to fix the problem quickly. This might establish your credentials with the complainer. If she doesn't complain, you know something is really wrong and can address this with her manager.
by mlayton
by zectim69
"First, I set up a simple database to log and track issue reporting"
Having some sort of Case Logging System, like you've mentioned, can really help in a situatuion like this. Our IT Dept. was always getting bad mouthed and blamed for things we had nothing to do with. People never follow procedure at our institution even though we constantly remind them and show them. Yet they always say we do nothing. Logging every Case and instance has helped shut those people's mouths because we have logs to back it up. We made our system through VB 6.0 and use the Visual Foxpro database. If you are thinking about writing such a program though I would recommend using an Access Database because I ran into so much trouble with Foxpro when I actually was creating a Case Logging Application for college.
by grandpa4
by rcom
My first question is why are people telling you this? Are they truely concerned or just back-stabing trouble makers. More than likely the person complaining really didn't intend for this to get back to you, so the person(s) that told you betrayed that person. No doubt if you've said anything in response they ran back and blabbed that.
In my opinion if someone doesn't bring it to me or my boss who gives a sh-- what's being said. If you're doing your job and no one else is complaining why worry about one user.
It's probably too late in this situation but a better way to handle this is to stop by from time to time and check on the user and spend a bit of time answering questions or pretending to fix something. If you go by and fix something call for a couple of days to check and see how things are going.
See what type of results you get. Don't get pulled into the age old trap of he-said, she-said.
by dcpnsmi
I have tried to get the users I support to write things down. I find that it is easier to trouble-shoot when the problem is in writing.
It would also help document requests and your responses.
by kenkrause
I had this problem also. My solution was to create a very simple html form to be filled out by the user with the user name, problem description etc. This form would be emailed to an account I had setup, and monitored 24/7 by a computer running Outlook express. It then forwarded a copy of the message to the appropriate tech, based on message subject, and sent a reply to the sender stating that their report had been received. I then used Windows Active Directory to place a shortcut to this form on all users' desktops. Followed that up by creating a company policy that absolutely NO problems would be attended to without this form being submitted. I didn't care if the user told me about it in the hallway or on break or wherever. No form, No resolution. That seemed to do the trick.
This goes back to documentation, documentation, documentation! Not only that, but the email server retains logs of all messages sent (or NOT sent, in some cases) which can be used to prove or disprove false claims.
Ken Krause
IT Manager
Dealer Marketing Services, Inc.
by gjtpike
Hi Corrielein -
you're in an interesting position.
Here's a couple of ideas:
~ if you're tracking your users concerns, start a monthly newsletter that identifies the issue, who reported it and how / when it was resolved. This puts you in a better light and will make everyone ever that your chronic complainer is just that.
~ if you're not tracking, start!
~ if you're comfortable with a face to face conversation, talk to the user - start out by saying something like "Could you please help me to understand this situation? From what I'm hearing, you feel as though you're not supported and I want to fix that!"
Please let me know how you make out!
~Jayne
Sort by Trending