Let’s get something out of the way really quick: if you implement cloud computing within your organization, something’s going to break.
No matter how good the technology or skilled the vendor, the fact of the matter is, at least one thing in your organization is going to be ripped apart when cloud computing of any kind is deployed. And the name of this doomed aspect of your organization?
Simply put, the barriers between your business units and your tech units.
Jake Gardner from LogicWorks makes this case eloquently in Wired this week, in his look at the “7 Sins of Cloud Computing.”
Gardner makes some great points, and leading the list is what he refers to as “Organizational Ignorance” – the belief that cloud computing, when implemented, won’t drastically effect the way an organization does business.
Some of this belief is based on lack of knowledge, and some of this ignorance is self-generating.
“With a lack of internal understanding, or even a reticence by internal staff to provide a comprehensive reasoning for cloud (for fear of losing their jobs), chief decision makers are often not working with all the facts that could provide them with best reasons for or against cloud implementation,” Gardner writes.
This is an excellent point, and one we’ve seen when working with customers to deploy our SUSE Cloud solution. Bringing in a cloud of any kind means that old processes like provisioning are bound to be radically altered… to the point they could be unrecognizable from what they were before.
Gardner brings up a lot of other sharp observations, which you should take some time to read. Deploying cloud is a big shift for any business and the more knowledge you have up front, the better.