In my last blog post, I identified ten reasons private clouds were failing. I consolidated that list to six items (below), and polled attendees at Gartner’s Datacenter Conference in Las Vegas in December. I asked the question “What is going wrong with your private cloud?” I was a little surprised that 95% of the 140 respondents (who had private clouds in place) said something was wrong with their private cloud.
- Focusing on the wrong benefits: Internal, bottom-line, or not putting the right metrics in place. (Usually, this is focusing on cost-savings, not agility).
- Doing too little: Is this really cloud? Or just virtualization? And what about the stuff running inside the VMs?
- Defending I&O — and doing too much: Optimizing for everything means optimizing for nothing.
- Failure to change the operational model: Agile clouds need agile processes — and people are your biggest supporters, or your biggest roadblocks.
- Failure to change the funding model: When you build a drive-thru service model, you better get paid first.
- Using the wrong technologies: What’s tactically right might be strategically wrong.
Read Complimentary Relevant Research
Cloud Computing Primer for 2017
Cloud has evolved from a disruption to an expected approach to traditional as well as next-generation IT. Our research helps IT leaders,...
View Relevant Webinars
Managing Software Asset Risks in Outsourced and Cloud Environments
Business customers, who often have little understanding of the cost and complexity of software contracts, task sourcing professionals...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.