Cloud overspend is an accountability problem not a tooling gap
Network World ·

After years of using the clouds, many organizations are coming to realize they didn’t have a proper plan in place from the get-go. Cloud adoption has often been driven by urgency, not design, according to Nabeel Sherif , principal advisory director at Infotech. It accelerated over the past 15 years, especially during the pandemic. Most organizations moved workloads and adopted SaaS, but the operating models behind that work did not change at the same pace. Infrastructure and operations teams, network teams included, now run on-premises and cloud side by side, often without a unifying model. They remain accountable for availability, cost, and risk but with far less direct control than in the past. The cost shows up in the numbers. Flexera’s 2026 State of the Cloud Report , which Sherif cited, estimates that 29% of IaaS and PaaS spend is wasted. Organizations also run 17% over their public cloud budgets on average. During a session at the Infotech LIVE 2026 conference in Toronto, Sherif outlined a method for redesigning cloud operations around the work that needs doing, then assigning that work to teams. “Cloud doesn’t eliminate operations work; it just changes its nature,” Sherif said. Why more tools and training miss the problem The common reaction that many organizations have to cloud problems is to buy more tools or add training. Those actions don’t however always solve the underlying issues. In Sherif’s view, the data points to governance, organizational structure, visibility, and accountability as the right path forward. Accountability is the sticking point because ownership and control no longer line up in the cloud. “In traditional operations, you assume ownership of the stack. Cloud breaks that assumption,” Sherif said. “You still own the outcomes. You don’t necessarily own all the underlying mechanisms.” He added that neither self-service nor automation fixes the issues. “Without redesign, you get responsibility without leverage,” he said. “So, governance, cost management, and security practices, if they remain rooted in sort of pre-cloud thinking, that’s going to create tension between the control mechanisms that we have in place and the actual delivery mechanisms that we’re using.” Designing cloud operations around the work Operations teams should spend less time executing tasks directly and more time validating services, monitoring outcomes, and managing vendors. That shifts where operational influence has to occur. “Cost, reliability, and security are increasingly determined by design rather than after deployment,” Sherif said. Sherif’s method starts with the work, not the org chart. A foundational step is to sort cloud work into consuming SaaS, hosting workloads, and building custom services, because each needs different skills and controls. Most organizations do all of this work, but not in equal measure. Sherif advises starting with the type that carries the most risk or the highest volume of work. An organization that mostly consumes SaaS needs vendor management and integration skills. A development-heavy one needs CI/CD pipelines and developer support structures. “Most organizations do all three simultaneously, treat them the same way, and that’s where things fall down,” Sherif said. The next step is choosing organizational structures that fit the work. Sherif calls these patterns. He treats them as design options that organizations combine and change over time, not as boxes to check. Some patterns are ways to govern and learn. A cloud center of excellence (CCoE) and a cloud community of practice apply to every type of work. Others are ways of working. DevOps, site reliability engineering, and platform engineering matter most for build work. “If your organization is mostly consuming SaaS, most of those patterns are not going to be a priority for you,” Sherif said. The result is a framework of work areas, not an org chart. A work area is a group of related work that needs to get done. It is defined before anyone decides which team handles it. “Teams do imply people and reporting structures, and that conversation pulls attention to who owns what today, rather than what needs to get done in the future,” Sherif said. Where leaders can start Sherif urged organizations to start from the work, not today’s org chart. He asked the room to consider what type of work they do, what makes that work good quality and how to organize around the work rather than around functions. The order matters. “You want to design the operation model around the work, and then map current teams to it to identify where the gaps and the changes are,” Sherif said. The resulting framework becomes a communication tool, he said. Leaders use it to explain what they propose and why. Staff use it to see how their roles relate to the broader model. The friction he sees most often comes from project teams that bypass IT. A team talks to a vendor, builds or buys a solution, then tells IT only afterward. Unaligned expectations drive that friction. Sherif relayed a friend’s saying about babies. “Babies aren’t dumb they’re just new,” he said. “[If] people don’t know stuff, then you can’t expect them to be smart about stuff. So, we need to set those expectations.”