Apply today for a FREE subscription to CIO Magazine!
Thu, Oct 2, 2008 11:35 EDT
|
Posted by: Meridith Levinson in Questions Topic: Personal ManagementBlog: Career Connection
Current Rating: |
When you're more qualified for a new job than the individuals with whom you're going to be working, your mere presence can threaten them--so much that they conspire to make your life miserable, and ultimately, to get you fired. That's precisely what happened to a software engineer, whom we'll call John Doe, this summer. (John didn't want to use his real name in this story because he's pursuing legal action against his former employer.) Here, John explains how he was unfairly targeted at work and shares the lessons he learned from the experience. (Note that certain details have been changed to protect John's identity.)
John Doe had been working for a manufacturing company as a contractor when he was offered a full-time software development/project management job with the company in Spring 2007. When the hiring manager offered John the full-time job, she told him that two other developers he'd be working with opposed John's hire. She told John that they didn't tell her why they didn't want her to hire him, just that they didn't want her to do so.
John says this information sounded alarm bells in his mind, but he took the full-time job with the company anyway because he needed the work and because he was excited about the project he was being hired to work on. It was a big, strategic initiative for the company with lots of visibility, and it touched virtually every function inside the company. John says that the hiring manager also reassured him that he would never have to work under these two individuals.
After John was hired full-time, John says the two software engineers who opposed his hire were made managers. Though John did not report directly to either of them, he had to work with them. "That's when life started going downhill," he says.
John says the two managers conspired to set him up to fail. He says they wanted the project he got and were threatened by his knowledge and expertise because it made them look unqualified. John says the two managers gave him contradictory verbal and written instructions. They would tell John not to do something, only to later ask him why he didn't do what they told him not to do (they implied that he should have done it.) They gave him unreasonable deadlines. They told him to ask them for help, but when he did, they always replied that they were too busy to help him. They also complained to John's manager (the woman who hired him) that he was not doing his job properly and that he spent too much time chatting with co-workers. John couldn't get a break.
Early in 2008, one of the developers who opposed John's hire was put in charge of the project John was working on.
"I was supposed to be the project manager," says John, "but he, for all intents and purposes, was made the project manager. The guy I was told I'd never have to work for was suddenly in charge of the project I was spearheading, and I was told that I would be answering to him."
Though John was wary of having to report to someone who was making his life miserable, he wasn't overly concerned about his job at the time. He thought it was safe because he was the only person in the company with the unique skills the project required and because his boss
This story is so similar to what happened to me, its scary.
I was hired on as a contractor by a hiring manager who was very supportive. The manager repeatedly noted that this project was ideal for my skillsets, both technically and managerially, and so put me in charge of a major component of this global project.
However, the day I started, I was told that two existing contractors who had been competing for my lead role were not only going to remain on the project but were also going to report to me. The business leaders had preferred the existing consultants, while the hiring manager wanted me to head up the project, so this was their compromise. I also learned that an in-house manager had just been given a very similar project for a major division, creating immediate overlap issues in our responsibilities. And finally, a few days later, the division business head gave me specific instructions for the project that were counter to my hiring manager's directives. I brought all these concerns to the hiring manager at the close of my first week, and was told, "we'll have to play it by ear". Like your article, I decided to try and please all parties and "soldier on". Big mistake.
My scenario progressed almost identically to your article, with project and timeline changes, no assistance, conflicting information, finger pointing, etc., and to a very similar conclusion. In the end, politics trumped best practices. I've learned, like your article, to keep track of conversations (formally, by creating "meeting minutes" for distribution, and informally by writing down comments made pro & con), and copies of emails and documents. As a consultant, all I can hope to use these for is to protect my reputation if necessary (and make sure I get paid for the time and work completed). But, I strongly recommend that employees in similar adversarial situations take these defensive actions seriously.
It is nice to see that I am not alone in such times as 'being setup.' Good article. Thank you. I am concerned about how one can move on from such a setting up and firing. How and what does one say at his next contract position when asked what happened in your previous position?
Good questions. Thanks for them. I will seek answers to them from experts and report back.
I think such clashes usually take place in Matrix organisations. You could either have one person sponsoring projects (and therefore having the last say) and another anguished team trying to complete it (which would but naturally have two parts - the doers and the recognition gainers). I work in such a place where all glory gets stolen by the sponsor and any problems promptly dumped on me! Things once went on so bad that a sponsor who doesn't even know the difference between a Router and a Repeater started complaining to the Directors about my competency. Thankfully, I had an extremely supportive boss who put his foot down in my favor. I'm living in a time of truce .. but I might not be lucky the next time around!! There's really nothing much that can be done in such cases, specially after project delivery - even if you happen to encrypt your hard disk or keep copies of communications. Someone has to take the axe .. you just have to be watchful it doesn't fall on you. If it does .. sayonara :) - no one said life's fair!!
In my situation I am not sure if I am being setup for dismissal or if my manager just try to make life as close to hell as possible, but it is exactly for the same reasons as mentioned before, i.e. Management feeling threatened.
I was entertaining the thought of looking for some other job, but now I am convinced to start my search much more vigorously. Thanks.