Slashdot Mirror
Ask Slashdot: Best Practices For Leaving an IT Admin Position?
An anonymous reader writes "I've been the server admin at a university for the past five years. Recently, I was given the chance to move from servers to networking, and I jumped at it. I now find myself typing up all my open-ended projects, removing certain scripts and stopping others. What would the community recommend as best practices for passing on administration of some servers? I am trying to avoid a phone call that results in me having to remote in, explain something, jog to the other side of campus to access the machine, etc. Essentially, I'm trying to cover all my bases so any excuse my replacement has to call me is seen as nothing but laziness or incompetence. I am required to give him a day of training to show him where everything is on the servers (web and database), and during that day I'm going to have him change all the passwords. But aside from locking myself out and knowing what is where, what else should I be doing?"
Build an internal Wiki. You won't be free from questions since you can 't cover everything in a one day training session. I'd make that two half days with a month or so in between.
Be fair of course in how you word it, but nothing speaks better than "I showed the new Admin X,Y,Z and he knows how to do X,Y,Z; here the signature to prove it". I know you are trying to avoid a new Admin coming in and then complaining about how the previous guy didn't know what the hell he was doing. Happens to everyone I'm afraid, but at least have your bases covered for what any replacement needs to know to operate in your permanent absence. It will also discourage the new admin from making any drama scenes with his/her new boss when he/she knows you have something in writing that is suppose to demonstrate/validate his/her new skills in the position. Other than that, don't burn any bridges, try to be helpful to the new Admin, when you have the free time, but don't go out your way and sacrifice your new job to help a struggling admin who might be in over his head due to fluffing up the resume.
That seems like an awfully small window to brain-dump all the info the new guy will need. I think you'll find yourself doing an "oh, yeah, I forgot to tell you about this" thing for awhile. Trying to make the guy look lazy or incompetent for not knowing everything after 1 whole day of info-sharing sounds mean-spirited.
Wow -- seriously? I'VE been doing IT for FAR longer than 5 years, and the attitude you're displaying right now I'd notice and either not hire you or fire your ass.
I'll be the first to agree if you end up with some incompetent boob, you want that on him and not you ending up doing two jobs, but if you had any maturity or experience, you'd recognize it _might_ take longer than 1 day to do a full knowledge transfer (in fact, if it only takes 1 day, frankly, you shouldn't have had a full time job.. you must have had a lot of downtime to post on Facebook). I'd do my best to document everything in a wiki, show him the ropes his first day, and provide him with my contact information. If a month later he was still bothering me for minutiae, we'd have words -- if three months later he was calling me for an emergency, I'd handle it and then handle him. But 1 day and gone? Either your 'sysadmin' position was 'sit on ass all day' or you need to realign your expectations. What would you want to happen if it was you coming in blind?
Basically the same as "screw your mortgage and family moron, you are fired".
Let the bank deal with all the trash you left behind and how to clean it up before they try and resell the place.
Oh, you weren't talking about being foreclosure. On second thought, my first thought stands.
Honestly, what's wrong with the new admin coming to you with questions, as long as s/he doesn't abuse the relationship? You'll find that in moving to networking, you're probably going to be doing some work with he new admin anyway, just not directly. Might as well maintain a healthy relationship.
Yep.
If you really are that important, have them contract the work to you.
And to siblings, it's not about saying screw you guys - it's a job, it's not your life, they will dump you the second you are redundant.
Stay in touch with your workmates if you liked them enough, but the second you are off the clock, it's someone elses problem.
Essentially, I'm trying to cover all my bases so any excuse my replacement has to call me is seen as nothing but laziness or incompetence.
Do you hate the guy? Sure people can be time wasters, but you wouldn't be blowing off a user, but an admin who's hands you might need at some time in the future.
I now find myself typing up all my open-ended projects, removing certain scripts and stopping others.
What's with all the last minute changes? Clearly it's not a 'best practice' to change anything just before you hand it over, as some issues can take days, weeks, or months to become noticed, if they can be traced back you your last minute 'unwarranted' changes, you'll be at the other end of those 'incompetence charges'.
The force that blew the Big Bang continues to accelerate.
That tactic is too common, and leaves people thinking you're an idiot because they get no chance to find out _why_ you did things certain ways. This role is in the same university: you do _not_ want to leave enemies behind in your old workgroup. Unless some other political issue is driving you out, plan a much longer hand-off period. Unless there's other staff that can fill him in on common practices after beginning, you should schedule time every day, then every week, then occasional emails to touch base. Have lunch with him and a notebook occasionally in the first month. Just be careful not to become a crutch.
The server admins and the networking group should remain on friendly terms: you're going to need favors from each other in the future, and keeping things helpful will help the server team grant those favors gracefully. It'll also let them know that when you say yes, it's as a colleague who wants everything to work, and when you say no, it's not personal.
Hats off. These days it's rather difficult to find reasonable, competent and professional people in the field; therefore I won't pass this occasion for a well deserved praise.
Definitely good advice, there would be so much more unnecessary stress and emotion if this attitude was more widespread.
Mi domando chi à il mandante di tutte le cazzate che faccio - Altan
If the guy who replaces you needs a hand, give him a god damned hand!
If you've failed to adequately document your role in the time you've been there, you're the one who is lazy and incompetent - it is in your best interests to convince your replacement not to point this out to your old boss, who might point it out to your new boss.
Get your management to buy into you sharing your time between networking and systems for perhaps two or three weeks (you decide based on volume and complexity of what needs to be handed over) and spend as much time as needed to (a) evaluate the skills of the new 'guy' and (b) get them up to speed on whatever they need to know. If you don't do it in the beginning you'll be doing it for months.
During this 'handover' period, track questions, answers, issues and concerns in one document that you and the new admin review at least once a week (again I don't know the scale of your environment). If any questions come up later and you've documented the entire handover period this way you're covered.
blindly antisocialist = antisocial
It sounds like you are taking most of the right steps already. Writing up projects, one last round of cleaning. . .
The rest really depends on how big of a job you are handing over. If you were a full time admin, then a single day of training is probably not going to be sufficient. If it was a part time position, then perhaps one day is sufficient. That said, I still wouldn't assume that the new guy is incompetent if he has questions after the first day.
I'd suggest that you tell the guy up front: You are moving to a new job and you won't have a lot of time to answer questions, but you don't want him to feel like you screwed him over. Do your day of training, offer to field emails for a week or two (you'll reply within 24 hours) then schedule an additional session for two weeks later. You should scale this to the size of the job you are handing over: perhaps an hour phone conference for small stuff, up to another day of training if you are handing over a full time position. At that point, he or she can ask any further questions and you can call it quits.
This buys you a bit of goodwill from both the new guy and your old boss. (Going to be wanting a reference from him someday? Show that you care and want things to go well, even after you leave.) Besides, odds are that the new guy is even moderately competent, he won't email you after the 3rd day, and will cancel your 2 week phone call. Plus, if he really is incompetent and starts seriously leaning on your expertise, you should call your old boss and tell him that the new guy has issues - that's probably more valuable than a slip of paper with a (now-known) incompetent's signature.
Best of luck.
Lets start refering to The War Against Terror by it's initials. . .
Wait for the first phone call.
Grab flash gun, keep it hidden.
Disappear behind server rack, muttering "I'm so lucky Health and Safety never came back here...."
Discharge flash gun.
Scream, swear loudly, and wave hand as if burnt.
Wait for "It's OK, we've got this."
Relax.
OK. Lemme try on:
You installed a bunch of open source software all over the place, removing Windows, Unix, and or Novell. (Probably Windows.) Your documentation is, admittedly, less than complete. You, admittedly, have scripts running here and there, which are also likely less than documented. You also are doing a job that should take a month, bringing a new admin up to speed on your (literally) custom built network, in a day.
And your primary concern is (and I quote):
I'm trying to cover all my bases so any excuse my replacement has to call me is seen as nothing but laziness or incompetence.
If I was your boss, I'd fire you and might consider bringing you up on charges of interfering with government property. What, is your name Terry Childers? Probably not. He at least was trying to do a good job. You're just the sort of tool that gives Linux users and computer guys in general a bad name.
The best practice for leaving an IT position? You should start by improving your attitude.
Hoist Number One and Number Six.
I'm sorry dave, but the CEO really wants another Yacht and we cant afford to keep you. Yes we know that you do 12 jobs and are critical to our operation, but we are going to hire some kid right out of college for $28,900 and save a shitload of money and abuse the snot nosed brat by making him work 120 hours a week with only 40 hours of pay. You are just too old for us to screw like that anymore.
Do not look at laser with remaining good eye.
It's unrealistic to expect everything to just work smoothly under a new person after 5 years working (I presume) mostly by yourself. It's not laziness or incompetence for the FNG to consult the person who architected the system when the documentation inevitably falls short. Grow up, be a professional, and help the new guy out.
If you're not replaceable then you're not promotable. I *want* people to be able to do what I do so that I have the option of doing something else.
Those are my principles, and if you don't like them... well, I have others.
Groucho Marx