As I type this, it’s a few hours before the final day of Symposium Gold Coast 2015. I’ve been honoured to have a range of interactions on cloud strategy, cloud challenges … and some cloud (as well as virtualisation) successes! It’s been a great event,
During my sessions, I’ve been using interactive polling. I find this a great way to get a little more accuracy (and anonymity) than raising of hands.
As promised, I am sharing the results … noting these are skewed^ … but that’s actually what makes them interesting.
Below are the polling results for my question of use of public cloud IaaS.
This fits with the pattern of later-start, faster-adoption of public cloud IaaS I’ve seen in Australia / New Zealand since ~2014. It also contrasts starkly with the (broader, statistically-valid survey results from ABS). Of particular note, this more aggressive adoption has it’s own set of challenges …
[insert small sales plug] Gartner clients can, of course, ask how to avoid these challenges. [end plug].
I hope you find these results of value.
^ I say the results are skewed because:
- All respondents are self-selecting (to attend a session on private and hybrid cloud, and to participate)
- Results are primarily – but not exclusively – Australian and New Zealand attendees
- We need to take the results at face value; there’s no independent verification
- The sample size is 95 respondents in this case
- Most respondents are likely to be enterprise-scale, which is particularly relevant to the results from the Australian Bureau of Statistics 2015 survey
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.