Why do IT projects struggle or fail?
I am sure if you ask that question to ten people you will get 10 different answers, or at the very least a wide variety of reasons. The product chosen to deliver the solution was a poor match, the product was implemented incorrectly, the PM sucked, the Vendor gave no support, insufficient training material/resources, poor interoperability, the list goes on and on.
One issue I have observed from time to time on my travels is quite different from the above listed examples. In fact, (and this is my personal observation and opinion) the real issue can be hidden under the reasons listed above.
So, what am I talking about? I am referring to human nature, self-preservation, fear of the known or unknown, preference for another solution/vendor, I think you get my point.
I have seen many projects where it is quite clear the product was not miss-sold, was a good fit, where the support and implementation was solid, the PM was on point and so on. Yet the project limped along for “reasons”, where all the problems, issues or objections that cropped up were simply individuals finding anything that would help justify or protect their position or opinion.
How do you keep -your- IT skills relevant without burn out?
I was having a chat with my Dad recently, about how those who work in IT keep their skills up to date. He is now retired but had spent 25+ years in the IT business so I always value his opinion. What occurred to me while we chewed the fat was the following.
<cliche quote>If there is one thing we can be sure of in IT, it is that change will happen and faster than we think.</cliche quote>
But seriously, how the heck can we keep up? I mean seriously every few months the next new “big thing” hits the ground in the shape of a new method, new tech or even a new tech start up. Regardless of what it is if you are even slightly serious about your IT career you have to pay attention and at the very least be aware of what it does, how it does it and what impact it has or will have.