Slashdot Mirror
Getting Rid of Staff With High Access?
HikingStick writes "I've been in the tech field for over 15 years. After more than nine years with the same company, I've been asked to step in and establish an IT department for a regional manufacturing firm. I approached my company early, providing four weeks notice (including a week of pre-scheduled [and pre-approved] vacation time). I have a number of projects to complete, and had planned to document some of the obscure bits of knowledge I've gleaned over the past nine years for the benefit of my peers, so I figured that would give me plenty of time. That was on a Friday. The following Monday, word came down from above that all of my privileged access was to be removed — immediately. So, here I sit, stripped of power with weeks ahead of me. From discussions with my peers in other companies, I know that cutting off high-privilege users is common, but usually in conjunction with a severance offer (to keep their hands off the network during those final weeks, especially if there is any ill-will). Should I argue for restored access, highlight the fact that I am currently a human paperweight, request a severance package, or simply become the most prolific Slashdot poster over the next few weeks? Does your company have a policy/process for dealing with high-privilege users who give notice? What is it, and do you make exceptions?"
Your situation kinda sucks as it sounds like you are a diligent worker who wants to help the company. But as long as they are paying you, it's really their choice how they want to use your services. All you can do is when your co-workers ask for your help in passing the torch, mention that you are hand-cuffed by the lack of access and have them request it for you.
P.S. Some activities to pass the time would include Watching Grass Grow and/or Watching Paint Dry.
Hulk SMASH Celiac Disease
a delightful term I learned from my UK counterparts. Essentially you're still under employ by the current company so cannot do work for your new one or any competition, and you relax at home while getting paid. It's like paid vacation, except not, since you could theoretically be called in to work at any point.
AKA. request to work from home if your access is revoked, since you can't do anything at that location now anyway.
It doesn't mean much now, it's built for the future.
It seems to be common now for companies' to strip users of all their privileges ASAP. If you think this was bad, be glad you're not be laid-off. I've often many people tell me that they learned they no longer had a job when their sessions were terminated in the middle of the work day.
Welcome to the work-world of the 21st century.
Steven
http://www.practical-tech.com/
http://blogs.computerworld.com/sjvn
Rumor has it that step 4 has something to do with becoming a highly-paid consultant for the old company.
Have you ever had nothing to do at work for that long? I can handle surfing the Internet at work for maybe a week. After that, the boredom is excruciating. Believe me, being completely ignored by your company can sometimes be almost as bad as other things.
Really, you aren't.
You should spend the next 3 weeks documenting your projects. That is what the company needs from you. So few companies get this, want you coding until the last minute.
What happens when your stuff breaks? The next folks start at your documentation and go from there. Internal wiki's are great for this.
That would be the ethical thing to do. At this stage you don't need the high access as your replacement has the access. I would work closely with your replacement explaining things to them that may not be nessarly documented, even if they are documented people most likely don't want to read it. So use the time to give your replacement the upper hand. There is a lot you can do without having root/administrator access.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Good time to pick up a new skill/programming language or refresh your knowledge, etc.
Don't blame me, I voted for Kodos