Getting Rid of Staff With High Access? 730
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?"
It's really the company's decision (Score:5, Insightful)
P.S. Some activities to pass the time would include Watching Grass Grow [watching-grass-grow.com] and/or Watching Paint Dry. [watching-paint-dry.com]
Re:It's really the company's decision (Score:5, Insightful)
What the organization really needs is some time to find out what sorts of things break when you aren't around to poke at them. For the next month they have the benefit of your knowledge, should they need it, but you won't be able to do stuff. This will allow existing staff members to learn to cover gaps while you are still around in case of an emergency.
You are leaving. The company is far less interested in what you can do for them in your last few weeks than they are in learning how to live without you. That basically requires that they cut you out of the loop as soon as possible.
Re:It's really the company's decision (Score:5, Interesting)
that pairing allows you to cover and discuss what you where doing and what needs to be picked up.
instead of spending your last weeks finishing your job you spend the last weeks as a source of information as someone else is trained to cover your job.
so far it has worked really well for us
Re:It's really the company's decision (Score:4, Interesting)
And there is no need to say that I should have done better documenting this along the way. I did what I could, I even added time into my project estimates to allow me to do just that but when a company is hell bent on making as much money as possible and not care at all what kind of quality it pushes out the door it does not always happen.
The peer I left behind is a good friend of mine and in the months after I left he would email me from time to time asking for hints on the "little problems". I helped where I could but I was limited to memory alone, no more looking at my little notes, hints or tips and tricks stuff in the code.
Re:It's really the company's decision (Score:5, Interesting)
YOu give your notice...you get to work normally till your last day.
The only thing I can think of is that they know if you do anything stupid...it is a major federal offense..and that that would be a deterrent?
But seriously, some of these systems have MUCH more valuable and sensitive info on them....and the people leaving don't get treated like shit, like many of the posters here allude to...
Re:It's really the company's decision (Score:5, Interesting)
Layne
Re:It's really the company's decision (Score:4, Insightful)
Re:It's really the company's decision (Score:4, Insightful)
LOL..what gave you that idea that you were scrutinzed so carefully?
Basically, you gotta be a US citizen....and be at the right time at the right place...I've seen it before. Most contractors are just trying to fill seats with bodies to get billing. I've often seen those that were barely competent get in....but, it is mostly about bodies in seats at many, many sites.
Re:It's really the company's decision (Score:5, Informative)
Pretty much all security clearance jobs will run a credit check, background check, etc.
Many jobs will send send investigators to past acquaintances, friends, neighbors, colleges, etc.
The point being, there is a HUGE degree of variation, even to get the same ultimate security clearance. You can immediately get an interim secret clearance just by filling out a form. top secret, etc takes longer and is more rigorous.
Re:Well SOX compliance and auditors are forcing ma (Score:4, Informative)
In any big project, there's always more documentation that can be written, and more details to pass on.
If you've got an employee that can turn over all their knowledge in two or three days, you've been hiring the wrong people.
One answer to your earlier question about "why weren't you passing/sharing knowledge the whole time you were there before?" It's not always about hoarding knowledge - often, there's simply nobody to turn it over to. In a busy environment, it's difficult to find time to sit down and train someone in a system they're unlikely to use. Those other employees all have their own projects to get done, too. Documentation and cross-training, while good to have, often slip in priority compared to getting the newest patch out.
As a contractor, I tend not to have this problem as much. Since I know from the beginning that I won't be there long, I can be meticulous in my documentation and training, planning from the beginning to get my work ready to turn over to someone else. Most regular employees, though, usually don't have that luxury.
Re:Well SOX compliance and auditors are forcing ma (Score:4, Insightful)
And for those thinking to flag troll - i've seen this actually happen numerous times. Besides, if you miss a deadline because of someone who's no longer around it's pretty easy to blame them eh?
Re:It's really the company's decision (Score:5, Interesting)
Also, the first time anyone had heard that the company might let people go instead of letting them serve out their two weeks was when our supervisor (who was extremely well liked) gave his two weeks, was given a box and escorted to the door in a very humiliating manner. The company then claimed that it was standing policy in spite of the fact that multiple people of all levels had served out their two weeks. Morale tanked and it was awful for productivity.
Re:It's really the company's decision (Score:5, Funny)
Waste others' time the way they are wasting yours. Request frequent meetings with superiors to go over your daily reports. Hold very frequent meetings with random groups of underlings to discuss strange topics. For example, you could have an 8:15 meeting with the receptionist, an entry-level programmer, and a sock puppet regarding the situation in Myanmar, followed by a 9:00 meeting with the same entry-level programmer, a different sock puppet, and the janitor regarding your detailed synopsis of the new Indiana Jones movie.
Make loud phone calls about your internal organs. Bring cake every day and insist that it's someone's birthday. Mix cat food in with Chex Mix and leave a bowl of it in the break room - see how much is gone at the end of the day. Etc.
Just because you aren't allowed to do any work doesn't mean you have to be bored or watch grass grow to pass the time.
Re:It's really the company's decision (Score:5, Funny)
Re: (Score:3, Interesting)
Re:It's really the company's decision (Score:5, Funny)
Re:It's really the company's decision (Score:5, Funny)
Re:It's really the company's decision (Score:5, Funny)
Re:It's really the company's decision (Score:5, Insightful)
Re:It's really the company's decision (Score:5, Informative)
Re:It's really the company's decision (Score:4, Informative)
If you're asked for a reference for someone and you trash them (however well deserved), it opens your company up to a lawsuit from the person who you were asked about.
If you're asked for a reference for someone and you sing their praises, the other company can sue your company should the employee do poorly in the new job.
That's why many places have policies about the kind of references their employees are allowed to give. I know of one bank that limits the allowable references to "yes, person x worked here from date y to date z." Beyond that, it is corporate policy to say nothing.
Re:It's really the company's decision (Score:5, Insightful)
Re:It's really the company's decision (Score:4, Funny)
Re:It's really the company's decision (Score:4, Funny)
Joanna: You're just not gonna go?
Peter Gibbons: Yeah.
Joanna: Won't you get fired?
Peter Gibbons: I don't know, but I really don't like it, and, uh, I'm not gonna go.
Joanna: So you're gonna quit?
Peter Gibbons: Nuh-uh. Not really. Uh⦠I'm just gonna stop going.
Re:It's really the company's decision (Score:5, Funny)
So he didn't do anything, not even touching the keyboard.
But it didn't work. At the end, he became too bored, and decided to quit himself..
Re:It's really the company's decision (Score:5, Funny)
Re:It's really the company's decision (Score:5, Interesting)
Your example is exactly why giving notice is not something you really do anymore. I got further screwed. I was nice like you and did all that, then HR came back with a letter, "All vacation is canceled" you cant take vacation after you give notice, you also forfeit all vacation and sick time accrued.
So I sat there and watched TV the last 2 weeks in my office. I was going to document all I knew, I decided that I was not going to as they wanted to be jerks about me being a good guy.
I still get calls from people there about systems that I was the only expert on. I reply with, "what is your PO number for this consulting call? I would love to help you but management and HR told me point blank that everything has to be done by the book."
So they hired another firm to help them, that firm contracts me out as the consultant. It pisses off the upper managers.
Re:It's really the company's decision (Score:5, Interesting)
When I was laid off from a previous job-- they cut off my server access immediately. Though it wasn't necessary in my case, it certainly makes sense as a basic policy when letting someone go.
EXCEPT for the fact that they didn't bother to check for running processes first. Completely unaware of the fact that I was about to be laid off, I had kicked of an elaborate SQL script on the live server just before my boss called me into his office. They killed my account with this script still running-- oops. A friend of mine who was still at the company said that the resulting zombie crashed the main Oracle server, requiring a reboot, three days after I left.
So the "safe" choice of immediately removing access caused a major crash, while the "dangerous" choice of not removing access would have caused no problem whatsoever. (I'd say something about irony, but I don't want to kick off a debate on the word's meaning and whether it applies...)
Re: (Score:3, Informative)
Re:It's really the company's decision (Score:5, Interesting)
I had a similar story; I got canned, and the second I left the building they started reformatting my equipment to make sure I hadn't left any time bombs. Due to server problem, I'd been using my desktop for development, and I had a huge code package sitting there waiting to be deployed (They fired me because I'd completed it).
So they ended up wiping out the code. Woops. The icing on the cake was that they changed all my passwords, and revoked all my access, but they didn't check for running sessions, so I got home and I was still remotely rooted in a pair of live servers. I changed the MOTD on all the machines I was still logged into to: "When terminating an employee, make sure to abort active sessions before you change the passwords." Then logged off.
I'm sure that sent them into a frenzy of paranoia, but frankly, they were acting like idiots. They went out of business in 3 or 4 months, and the guy who fired me spent a year or so after that trying to get me to do contract work for him.
Re:It's really the company's decision (Score:4, Informative)
GP was not being childish; he was not throwing a tantrum; he didn't even know he was about to be laid off. He started a long-running script, presumably a perfectly normal part of his job, but one which would need some shepherding. Then his permission to do that shepherding was revoked, so he was unable to do it. So he didn't do it. So the company reaped the benefits of their own folly. There was nothing the GP could have done to affect the situation, and no blame can reasonably adhere to him.
So get off your high horse, buddy. Somebody with as low a UID as you ought to know better.
Re:It's really the company's decision (Score:5, Insightful)
Also, It's nice to leave without burning bridges. Who knows, maybe some of the people you leave behind may remember you in a positive light later in your career and provide an opportunity?
Re:It's really the company's decision (Score:5, Insightful)
This advice is bang-on. It may be a boring two weeks, but c'est la vie. Whatever you do, don't rock any boats or burn any bridges. What goes around, comes around.
Re:It's really the company's decision (Score:5, Insightful)
And if you tell me that you need a paycheck to pay the mortgage, electric bill, or whatever, you aren't being fiscally responsible having no safety buffer. If you think that it doesn't matter unless something goes wrong, well, your life sucks more that it needs to because you aren't taking the vacation.
Re:It's really the company's decision (Score:5, Insightful)
Back pain (Score:5, Funny)
Nice to know (Score:5, Funny)
Thanks for the heads up!
Comment removed (Score:5, Interesting)
Re:Nice to know (Score:5, Informative)
Re:Nice to know (Score:4, Informative)
Don't know in this case, but I wouldn't be surprised if it were law.
Europe in general has much more law around that governs employee-employer relation than the U.S.
Take a look at French Labor Law for example http://en.wikipedia.org/wiki/New_Employment_Contract [wikipedia.org] or German Labor Law http://www.germanlawjournal.com/article.php?id=594 [germanlawjournal.com]
Re:Nice to know (Score:4, Interesting)
*laugh* That's nothing. One of our tech writers gave his notice two months ago, and has been working on tying up loose ends since.
I've never actually seen anyone give that much notice.
But, yes, giving advance notice and having them lock you out doesn't sound so bad. I've known instances in my company where someone gives notice and gets told "OK, you're on paid leave until you are done" because they don't want people who are leaving poking around in systems.
I guess to some employers, once you say you're leaving, you're persona non grata. If they don't want to use your time any more, it's their dime.
Cheers
Re:Nice to know (Score:5, Interesting)
I was laid off from one large company once and they provided two months of paid time off. Once they notified me they cut off access. Their take was that my new job was to find another job. The kicker was that if you found another job during that time period then you did not get the payoff package at the end of the two months. Kind of funny, I found a new job just after the check cleared. They setup the rules, we just play by them.
I also had a situation a long time ago where a contractor that worked for me decided he was going to relocate for a new job. He gave two weeks notice. I checked his projects he had which were done and told him that he was no longer needed. I did not have any make work that justified me paying him for another two weeks. Such is the life of a contractor.
And don't forget the main rule here, no one is irreplaceable. No one! Not even you. (Yes, I even mean you there in the back with four digit
Re:Nice to know (Score:4, Interesting)
I personally know someone that cost a large company what likely turned out to be a few million dollars when she left. She quit because she couldn't schedule vacation time without working her butt off for 2 weeks preparing things in advance, and then returning buried for 2 months playing catchup because nobody was willing to let her train anyone else (in the WORLD) to do what she did, which was quite a few obscure yet important things. (imagine a 40+ story building that occupies a city block, and 4+ floors of that building can't do their jobs, (jobs where work snowballs when not done) for several weeks, and ongoing impacts to parts of the building for the next 4 months) The result was a lot of heads rolled and several new policies were instituted after about 6 months of unbelievable chaos. "this will never be allowed to happen again" was heard by one of her coworkers as things wound down. At least it looks like they learned their lesson.
Given, that's an exception and not the rule, but it's fun to look at what can happen.
Re:Nice to know (Score:5, Insightful)
Re:Nice to know (Score:4, Insightful)
Keeping someone who will leave is sometimes good (Score:5, Interesting)
The one time I was laid off I was told it was effective in six weeks. I spent much of that time documenting and training coworkers on projects that I had worked solo on. My network access and other privileges were not affected. I asked the VP of engineering if I could take some of the source code home for reference so that I could answer questions over the phone or by email after I left. He drafted a letter stating that I was allowed to keep the source for this purpose only and that it remained company IP and could not be disclosed to anyone else. We both signed it.
This was about a 150 person company owned by a large international conglomerate. The VP was originally from the conglomerate's corporate headquarters and joined us two years earlier when we were acquired. The rest of management was local. I had been there about four years. A year after my layoff the situation at the company had improved and I was asked to return.
The moral of the story:
I don't deny that it is common to be immediately cutoff when you resign, but it is not a given.
Don't burn bridges.
It's a waste of money to pay someone who doesn't even want to be working for you. Obviously their output is going to be nill so their pay should be nill.
Myself and at least one other poster have demonstrated diligence training those who will be taking over. I think it is far more of an individual judgement call based on past projects and the individual level of trust.
If you are going to be involved in managing those family businesses I would suggest a less black and white perspective. Sorry, but management is not easy and such a black and white perspective often indicate the less capable managers or someone in an unforgiving bureaucratic/politicized environment who needs to cover their ass with policy compliance. That said, I agree that it many cases the proper decision is immediate cutoff, immediately issuing a final check, and wishing them well as you walk them out in a friendly manner. My point is merely that in some cases keeping them around for a little while can be beneficial to the company.
Re: (Score:3, Insightful)
Uh, aren't you always at the mercy of your employees? After all, if you could do it all yourself, why hire people?
You sound like a joy to work for.
Re: (Score:3, Informative)
Comment removed (Score:5, Funny)
Re:Are you crazy (Score:5, Insightful)
Re:Are you crazy (Score:5, Insightful)
Comment removed (Score:5, Informative)
Re:Are you crazy (Score:5, Interesting)
So, I spent 3 months or so picking my nose with little tiny things to do here or there. I was going nuts. I personally don't know how anyone can be at work for 8 hours a day, 5 days a week and just "browse the web". I set up a proxy server at home and use FoxyProxy so I could get to any site that was blocked (youtube, fark, but not
I brought in a USB HD with GB's of stuff on it, like... games. I still wanted to slam my face on a fork. Daily.
As a programmer I actually want and need to
So, during my many, many of hours of downtime, I just started looking for a new job on monster, etc. Then I would just leave without even needing to tell anyone, and go on interviews.
Found a new job. Now happy.
Though to be honest, with a state job, once you have about 1 year under you belt, it almost takes an amendment to the state constitution to get you fired. Which was nice from a security point-of-view. Though it also allowed a lot of under-skilled "programmers" to be permanent fixtures.
Re: (Score:3, Interesting)
Most likely, something like that will happen to you again - but it's usually temporarily. You're going to get a new job every time?
Then what're you going to do after retirement?
Re:Are you crazy (Score:5, Insightful)
I can't imagine something better than being paid to read Wikipedia and learn stuff all day long for months at a time. That's basically a MacArthur grant.
I'd learn Icelandic, finish my PIC data acquisition unit, re-learn synthetic organic chemistry, design and build a couple power supplies, actually learn electrical engineering rather than just pretending to know it, build a suit of chainmail, learn enough aerodynamics to design a new set of wings for a homebuilt plane... I could spend three years of 8 hour days online with ease, and love every second of it.
(I know this because after a car crash I spent about six weeks bedridden and that's exactly what I did the whole time, and it was *glorious*. I learned enough Japanese to have semi-intelligent conversations and taught myself Perl during that painful vacation.)
Re:Are you crazy (Score:4, Funny)
Re: (Score:3, Funny)
Re:Are you crazy (Score:5, Funny)
He's a Unix, you insensitive clod!
It's even surprising you must stay. (Score:5, Interesting)
In the early nineties, my dad was a high-privilege employee at a bank. Anyway, due to office politics, he pretty much got the boot because one of the higher ups didn't like him. (You know, how easy it is to fire someone if you really want). He had been working there for nearly 20 years, and according to local law he had 6 months notice. He was disallowed to go to the bank during those 6 months: from one day to another he sat at home.
I heard this is pretty much the rule with high-privilege employees. So, I'd suggest, sit back, enjoy yourself and troll on slashdot as if there were no tomorrow.
Re:It's even surprising you must stay. (Score:5, Interesting)
nope (Score:5, Funny)
Request "Gardening Leave" (Score:5, Insightful)
AKA. request to work from home if your access is revoked, since you can't do anything at that location now anyway.
Let me put it this way... (Score:5, Funny)
We look forward to hearing from you...frequently.
Access removal (Score:5, Insightful)
Any good admin/manager knows if you have physical access, you might as well have root/admininistrator access.
Comment removed (Score:4, Interesting)
Enjoy the break (Score:5, Informative)
For example, I worked on banking software and had god-rights. If I as a regular employee steal all of the customer data and sell it, then I am the criminal. If I have been terminated and do the same, then they are at fault. Now yes, I realize that it's a pedantic difference, but the banks which run the software see a world of difference and will sue the my employer accordingly.
Believe me, it's cheaper to pay me 6 months severance than it is to be sued for my actions.
Most are set out the door immediately (Score:5, Informative)
Re:Most are set out the door immediately (Score:5, Insightful)
On the other hand, those two weeks could be a really crucial time for the employee to document his knowledge and train others. Any company that won't take advantage of those two weeks is probably just being paranoid.
Nothing new here (Score:5, Insightful)
Welcome to the work-world of the 21st century.
Steven
http://www.practical-tech.com/ [practical-tech.com]
http://blogs.computerworld.com/sjvn [computerworld.com]
Re:Nothing new here (Score:5, Funny)
He tries to interrupt me with some lame explanation, but I'm having none of it. I pick up his stupid little "certificate of excellence" award he got at the last quarterly meeting and throw it against the wall, shattering it to pieces. He tries to call security, but I rip the phone out of his hand and continue to hurl abuse that would make the paint peel if he didn't keep the office at 60 goddamn degrees all the time, rendering it permanently encased in ice.
Finally, some of my fellow co-workers come in and ask what's going on. I tell them I've been laid off, and so they start in on the boss too. How could you do this to our best employee, who do you think you are, etc. By this time, my boss is in a corner in the fetal position weeping softly. My two co-workers quit on the spot in solidarity, and throw their laptops at my boss, who is knocked unconcious by one of them, while the other smashes into his new 24" wide-screen HD monitor.
At last, my co-workers head off to the bar to continue the rant about the injustice of it all, while I go back to my desk to put my "wall o' tech books" in a box. While, I'm there, I happen to notice the back of my computer. Turns out I had knocked the Ethernet cable out with my foot.
Oops.
Re:Nothing new here (Score:5, Insightful)
No, welcome to the work-world of the U.S. (circa 1990-200?). Much of the world hasn't adopted these draconian and dehumanizing disemployment procedures. They rely on human decency during severance just as U.S. companies once did.
The common practice of frog walking terminated employees to the nearest exit results in far more long term damage than the hypothetical "disgruntled employee on his/her way out" ever could. I suspect some of the HR managers came up with this process in order to meld the Japanese "work to death" management theories with the U.S. "T minus 0 seconds of job security." It doesn't work but it gives the HR wonks something to justify their own jobs. Think of it this way, when Joe employee has zero job security, every minute of every day becomes a "I may be on my way out" minute. What makes that employee any less likely to do the damage 30 seconds before the termination decision is made? This is what we have across the U.S. right now and people wonder why you can't get a clerk at the *mart, why you can't get good service anywhere and why corporations are infested with incompetent, selfish, opportunists [slashdot.org] who steal from customers and sabotage companies and co-workers in order to gain "job security." The team player is dead, it's every man for himself in corporate America.
The odd thing is that these same American multinational companies often do have sane and humane exit policies for their outsourced contractors and their overseas employees.
Re: (Score:3, Interesting)
Here's a plan: (Score:5, Insightful)
Rumor has it that step 4 has something to do with becoming a highly-paid consultant for the old company.
Take the high road (Score:5, Insightful)
Go on gardening leave. (Score:5, Insightful)
This is almost certainly not personal. Your senior management has obviously made a policy decision that the risks of leaving you with access to the systems are more important than the costs of locking you out. Obviously *you* know you are honest and safe, but they can't take that risk. If you think about the amount of damage you could have done if so inclined, you might see the point. There are quite a few horror stories about disaffected employees and computer systems.
Warcraft FTW (Score:5, Funny)
fuck it up for everyone else (Score:5, Funny)
Re: (Score:3, Interesting)
You're not supposed to finish your projects (Score:5, Insightful)
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.
Re: (Score:3, Interesting)
So aside from it being the moral thing to do, enlightened self-interest also suggests that you should always treat your employer well, odds are, you'll meet them again in a few years.
Start a Political Movement (Score:4, Funny)
Highlight unfair labor practices, working conditions, unsavory boss types, gender inequality in pay scales, and anything else that brings pain to people's lives. Gender inequality is a great one, because it exists almost everywhere. Distribute pamphlets, circulate emails, stick things up on whiteboard, announce your demands loudly.
If you can get 75% of the workers there to sign a petition to join a labor union the organization has to deal with the union by law. Offer people a cookie to sign the petition and you will hit that number. An affiliated union can get an organizer in there after you leave to keep things going.
Coders of the world unite!
M
It isn't neccesarily personal... (Score:4, Interesting)
Company B, which I left a couple months ago, let me work my entire 4 weeks notice with full access.
I don't know how big a firm your talking about here, but a lot of companies have a pretty firm HR policy on asset access for short timer employees. Before you get too upset, check into the policy and see if your being singled out or if that is just the way the organization works. It certainly sounds to me based on your snippet the latter is much more likely.
Sit back and relax... (Score:5, Interesting)
I spent those two weeks typing documentation on everything I did, and in training one of the junior admins to wrangle SMTP until they found a replacement. The only real benefit I got out of the deal was that I didn't have to carry a pager anymore.
The other benefit? The folks there were okay with me burning off paid sick days to arrange for the U-Haul and to tie up loose ends before the move.
Most companies that I've worked with in the past were similar - you only really lose access to the vital stuff, but there's usually plenty of non-vital stuff that still needs done until you bail.
Consult your replacement. (Score:5, Insightful)
It is unusual (Score:5, Interesting)
It does seem to me that there's little point in removing access and keeping an IT guy on. If they need to remove access they should just pay you for a month and let you go. The fact that they want you to stay and took away your access says a lot of negative things about them. They don't trust you, but they want to keep you to the bitter end anyway.
Knowledge transfer as much as you wish during this time. If I was being treated this way, it sure wouldn't make me want to seek people out to give knowledge to, but I would probably help anyone who came to me with questions. I do suggest to you that you not ask for your access back. If your company wants to be a jerk about this, let it be a complete inconvenience for them and play by those rules. A company that has already shown that they don't trust you is not going to look favorably on any requests you make for restored access. In fact, they might find it suspicious that you need the access and they might suspect you of planting trojans, etc. Just live with it. In fact, you probably should fight to not get the access back and here's why. If something goes wrong after you leave, your company has shown you that they don't trust you. They might blame you for whatever happens if you get your access restored.
Most companies do not act this way. I've worked in IT for almost 22 years now (since college) and we've either just sent people packing the same day (never for IT staff, but it has happened for sales people and such) or they got to keep their access until they left.
throwing the gauntlet, eh? (Score:3, Funny)
Good lord, man, do you know what you're doing? College just let out...
But if you're serious, I'm willing to take odds -- and willing to see if a challenge like that changes the character of slashdot during the event.
Now we just need sponsors and a catchy name, any suggestions out there?
see if you can work from home... (Score:5, Interesting)
if they won't do that, ask for severence and be on your merry way enjoying the time off.
I wasn't so lucky. I was 'fired' (new management didnt' understand my role as lead network security analyst, and even worse, feared my knowledge). But because of that fear, I got a severence package and most of the bonus I was promised for helping an outsourcing initiative (no, it wasn't me who was replaced through that). I was also able to collect unemployment. The downside is that I had to explain why I was fired in all of my interviews.
Your company does respect you (Score:4, Interesting)
Remove Time Bombs (Score:3, Funny)
If a company withdraws privileged access from personnel nearing termination, how are those people supposed to disarm all the time bombs they've installed in systems over the years?
But seriously: The last company I was laid off from never stripped me of any privileges. Upon termination, I was expected to (and did) return my secure token generator, so now I can't log in through their firewall any longer (this assumes that I'm not aware of any back doors). But, during my career, I had administrative responsibility for several servers. I had installed some simple monitoring programs on these systems in my personal accounts that would page me and e-mail me at work and home if problems were detected. Prior to leaving, I prepared instructions for my replacement which included changing the notification e-mail addresses. He never did so. That was in 2003. Occasionally, I still get status messages from these systems, indicating that my user accounts, including e-mail routing rules, are still active.
It depends (Score:4, Informative)
If not, I'd approach my boss, say "I understand that you want to protect all the data that I have access to. But, I hope to be able to serve this company in the time that I have left and without at least some of that access, I can't do that. Here are the things that I still have in progress: X, Y and Z. If you give me permission to do A, B and C, then I can complete these projects before I leave.
"Others might have given you much less notice, But out of loyalty, I wanted to give you ample time to find my replacement and handle the transition. Would you please consider reinstating the access I need to finish these projects? If you cannot, please tell me how I can serve this company until my departure."
They probably won't give you the access. But, this at least creates a positive impression in their minds. Pulling some of the other stunts suggested here doesn't.
Don't burn bridges, and transfer knowledge (Score:5, Interesting)
Don't take it personally. Especially if you are leaving a large company.
So.. what to do with your new free time? If you really want to not burn a bridge, spend the time documenting all the little ins and outs of the stuff you really think is important, or that you have had some nagging concerning about. Find out who will be picking up your tasks, introduce them to the folks that you interact with on a routine basis. If you have direct interaction with end users, let your replacement know which end users requires a little more attention, or have difficulty with things. Give your replacement(s) a little "tour" of the more obscure tasks that you do. All systems have little quirks, transfer those bits of knowledge. Any special configurations, unusual setups, etc.
Why would you want to do this. Because it's a professional way to respond. And it is possible that years later it might come back to you. As a personal antidote, when I left my first company (after 13 years), I didn't burn any bridges. They let me keep my system authorities, but what I did was to set up a new account for my replacement and with my replacement looking over my shoulder I started to remove my old accounts, just to make sure that things would still work. I worked closely with my replacement in "cleaning up" all the little hooks that my old admin accounts had and made sure that he had the same access that I did. A few years later in the new company, I was laid off as part of a large downsizing - several hundred people (everyone was literally given notice, told not to touch any system, make one phone call, grab your personal stuff and escorted out of the building - in a very unprofessional manner). My old manager from the original company contacted me and asked if I was part of the downsizing and let me know that "there is a desk here if you need it". (As a final note in this, about 6, 7 months after I was laid off, I received a call from the company that laid me off.. asking for my skills again.. my response was "hell hasn't frozen over yet") -- so the karma works both ways..
Fuck them. (Score:4, Informative)
Your play is to do whatever is in your own personal interest (which would include the interest of your family and friends, and perhaps innocent bystanders).
My take (Score:4, Informative)
OK, our policy falls in to two categories/buckets:
1 - your privs are removed and you are sent home with pay for the notice period, goodbye don't come in to work.
2- you keep all your privs and you continue to work, thanks for staying during the notice period.
Nothing else makes sense to us. Removing your privs and having you come in just creates a distraction while you talk to other staff, not useful to us.
As to whether you fall into bucket 1 or 2 is the result of conversations among management. Any doubt that you will play nice - goto bucket 1 immediately. Any doubt that you are really needed to complete work - goto bucket 1 immediately. If you both can and will contribute to the project and we do not expect any issues with you working during your notice (poaching employees, causing trouble, etc.) then go to bucket 2.
We have had people we assigned to bucket 1 that were great employees and I'd like to keep. They were not really needed for the project and we sent them home as sort of a last 'paid vacation' from us. No ill will, I'd hire them again. We've also sent people home and taken a hit on the project as the distraction, productivity, or trust factor outweighed the usefulness factor.
Removing your privileges and still having you come in makes absolutely no sense to me. Seems to be the worst of both worlds, you can't really be productive and the low work load can cause you to create distractions for other staff. I just do not get why they want to do that.
Hope that helps.
Re:Four weeks??? (Score:4, Interesting)
Once, however, it was a defensive move. My manager was maneuvering to fire me (not justified, but I was a resident alien and appealing would have been more or less impossible) so I resigned before he got the chance--and padded my stay to four weeks, until I had my affairs in order.
Re: (Score:3, Insightful)
Re:They are protecting their assets (Score:5, Insightful)
Anyone who is malicious and has half a working brain would, of course, do all of that evil stuff before giving any notice. Do they really think that all of their employees are malicious, incompetent, backstabbing morons ?
You could be trying to steal information or recruit your coworkers to your new job.
Yes, the free market is a cool thing, as long as it doesn't impact the bottom line. Then you should fight it tooth and claw. And you should hang on to moronic employees who can't look for better jobs themselves, but need to be recruited by a coworker. Geez. Some people in charge must really, really think that all of their employees are a bunch of dimwitted morons. Maybe they're right, too.
Re:They are protecting their assets (Score:4, Insightful)
because anyone competent in such things had them in place months ago.
He's leaving on good terms, he would not timebomb anything. Disgruntled employees? they had their timebombs in place for months. Best if you know that most of the backup tapes are also infected with it so they cant easily roll it back.
I know I have had to disarm may disgruntled timebombs left by people. The really clever guys had them there for a long time so it's a major bugger to get rid of them. One was part virus and replicated and replaced it's self afte a bit of random time (3-10 days later it pops back up.)
Re: (Score:3, Insightful)
My immediate response to this would be "They are the same person they were before they gave notice. If you believed they'd be so unprofessional, so untrustworthy, then why did you give them that access in the first place?". Simply giving notice isn't anything special or unusual. Everybody leaves their job. The head of HR will one day give his 2-weeks notice. Even the CEO of the company will one day leave for another position. The company itself isn't going to be shy about telling employees that outsourced c
Re: (Score:3, Insightful)
I brought in a large stack of books and my laptop, and began brushing up on skills that I needed in my new job but had become a bit rusty on.
Then there was the time I gave 2 weeks notice at a large bank (you've all heard of them). I was immediately escorted out the door, and 3 days later got a check in the mail for the 2 weeks I had offered notice for, plus
Re: (Score:3, Interesting)
You start with a knight on an empty chessboard and you need to write a simple algorithm to solve for a method where the knight can move over every square of the board only hitting each square once.
it a classic recursion interview question.
its even more relevant in my industry - embedded - where many of our uCs only have a stack depth of 31 so forces the interviewee to think creatively. any questions like "whats stack depth?" might send them straight out of the door....
its always a good pr