IT Pros Say: Cloud Needs a Makeover

Josh Stella

It's not especially surprising that a new IT survey shows that cloud use for business and government poses challenges. All transformative technologies do. It's the extent of agreement — 96 percent say cloud needs a "makeover" — and nature of the challenges that's worth examining. In significant numbers across the board, respondents cited cloud complexity, compliance and security, cost control, speed of delivery, and domain expertise as the cloud problems their organizations were working to overcome this year.

The Three Cs and Beyond

Compliance, complexity, and cost were the obstacles to effective cloud management that garnered the three top trouble spots. The survey yielded specific complaints around each of those.

Compliance refers to businesses and government agencies or their contractors making certain that internal policies (usually structured around security and system reliability concerns) and regulatory demands (around NIST SP 800-53, HIPAA, ITAR, and other laws) are met. In the survey, almost 44 percent of respondents identified ensuring compliance and security as a top cloud challenge. 39 percent said security and compliance "is slowing us down."

And, when asked to prioritize the chief reason that cloud needs an overhaul, the second most popular response was "it needs to be easier to keep secure," with "it needs to be simplified and easier to use" coming in at number one.

Indeed, turning to ease of use, the nature of cloud's complexity problem was laid bare in several parts of the survey as well. Almost 42 percent said that "managing increasing cloud complexity" was a foremost concern. When asked why their company failed to get the most out of cloud, respondents emphasized that C-level executives (26.1 percent), IT leadership (35.8 percent), and developers (20.3 percent) "don't understand cloud complexity."

Contributing directly to the complexity conundrum are the number of tools and services organizations use and the nature of the problems that tooling can create. In order to make the cloud deliver on business expectations, more than half of the respondents cited high numbers of tools and services in use: 30.6 percent at 6 to 10, 15.8 percent at 11 to 15, and 6.8 percent at 15 or more. Another 38.4 percent use at least 3 to 5 tools and services to make cloud deliver. Tooling developed in house wasn't an answer to complexity either. A whopping 83 percent of respondents indicated that creating in-house solutions only leads to more problems.

The specific complaints are enlightening: in-house tooling requires specialists and time to maintain the tools; in-house tooling involves a lot of egos and, thus, a lot of politics; adopting newly available cloud services is made difficult with our in-house tooling; and, adopting new application architectures is made difficult with our in-house tooling.

The survey further revealed a direct relationship between complexity via tooling and the other top trouble spot, cost. Nearly 70 percent of respondents said they were spending almost as much or more on cloud tooling and services than on the cloud itself! Controlling costs overall was a chief problem that 47.7 percent of respondents were working to overcome this year, with some noting that not only does cloud need to be less expensive in general, but it needs to be easier to reduce costs. Nevertheless, compared with traditional data center operations, 57.7 percent agreed that the cloud had saved them money. A shadow on that strong figure is that another 25 percent were not achieving the savings they expected with the cloud.

In addition to compliance, complexity, and cost issues, almost 36 percent of respondents were concerned about meeting business agility demands — referring to the speed at which they could deliver their product to market with cloud utilized. Finally, a significant 26.5 percent worried about acquiring personnel with sufficient domain expertise in the cloud to make their organization efficient.

What's the Solution?

Undoubtedly, different practitioners will advocate different approaches to the cloud problems this survey and other surveys point out. But, if you can easily go fast, see everything, and keep a system right with one holistic approach, you can dramatically reduce the time spent and money wasted on complicated, multi-tooled operations and compliance regimes that don't take full advantage of cloud's innate character.

No matter the route chosen, businesses and government need an easy-to-understand solution, built for and with cloud, that requires only basic domain knowledge to operate, but that's powerful enough to manage scaled systems.

Survey Methodology: Just over half of the survey respondents identified as IT operations personnel. Others included developers, cloud architects, DevOps engineers, and executives. Organizationally, commercial enterprises, government agencies, small/mid-sized businesses, and startups were all represented. And, the survey covered all phases of cloud maturity in its field of respondents: 35.5 percent using a mix of cloud and on-premise data centers, 29 percent planning to adopt the cloud within the next year, 20.6 percent in the process of transitioning to the cloud, 14.8 percent fully in the cloud.

Related Links

Hot Topics

The Latest

MEAN TIME TO INSIGHT Podcast - Episode 24: Network Observability Tool Sprawl

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

Capacity Isn't a Guess: Observability-Driven Sizing for On-Prem Databases

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

5 Security Principles Every Entrepreneur Should Apply to Leadership

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Signs It May Be Time to Reassess Your IT Infrastructure Strategy

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Enterprise Edge AI Reaches Inflection Point

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

AI Is Hitting Operational Limits

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

Alert Fatigue Is No Longer a Morale Problem, It's a Reliability Risk and a System Failure

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

Most Enterprises Think They Can Switch AI Vendors in a Month ... Most Who've Tried Couldn't

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Your Observability Stack Has a Telemetry Pipeline Problem

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

Operator to Orchestrator: 80% of IT Pros See Shift in Role as AI Permeates Workflows

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

IT Pros Say: Cloud Needs a Makeover

Josh Stella

It's not especially surprising that a new IT survey shows that cloud use for business and government poses challenges. All transformative technologies do. It's the extent of agreement — 96 percent say cloud needs a "makeover" — and nature of the challenges that's worth examining. In significant numbers across the board, respondents cited cloud complexity, compliance and security, cost control, speed of delivery, and domain expertise as the cloud problems their organizations were working to overcome this year.

The Three Cs and Beyond

Compliance, complexity, and cost were the obstacles to effective cloud management that garnered the three top trouble spots. The survey yielded specific complaints around each of those.

Compliance refers to businesses and government agencies or their contractors making certain that internal policies (usually structured around security and system reliability concerns) and regulatory demands (around NIST SP 800-53, HIPAA, ITAR, and other laws) are met. In the survey, almost 44 percent of respondents identified ensuring compliance and security as a top cloud challenge. 39 percent said security and compliance "is slowing us down."

And, when asked to prioritize the chief reason that cloud needs an overhaul, the second most popular response was "it needs to be easier to keep secure," with "it needs to be simplified and easier to use" coming in at number one.

Indeed, turning to ease of use, the nature of cloud's complexity problem was laid bare in several parts of the survey as well. Almost 42 percent said that "managing increasing cloud complexity" was a foremost concern. When asked why their company failed to get the most out of cloud, respondents emphasized that C-level executives (26.1 percent), IT leadership (35.8 percent), and developers (20.3 percent) "don't understand cloud complexity."

Contributing directly to the complexity conundrum are the number of tools and services organizations use and the nature of the problems that tooling can create. In order to make the cloud deliver on business expectations, more than half of the respondents cited high numbers of tools and services in use: 30.6 percent at 6 to 10, 15.8 percent at 11 to 15, and 6.8 percent at 15 or more. Another 38.4 percent use at least 3 to 5 tools and services to make cloud deliver. Tooling developed in house wasn't an answer to complexity either. A whopping 83 percent of respondents indicated that creating in-house solutions only leads to more problems.

The specific complaints are enlightening: in-house tooling requires specialists and time to maintain the tools; in-house tooling involves a lot of egos and, thus, a lot of politics; adopting newly available cloud services is made difficult with our in-house tooling; and, adopting new application architectures is made difficult with our in-house tooling.

The survey further revealed a direct relationship between complexity via tooling and the other top trouble spot, cost. Nearly 70 percent of respondents said they were spending almost as much or more on cloud tooling and services than on the cloud itself! Controlling costs overall was a chief problem that 47.7 percent of respondents were working to overcome this year, with some noting that not only does cloud need to be less expensive in general, but it needs to be easier to reduce costs. Nevertheless, compared with traditional data center operations, 57.7 percent agreed that the cloud had saved them money. A shadow on that strong figure is that another 25 percent were not achieving the savings they expected with the cloud.

In addition to compliance, complexity, and cost issues, almost 36 percent of respondents were concerned about meeting business agility demands — referring to the speed at which they could deliver their product to market with cloud utilized. Finally, a significant 26.5 percent worried about acquiring personnel with sufficient domain expertise in the cloud to make their organization efficient.

What's the Solution?

Undoubtedly, different practitioners will advocate different approaches to the cloud problems this survey and other surveys point out. But, if you can easily go fast, see everything, and keep a system right with one holistic approach, you can dramatically reduce the time spent and money wasted on complicated, multi-tooled operations and compliance regimes that don't take full advantage of cloud's innate character.

No matter the route chosen, businesses and government need an easy-to-understand solution, built for and with cloud, that requires only basic domain knowledge to operate, but that's powerful enough to manage scaled systems.

Survey Methodology: Just over half of the survey respondents identified as IT operations personnel. Others included developers, cloud architects, DevOps engineers, and executives. Organizationally, commercial enterprises, government agencies, small/mid-sized businesses, and startups were all represented. And, the survey covered all phases of cloud maturity in its field of respondents: 35.5 percent using a mix of cloud and on-premise data centers, 29 percent planning to adopt the cloud within the next year, 20.6 percent in the process of transitioning to the cloud, 14.8 percent fully in the cloud.

Related Links

Hot Topics

The Latest

MEAN TIME TO INSIGHT Podcast - Episode 24: Network Observability Tool Sprawl

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

Capacity Isn't a Guess: Observability-Driven Sizing for On-Prem Databases

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

5 Security Principles Every Entrepreneur Should Apply to Leadership

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Signs It May Be Time to Reassess Your IT Infrastructure Strategy

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Enterprise Edge AI Reaches Inflection Point

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

AI Is Hitting Operational Limits

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

Alert Fatigue Is No Longer a Morale Problem, It's a Reliability Risk and a System Failure

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

Most Enterprises Think They Can Switch AI Vendors in a Month ... Most Who've Tried Couldn't

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Your Observability Stack Has a Telemetry Pipeline Problem

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

Operator to Orchestrator: 80% of IT Pros See Shift in Role as AI Permeates Workflows

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...