Top Ten List: Introduction to The Top Blockers to Deployment
Over the next ten working days, this blog will list what I have observed to be the top ten blockers to operating system deployments. My focus for the past sixteen years has been on the Microsoft Windows environment, so my Top Ten List is mainly for Windows. The list is also oriented more toward desktop deployments than to servers, although much of it applies to servers as well. It is aimed at larger enterprises that typically struggle through mass deployments and complain about how hard it is to keep up with the changes in technology.
Although does happen to be Windows focused, I believe what I highlight is likely to apply to any massive deployment, including Apple, Linux and Unix. And I’m already noticing nearly identical blockers when customers attempt to move into the Cloud–because ultimately, the Cloud is about continual, dynamic deployment of services, and nobody is going to get there from here without adjusting old habits.
I’m not saying I have answers to all these deployment blockers, although I will try to give some hopeful “Better Way” advice. But I have been out there for a long time, observing successes and failures, big and little. To me, what is on my list is just our human condition, that is, behavior that is uniquely human, habits which technology alone cannot resolve. Most people call it politics, but I think it goes way beyond that. There isn’t a customer that doesn’t suffer through these blockers—some more than others, but no one has been free and clear, at least in my experience.
Once the Top Ten countdown is complete I’ll dig in with future posts to give deeper details on what I’ve seen contractors, partners, and Microsoft Services do to resist and counter these blockers, what worked, what failed, and the reasons why.
Drum roll please. Let’s roll out Deployment Blocker No. 10.