On TechRepublic: Beware of crazy recruiter tricks
BNET Business Network:
BNET
TechRepublic
ZDNet
TalkBack 8 of 20:
Next »
« Previous
"If it breaks, can I fix it?"
So what's the other option? Run a system until it has run itself into the ground and can no longer be fixed? A smart CIO doesn't let the institutional knowledge go out the door with the staff.

I've seen more IT projects fail because the IT staff was afraid of being made irrelevant due to an upgrade. Will a COBOL programmer three years from retirement really get actively involved in upgrading a system knowing that the successful completion of the project will put his career in jeopardy so late in the game, even if it's in the company's best interest? Of course not!

So why should a company keep an "if it ain't broke, don't fix it" attitude? All that leads to is needless dependency on people being overpaid simply because their skill set is rare. Additionally, the company probably won't hire two COBOL programmers, so when this person gets sick, or gets hit by a bus, the company is screwed.

On top of all that, when you wait too long to upgrade systems, the upgrade path is either convoluted (e.g., upgrading through multiple software versions), or it simply can't be accomplished at all. In other words, the longer you wait, the harder and more expensive the upgrade will be. Every system will become obsolete, and "it ain't broke" is just not a compelling reason, because all that really means is "it ain't broke yet."
Posted by: dkawalec   Posted on: 08/22/08  (Edited: 08/22/2008 @ 02:03) You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

Progress? By definition...  techboy_z | 08/21/08
But prove the ROI  Feldon | 08/21/08
Change is not progress  larwe | 08/22/08
No...but...  techboy_z | 08/22/08
"If it ain't broke, don't fix it."  Anton Philidor | 08/22/08
I beat it like this...  techboy_z | 08/22/08
"... some initial cost to rebuild a system..."  Anton Philidor | 08/22/08
"If it breaks, can I fix it?"  dkawalec | 08/22/08
RE: Top five issues your IT staff wants to address but is afraid to tell you  JoeCotton | 08/21/08
There is no history of the code  JoeCotton | 08/21/08
History is needed...  MV_z | 08/22/08
You will need them.  Dealing | 08/21/08
RE: Top five issues your IT staff wants to address but is afraid to tell yo  neimon | 08/22/08
And the top answer is: your short-sightedness is killing you (and us)  terry flores | 08/22/08
Where's the reference?  IMHOYAAAH | 08/22/08
6. We want you to be able to hear and deal with the cold, harsh truth  dkawalec | 08/22/08
Move your #6 to #1  ws3d | 08/26/08
totally wrong  cwhull | 08/24/08
RE: Top five issues your IT staff wants to address but is afraid to tell you  imakethingsgo | 08/26/08
Indeed.  magallanes | 08/26/08

What do you think?

SponsoredWhite Papers, Webcasts, and Downloads

advertisement
advertisement
Click Here

Enterprise Applications

  • Check out some of the easiest and most powerful ways to boost productivity while saving money on your application infrastructure. See ZDNet's comprehensive Enterprise Application resource center, now!
  • New Online Dashboard
  • Read about top issues IT decision-makers face every day, plus get cost effective solutions to real life IT problems. Oracle Topline