Slashdot Mirror


Dealing With an IT Bully

jammag writes "'"You are an idiot." That was how I was greeted on an already gloomy, rainy Monday morning.' Eric Spiegel offer his a first-hand account of dealing with a tech world geek-gone-bad and presents some ideas for coping. 'These bullies are quick to aggressively divert blame for any problem back to someone else, because they couldn't possibly be responsible. Some are passive aggressive, where they will subtly lay blame behind your back. Others enjoy getting in your face and being as confrontational as possible.'" What experiences have others had that defied all logic and possibly made you want to start looking for rifles and bell towers?

2 of 521 comments (clear)

  1. Geek-gone-bad? More like Geek-becomes-PHB by KiltedKnight · · Score: 5, Interesting
    The author did right to leave. He wasn't going to get anywhere as long as the CIO and the development management weren't going to cooperate. However, after this fiasco, I would've considered writing up a new policy and trying to get it through the CIO... one that says, "No training or documentation? No upgrade." There is no other way to deal with this situation, unless you want to escalate above the CIO... but if you do that, you need to have documentation in order to show that the other people and those you skipped around are incompetents and are the cause of the problem. Even if you do have all of your ducks in order, be ready to look for a new job as well.

    I've been lucky enough to not have had these kinds of situations... but then again, I've also been on-call when my software upgrades have gone in AND had a good working relationship with the operations staff. When the few problems happened, they were able to call and get a quick and friendly resolution to the problem without all the name-calling. Almost like we had a system in place........

    --
    OCO is Loco
  2. My Own Experience by happyslayer · · Score: 5, Interesting

    I had an experience in one of my jobs, and it was with a co-worker/subordinate:

    So here it was, me as the head of the IT department for a Navy command, and the only military officer in the shop; everyone else was a civilian contractor.

    After a couple of years, I was feeling very comfortable: Things were getting done, 90% of the users were happy, and I could answer most questions and problems within 30 minutes of the subject coming up, if not right away.

    Then things started going down hill. People were getting frustrated, required maintenance wasn't being done, and the head contractor had screwed up and corrupted the entire mail system (had to spend a whole weekend getting it back.)

    As time went on, things got worse, and I could never figure out how or why. I started getting acid reflux, couldn't sleep, and was wondering why it all seemed to go to hell.

    It all came to a head when, after a particularly thorough chewing out by an unhappy user, one of the techs came and told me that the managing contractor (she of the corrupt email) had been going around behind my back telling everyone how screwed up I was and how everything was going to hell because I didn't know my ass from a hole in the ground.

    (To be fair, she was under a lot of pressure; the company she was working for was planning on firing/"downsizing" to save money, and our 5 person shop was seen as a potential target. Unfortunately, she decided to push her own importance by cutting down me. Definitely passive-aggressive.)

    Anyways, after checking out the sordid tale (just to make sure what I was being told was true), I went home, had a beer, talked to my wife, and then called my boss: Since you can fire the contractor, fire me. I explained that this conflict was hurting the command, and

    • a) She (the managing contractor) was right and I didn't deserve to run the IT department, or
    • b) She was wrong, and I didn't deserve to be treated this way.

    Either way, I wasn't going to take this crap any more. (And yes, I did try to talk to the higher-ups about this, but all they could do was shrug and say "Sorry, we can't get rid of her.")

    Boy, within 30 seconds of getting to work the next morning, everyone had heard about it! At least to me, most people were supportive, and said, "About time!" By mid-morning, the manager in question asked to talk to me privately, and started crying about humiliating this was. She also mentioned that she could get fired if this got back to corporate. All I said was that I couldn't help it; we couldn't seem to work together, and gave my reasons above.

    Well, to make a long story short (I know...too late), the Wing commander called me in, chewed me out for not working out this problem myself (and probably rightfully so...), and then said to get my a$$ back to the job because no one else can do it. I said, "Aye-aye, sir!" and went back to work.

    Things got better in the shop for a good while; I volunteered for a 6-month duty during the war, and when I got back, it didn't matter because I was getting out very soon.

    Moral of the story: I don't know--you tell me if it makes any sense.

    --
    Never confuse movement with action. --Hemingway