The Cloud Doesn’t Care About Your Strategy. Until You Make It
What senior leaders still get wrong about cloud transformation and how the ones who get it right think differently
I’ve sat through more cloud transformation kick-offs than I can count. Bright decks, enthusiastic vendors, a CTO with a roadmap that looks like it was designed by someone who had never met a P&L. And almost every time, somewhere around slide fourteen, I’d feel a familiar tightening in my chest, because I knew we were about to spend eighteen months and a significant portion of the technology budget to end up roughly where we started, just with more Kubernetes clusters and a slightly higher AWS bill.
That feeling pushed me to think harder about what actually separates the organizations that transform from the ones that merely migrate. After a decade of navigating these journeys, first as a line-of-business leader, then in the executive suite, the answer I keep coming back to is deceptively simple: it’s not about the cloud. It never was.
🔥 Top Tech Jobs Are Hiring NOW — Don’t Miss Out.
👉 Apply & Secure Your Job
The Strategy Problem No One Talks About
Here’s an uncomfortable truth I’ve had to share with boards and executive teams over the years: most cloud transformation initiatives fail at the leadership level, not the technical one. The engineers usually know what to do. The architects have seen the patterns before. What tends to collapse is the organizational will, specifically, the willingness of senior leaders to make the hard structural decisions that cloud transformation actually demands.
Moving workloads to the cloud is a technical exercise. Transforming with the cloud is an organizational one. The distinction matters enormously. When you conflate the two, you end up with a very expensive lift-and-shift that burns out your engineering teams, delivers marginal cost savings, and leaves the business more or less unchanged, except now everything runs in a data center you don’t own and can’t fully explain to your CFO.
“The cloud is not a destination. It’s a set of capabilities that only unlock value when the organization has the maturity to use them.”
I’ve watched companies spend north of $50 million on cloud programs that, when examined honestly, amounted to: we moved our servers and changed some vendor relationships. That’s not transformation. That’s relocation. And the executive team, if we’re being straight with each other, often played a direct role in producing that outcome by treating cloud as an IT initiative rather than a business one.
What the Board Actually Needs to Hear
Let me tell you what I wish someone had said to me earlier in my career, and what I now make a point of saying plainly in boardrooms: cloud transformation is a bet on organizational agility. Not on cost savings, not on innovation theater, not on being able to say you’re “digital-first” in the annual report.
When framed correctly, the conversation with a board should center on three things: the speed at which the business needs to respond to market changes, the degree to which technology currently constrains or enables that speed, and what it would take, honestly, structurally, to remove those constraints. Cloud infrastructure, when it’s working, compresses the cycle time between an idea and its impact on the customer. That’s the value proposition. Everything else is noise.
The CFO will want to talk about CapEx versus OpEx. Acknowledge it, but don’t let it dominate the room. A shift from capital expenditure to operational expenditure does change the balance sheet in interesting ways, but it’s not the point. The point is that variable cost models align your technology spend with your business outcomes, you pay for what you use, you scale what works, and you stop funding what doesn’t. That’s a fundamentally different relationship with technology investment, and it requires a fundamentally different kind of financial governance.
The Organizational Change Nobody Budgets For
Here’s where most transformation programs quietly fall apart: they budget for technology and forget to budget for people. Not headcount, capability. The gap between what your teams know how to do today and what cloud-native operations actually require is almost always wider than the initial assessment suggests. And it doesn’t close itself.
Get Giulio Sistilli’s stories in your inbox
Join Medium for free to get updates from this writer.
I’ve seen this play out in a particular way more times than I’d like to admit. The initial excitement is high, the vendor promises are generous, and the early wins, spinning up environments faster, reducing deployment friction, feel genuinely good. Then, about six months in, the business starts asking for the things that were supposed to come from the transformation: faster product cycles, better data access, and more flexible pricing architectures. And that’s when the gap becomes visible.
The teams that were supposed to operate in this new model were never quite prepared for it. The governance structures that made sense for on-premises operations quietly strangled the velocity that cloud was supposed to unlock. The security practices designed for a perimeter that no longer existed created friction at every turn. And suddenly, the executive sponsor, perhaps you, is fielding uncomfortable questions from the board about why the transformation hasn’t produced the promised returns.
“You can’t transform your technology without transforming the operating model that surrounds it. Anyone who tells you otherwise is selling something.”
The fix isn’t complicated, but it does require honesty at the leadership level. Cloud transformation needs a dedicated organizational change workstream, not a line in the project plan, but a genuine investment in reskilling, role redesign, and the patient, unglamorous work of changing how teams make decisions. The organizations that get this right typically assign an executive, not a project manager, to own the human side of the transformation with the same accountability as the technical side.
Where AI Enters the Picture
It would be disingenuous to write about cloud transformation in 2026 without addressing the obvious: the reason most organizations are revisiting their cloud strategies right now has a lot to do with AI. The large language models and the infrastructure required to run them at scale have forced a reckoning in how enterprises think about their cloud architecture, their data strategy, and frankly, their entire technology roadmap.
What I find interesting and somewhat reassuring is that the fundamental leadership challenges haven’t changed. If anything, AI has amplified them. The organizations that built genuine cloud maturity over the last decade are finding it dramatically easier to adopt AI capabilities. The ones that did cloud theater are discovering that you can’t build on a shaky foundation, no matter how sophisticated the model running on top of it.
For executives navigating this right now, my honest counsel is this: don’t let AI urgency shortcut the structural work. The pressure to deploy AI capabilities quickly is real, and in some industries, the competitive stakes are genuinely high. But a poorly governed cloud environment doesn’t become a well-governed AI environment just because you add a language model to it. The data quality issues, the access control gaps, and the organizational silos all follow you up the stack.
The Questions I Now Ask in Every Transformation Review
After years of sitting across from executive teams at various stages of their cloud journeys, I’ve developed a short list of questions that tend to surface the real state of play faster than any status report. I share them here not as a framework to be rigidly applied, but as a set of honest provocations that have, more than once, redirected a program that was heading quietly off the rails.
The first question is deceptively simple: who owns the outcome? Not the project, not the budget line, the outcome. If the answer is the CTO or CIO, I get concerned. Outcomes belong to the business. Technology is the enabler. When the business leader has genuinely internalized ownership of the transformation outcome, the dynamic shifts in ways that are hard to manufacture through governance alone.
The second question is about the last thing that didn’t work. Every transformation has them: the migrated application that performed worse in the cloud, the cost estimate that turned out to be optimistic by a factor of three, the team that quietly reverted to the old way of working because the new way was too hard. How an executive team talks about those moments tells you everything about whether the organization is learning or managing optics.
The third question is about the customer. Not the end user of the technology, but the actual customer of the business. In what specific, demonstrable way will this transformation make their experience better, faster, or more valuable? If the answer takes longer than thirty seconds and involves the words “infrastructure” or “platform,” the program has probably lost the plot somewhere along the way.
A Final Word on Courage
I want to end on something that doesn’t get said enough in the business press, which tends to favor case studies of the companies that got it spectacularly right. Most cloud transformations are hard, messy, and humbling. They surface organizational dysfunction that had been quietly accumulating for years. They require leaders to make decisions — about people, about priorities, about what the business actually is and wants to be- that are genuinely difficult.
The executives who navigate this well aren’t the ones with the best technology strategy. They’re the ones with the courage to be honest about where the organization actually is, the patience to do the unglamorous structural work, and the clarity to stay focused on what the business is trying to become, not what the technology is capable of doing.
The cloud will do what you ask it to. The question, the only question that has ever really mattered, is whether your organization knows what to ask for.
