Skip to main content

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.

Hot Topics

The Latest

For fifteen years, observability lived downstream of everything else. Code shipped, something broke, an engineer went to the dashboards. The job was forensic. The pillars we built, such as logs, metrics, and traces, were designed for that role: tell a human what just happened, fast enough that they can make it stop. That role has quietly ended ...

Hybrid IT has become the standard operating model for enterprises — but that companies are still looking for the right hybrid IT mix, according to the 2026 State of the Data Center Report from CoreSite. After years of cloud migration and hybrid adoption, organizations are shifting their focus from deciding whether to use cloud, colocation or on-premises infrastructure to determining which workloads belong in each environment ...

Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...

Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...

I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...

The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...

For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...

The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...

44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...

Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...

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.

Hot Topics

The Latest

For fifteen years, observability lived downstream of everything else. Code shipped, something broke, an engineer went to the dashboards. The job was forensic. The pillars we built, such as logs, metrics, and traces, were designed for that role: tell a human what just happened, fast enough that they can make it stop. That role has quietly ended ...

Hybrid IT has become the standard operating model for enterprises — but that companies are still looking for the right hybrid IT mix, according to the 2026 State of the Data Center Report from CoreSite. After years of cloud migration and hybrid adoption, organizations are shifting their focus from deciding whether to use cloud, colocation or on-premises infrastructure to determining which workloads belong in each environment ...

Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...

Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...

I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...

The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...

For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...

The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...

44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...

Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...