Technical disruptions are likely only a small hurdle to overcome when compared to the organizational change that is required for moving from legacy on-premises IT technology to the public cloud. Here are a few considerations for getting executive buy-in for your public cloud projects.
Executive Buy-in Early on
Finding your internal champion or “partner” early on in your public cloud computing strategy is key. Once the partner has been identified it is important to be completely transparent about the plans and the progress of the project, identifying successes as well as failures and the lessons learned. One way to achieve this buy-in is to explaining your plans in terms of business value like business agility, innovation and faster time to market, which often times, at scale, can far outweigh the costs associated with cloud infrastructure.
Budgetary and Financial Considerations
If you are used to calculating and receiving your budget based on the procurement of IT hardware and licensing over the next 12 months, chances are the utility billing model will throw your procurement department for a loop. The way funding is allocated for projects hosted in the public cloud is drastically different than the old model. While the utility billing model may be cheaper in the long run for highly variable workflows, especially in capital costs, predicting total expenditure early on in the fiscal year can be difficult.
Procurement departments are used to beating up their vendors for more attractive pricing by utilizing grueling RFQ/RFP processes. This model cannot be used (at least at this point) with public cloud infrastructure. More about writing an RFQ/RFP to procure public cloud infrastructure here.
The third funding consideration with the public cloud is the over provisioning of infrastructure. The fastest time to value in your cloud project is achieving developer adoption. You want your developers to become familiar with the new cloud platform, and be able to rapidly deploy their development environments, but at the same time you do not want infrastructure to be deployed just because the novelty of rapid deployment exists.
To overcome these challenges many organizations have implemented a bill-back or show-back model to create awareness and accountability for the cloud computing resources that are used. Not only do these methods help prevent the over provisioning of infrastructure, but they help the financial decision makers calculate trends in spending.
Launching a project hosted in the public cloud, especially if it is the first, can be quite disruptive on many levels. One thing to remember is that there are many companies going through the same internal struggles that you are. Cloud-A is always willing to help match users up with each others to discuss their public cloud success stories as well as their horror stories (with their permission of course.)
For more information on cloud migrations and other considerations for public cloud adoption, check out our whitepaper titled: Public Cloud Adoption in the Enterprise.
- Best practices for faster time to value
- Keys to developer adoption
- Application considerations
- Handling internal politics
- Budgetary considerations
- Achieving executive buy-in