I recently wrote a research note to explain what we’ve been seeing from our client base. In thousands of interactions, there are very specific patterns for private cloud successes and failures. The top ten reasons (in no particular order) that private clouds are failing are:
- Focusing Exclusively on Operational Benefits: Thinking private cloud is an internal IT project only.
- Building the Wrong Expectations – or None At All: Business case and metrics are key.
- Defending IT: Building “private cloud” to protect IT’s turf.
- Doing Too Little: Often, private cloud really means virtualization, with maybe some automation
- Doing Too Much: Putting in everything including the kitchen sink. Optimized for everything, so it is optimized for nothing.
- Focusing Strictly on Infrastructure: VMs are not enough – something’s got to run inside them.
- Failure to Change the Operational Model: Jamming cloud into your existing process model and org structure ain’t gonna work.
- Failure to Focus on People: Your staff can be your biggest supporters, or your biggest roadblocks. Google the possible etymology of the word “sabotage.”
- Failure to Change the Funding Model: When you build a drive-thru service model, you better get paid first.
- Using the Wrong Technologies: Choices, choices – what’s tactically right might be strategically wrong.
Read Complimentary Relevant Research
Cloud Computing Primer for 2018
Cloud is evolving from a market disruptor to an expected approach for traditional and next-generation IT. Our research offers actionable...
View Relevant Webinars
The 2018 Security Threat Landscape
The security threat landscape has been exciting and surprising. But what is next? Gartner presents the best predictions on how the threat...
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.