{"id":4332,"date":"2010-06-08T11:52:12","date_gmt":"2010-06-08T18:52:12","guid":{"rendered":"https:\/\/svapm.org\/?p=4332"},"modified":"2010-06-14T09:03:06","modified_gmt":"2010-06-14T16:03:06","slug":"myth-1-if-it-aint-broke-dont-fix-it","status":"publish","type":"post","link":"https:\/\/svapm.org\/?p=4332","title":{"rendered":"Myth #1: If it ain’t broke don’t fix it!"},"content":{"rendered":"

\u00a0\"\"<\/a><\/p>\n

Say what?<\/p>\n

I can’t tell you how many times I hear this, and it bugs me to no end. Colin Powell once said, ” ‘If it ain’t broke, don’t fix it’ is the slogan of the complacent, the arrogant or the scared. It’s an excuse for inaction, a call to non-arms”.\u00a0 Alright, so the context for his quote was completely different but let’s not go there. I gotta say I agree with the man in principle. It’s a phrase sometimes thrown around to temporarily sweep something under the rug, or to remain in denial that what’s working now will continue to work indefinitely.\u00a0So wrong (IMHO)!<\/p>\n

If we’d have been happy with walking from A to B, we wouldn’t be biking, driving or flying today. Innovation doesn’t come from standing still and accepting status quo. It comes from having a different perspective on something, from wanting to look beyond the current offering, and\u00a0from thinking the impossible and going for it!<\/p>\n

Okay, let’s apply this in the day-to-day tactical sense. I have seen entire company vision documents and roadmaps drawn up\u00a0just on the premise that\u00a0just\u00a0the current infrastructure will support any additions, extensions, fixes and\/or advancements that are being considered. Must we wait for something to break before it gets our attention?And must we necessarily reject advancements or improvements just because we don’t want to rock the boat with something that’s currently working? It’s\u00a0a fairly short-sighted approach, I say.<\/p>\n

The questions we really need to be asking are:<\/p>\n