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.
There is no one cloud solution to rule them all..
OK so here it is, one thing I have observed for a good while now is how much noise there is about how -you- should be in the cloud (Public) and if you are not you’re already dead.
I call Bull****!
Public, Hybrid and Private clouds are solutions not final destinations, regardless of whether you are a customer, partner, or any other third thing you should be purely focused on what is best for you or (if you provide IT services) your customer. It is plainly obvious to me that in -all- of the customers I have visited there has been no appetite or reason to mass adopt any single one solution/option as it simply would not fit how they do business and function day to day. There will of course be exceptions to this rule but they are indeed exceptions not the norm.
As I have heard in the past, the reason you don’t hear lot’s about Private cloud success stories is because they are Private (the clue is in the name) not every customer wants to shout about it for reasons and lets not forget the speed of business is in no way on a par with the speed of IT innovation.
It is reckless to blindly suggest to folk that only one type of cloud will meet all their needs. Public cloud is here to stay but the sweeping statements about it being the final destination for everyone is nonsense. All three cloud types are here to stay, they give customers choice (which is critical).
From my point of view, it is my professional duty to provide my customers with informed and appropriate solutions for their needs. For many I know this is plainly obvious but with all the noise at present I felt I needed to at least write something about my thoughts on the matter.
Again feel free to comment if you wish I am keen to hear what you think.
When everyones an Architect.. no one is..
I think this is the first time I have written a “rant” post (for a while at least) so if you don’t want to hear me whine run away now!
In the past 12 months I think I have met more folk with Architect in their job title than I truly believe is valid. Now I will be clear this is not a slight on the individuals all of them have been exceptional (at least the ones I have had the pleasure to work with).
An architect is a person who plans, designs, and oversees..
However what I feel is happening is a devaluation of the job title/meaning. While I understand many people pursue that job role/title as an end goal for their current career plan imo it’s getting quite ridiculous how many now seem to exist.
Too many chiefs (in title) not enough indians?
Maybe I am off base, what do you think?