IT Crises vs. Vacation: Sometimes It Isn't Pretty
CWmike writes "It's true that IT systems have become essential to business operations, but the successful functioning of the IT department shouldn't rest on any one person's shoulders. All told, vacations serve as mini tests to prove if a department can function when key players are away. That's the theory, anyway. In reality, IT departments sometimes flunk. The results can either be comical or turn out to be a serious wake-up call to organizations that need a better Plan B. To prime your mental pump before your own vacation, Computerworld compiled anecdotes about good vacations gone bad."
at least in the states is, companies have figured out they can get one person to do the work of two and pocket the other guy's salary. I'm seeing this everywhere in the form of longer wait times for services. It's also really screwing the economy because it means there's 1 less job available, so higher unemployment and less money circulating. We're heading back to the 1800s, when our masters argued that idle hands were the devil's playthings, and the lower class would just spend the time drinking anyway... Kiss your vacations (and your 40 hour work week) goodbye.
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
When I leave ... then I turn off my pager...
So I'm guessing the last time you left was sometime in the 90's?
*ducks*
If what I just said sounded like a troll, it was probably just a failed attempt at humor.
I'm personally aware thru my late father, who was an accountant, of two companies that had employees embezzling funds for years. One telltale sign was that they never took vacations, because their replacements would have discovered what they were up to. Businesses should insist that their personnel take time off, just to make malfeasance easier to detect.
The flip side to being "one deep" is you are more valuable. I would lean towards hoarding knowledge and being on-call. I don't WANT my employer to be comfortable functioning without me.
Business is a team sport and you are definitely NOT being a team player. I have fired people for doing exactly what you are suggesting. It doesn't make you more valuable, it makes you a liability. You are putting the organization at risk for your own gain. If you make everything dependent on you and then you get hit by the proverbial bus, your selfishness has endangered everyone who depends on you. Single point of failure is a bad thing and information hoarding makes you a single point of failure. If the people you work for tolerate that kind of behavior from you, they are extremely foolish.
I off and on contracted for a place where this was hugely important.
What they'd do is come up with some bullshit reason they were giving a bunch of people 2 or 3 extra weeks of vacation but it must be taken within a short time frame (that quarter or the next two quarters), usually times to align with the summer already planned vacations, and sometimes not entirely bullshit.
Either way, if you were gone for about 3 weeks, and no one really needed you for that time off, your job was going to be axed shortly. Maternity leave? No problem, your job will definitely be here when you get back because we'll try not to fill it at all, and if we don't need it, you're gone as soon as we're legally allowed when you get back.
It's slimy, but it's business.
Fault tolerance is a serious problem. If you only have two people who know a system, both of whom work in the same area, and both get the same infectious disease for a week you have a problem. On the other hand, having 3 or 4 people with redundant skills is a waste of money. I can see the appeal of cloudsourcing to a 3rd party in that regard.
On a personal basis, if you don't have something you, and only you can do until the day you retire you're taking serious risk. That doesn't have to be technical of course, you can be the only one who knows how to deal with the crazy redhead secretary in another department who bothers you all the time, or you could be the only one who knows how stuff in storage is laid out or whatever. It's a tricky balance between 'manpower intensive to replace' and 'crippling the company if you get hit by a bus'.