- Whether to mention a pregnancy in a job interview
- A possible meeting protocol
- What are an end-user's responsibilities?
- Another take on opening PCs, or not
- Getting some process going
- Selling a more open environment to management
- Running an effective meeting
- Licensing rules for virtual machines
- The ROI of metrics
- Legal challenges to virtual machines
October 01, 2007 | Comments: (0)
Involuntarily irreplaceable
Dear Bob ...
When I hear the broad statement: "If an employee is irreplaceable you should immediately fire that employee," (as cited in your recent article, "The causes of greatness," Keep the Joint Running, 9/10/2007) it hits a sore spot, since I am unfortunately in that category. I am not in that category by choice; instead my management (second line and up) has consistently sabotaged my ability to make myself replaceable.
The problem is that we use a very complex piece of software on which I was the lead developer. We inherited this from a prior company following a number of spin-offs, mergers and acquisitions, and I am the only original developer remaining. Over the years I have trained several people (a costly process) who have then either left the company du jour or been the victims of downsizing; I have also lobbied to remove this from our products, and although I have gotten agreements that this should be done, resources have never been allocated.
I am certainly not alone in this regard. Now changing the statement to "If an employee insists on being irreplaceable...." as the fault lies with the employee; however, if an employer forces the employee to be in that position, firing him or her would be to blame the victim.
- Call me Irreplaceable
Dear Irreplaceable ...
I certainly understand the sore spot. The question is whether there's anything else you can do about it, now that you've already used the most common tactics of training replacements and making your unique skill irrelevant.
If there's a third tactic to pursue, I'm unaware of it. That leaves becoming more persuasive with the company's decision-makers regarding the two that are available to you.
I don't know if you're willing to try a higher-risk approach (or if you already have). It's a modification of the what-if-I-was-hit-by-a-bus argument. It goes like this: "I need your help. Right now I'm in career jail, which means I have a strong financial and career incentive to find another opportunity in another company. I really don't want to do this - I like working here. What can we do so I can go on to my next opportunity here instead of someplace else?"
Anyone with any brains who hears this will recognize it for what it is - a veiled threat. On the other hand it's an honest statement of a real risk to the business, stated in businesslike terms, so it shouldn't offend a businesslike manager.
The risk to you, of course, is that not all managers are businesslike when the chips are down . You'll have to judge for yourself whether a conversation like this can work with the people you'll be dealing with.
- Bob
Powered by ScribeFire.
Posted by Bob Lewis on October 1, 2007 08:00 PM
RATE THIS ARTICLE:
-

- COMMENTS
As I stated in a previous post, the manager(s) who allow this situation to occur should be the personnel terminated. No one seems to notice this point. It does not matter whether the employee is purposely making themselves irreplaceable or management inaction/decisions are causing the situation. It is incompetent management that is to blame.
Posted by: Mark Robinson at October 3, 2007 11:05 AMThere's another way to make the "what if I get hit by a bus" argument hit home without the veiled threat. Drive the bus yourself. Say, "I'm considering having surgery that will require two months of medical leave. What do you think we ought to do about support during that time?" This ought to prompt some response in getting backup in place. Of course, it doesn't mean the person won't leave again...
Posted by: John Stork at October 3, 2007 11:15 AMI found myself in Irreplaceable's spot a decade ago and realized that the veiled threat you recommend would not work. So, instead of saying anything, I just waited until a juicy enough outside opportunity came up, then gave my two-week notice. I took about 3 months, but eventually the evening and weekend support phone calls stopped and my former underling has trained her future replacement. I'm still in regular social and friendly contact with my former coworkers.
Posted by: J at October 3, 2007 11:25 AMThere is a path out: Document the heck out of the software. Make sure the source is heavily documented internally. Label all the interfaces, data items, procedures/paragraphs/subroutines, etc. Write detailed documentation on what typically goes wrong, how to diagnose it, and how to fix it. Create scripts for compiling and testing the software. Produce diagrams and logic flows on how the software works and interfaces with the user and/or other systems. Create at least 5 times as many lines of documentation as there are lines of code. You mention that training someone new is expensive. Documentation doesn't eliminate the cost, but it can vastly reduce the cost. Now you can hand the software over to a young, new person and you can move on to other challenges.
Posted by: Mark P at October 17, 2007 01:01 PM|
Three books. Three ways to change the world, your life, or at least Bob Lewis' bank account. Leading IT: The Toughest Job in the World distills the world of IT leadership into eight learnable skills and gives you concrete, practical techniques for each one of them. Bare Bones Project Management: What you can't not do makes project management manageable, even for first-time project managers with no formal training in the discipline. ManagementSpeak: What managers say/What they mean … well, it won't help your career, and won't make you a better manager. Mostly, it will make you chuckle, guffaw, and maybe even chortle. Make friends - it's the perfect gift for anyone who has ever suffered through one of those meetings. Order your copies today! |
TOP STORIES
Top 10 stories of the weekA new place to hide rootkits
Sun exec on OpenSolaris, Linux
AT&T: No free iPhone Wi-Fi info
MS to appeal E.U. fine
XP SP3 causes endless reboots
Vista as insecure as Win 2000
Google grilled on human rights
Java ubiquity an edge in RIA battle
The InfoWorld news quiz
ADDITIONAL RESOURCES

- Virtualization: A Step by Step Approach to Success
- Dialing up Agility with Business Transformation
- 5 Things You Need to Know About Storage Virtualization

- Virtual Test Lab Automation: Manage development infrastructure
- Improve Resource Utilization and Lower Operating Costs
- Protect Your Data with SSL





