What Cloud Transformation Actually Taught Me
What Cloud Transformation Actually Taught Me
8 min read
There is a version of this essay I could write that is safe.
Technology alone is insufficient. People and culture matter. Organizations need alignment and change management. All true. All correct. And almost entirely useless as a guide to what actually happens inside large enterprises when a major transformation is underway.
I want to tell you what I actually saw — not the conference version, but the real one — because the same dynamics are playing out right now inside every large organization attempting AI transformation. The leaders who recognize them will be the ones who get it right.
How the methodology was built
I spent nearly a decade at Amazon Web Services building the Enterprise Transformation practice at AWS Professional Services. I joined to build something that didn't yet exist: a practice dedicated to the organizational and human dimensions of cloud transformation. At the time, this was counter-cultural. AWS was a technology company, and the prevailing belief — inside AWS and across the industry — was that technology was the lever. Get the platform right, and adoption would follow.
I believed something different. I believed that culture, leadership alignment, and operating model were the real barriers between cloud investment and realized value. It wasn't a popular position. But the evidence kept accumulating.
What followed was nearly a decade of collective learning — building frameworks, taking them into the field, watching what worked and what didn't, and iterating continuously in real conditions with real organizations. The practice attracted an extraordinary community of practitioners, partners, and customers all trying to figure out how to help large, complex organizations succeed at something they hadn't quite done before. The methodology that emerged wasn't a theoretical construct. It was built from experience — refined through hundreds of engagements and shaped by everyone in that room.
What the evidence showed
When cloud programs stalled — and many of them did — the diagnosis usually pointed to technology. The platform wasn't ready. The migration was more complex than expected. That was almost never the real reason.
Here is what I actually observed.
Executive teams that appeared aligned but weren't. Not misaligned in ways they would admit to — but quietly, structurally at odds. Different priorities, different budget expectations, different definitions of success. None of those disagreements had been resolved before the program launched. The transformation became a proxy battlefield for dynamics that predated it.
Organizations that radically underestimated the human and business impact. Leaders who approved a technology program discovered midway through that they were actually running a business transformation — one that required deep coordination across functions that had never worked this closely together, fundamental changes to how decisions were made and work was done, and a clarity of future-state vision that most organizations hadn't developed before the migration began.
Functions that felt bypassed — and responded predictably. The security organization was a consistent example. Security teams were almost universally brought in too late. Major architectural decisions had been made without them, and they had every rational reason to resist a process they hadn't shaped. What looked like obstruction was actually a predictable response to a solvable design failure. The people who carry real accountability for risk need to be in the room at the beginning.
Leaders who performed certainty they didn't have. Transformation requires something that most leadership development hasn't prepared leaders for: the capacity to lead with genuine confidence in conditions of genuine uncertainty. To model curiosity. To create environments where people feel safe bringing forward what they actually see.
What we found, in programs that struggled, was the opposite. Leaders who had been rewarded throughout their careers for having the answers continued to perform that certainty when they didn't have it. The culture this created wasn't dishonest, exactly — it was silent. People learned that raising a concern would be characterized as resistance. That the official narrative didn't fully match the real one, and that gap wasn't safe to name. Over time, organizations lost access to their most important resource: the honest intelligence of the people doing the work.
Early warning signals went unheeded. The people closest to real problems were sidelined rather than heard. Stated values and lived reality diverged — and people, who always know the difference, stopped trusting the stated values.
A misreading of what the talent problem actually was. Many organizations concluded that their people lacked cloud skills — which was partly true — and that training would close the gap — which missed the point. We watched entire organizations complete certification programs and return to environments where they had no meaningful access to the tools they'd just learned. Where conditions in the training environment bore no resemblance to what they'd actually encounter. Where months elapsed before they had any real opportunity to apply what they'd learned.
What people actually needed was relevant experience — continuous, integrated into real work, with access to real environments and the psychological safety to experiment and learn from mistakes in real time. Learning has to be part of the work, not a prerequisite for it.
A gap between stated values and lived reality. This may be the most damaging dynamic of all, because it is the one that erodes the trust an organization needs to sustain change over time. Many organizations had explicit cultural commitments to innovation, learning, candor, and psychological safety. And in many of those same organizations, the lived experience of the people doing the work told a different story.
People who raised early concerns — often accurate ones — were characterized as resistant rather than as contributors with valuable perspective. The behaviors publicly valued were privately penalized when they created friction. Over time, people learn the real rules. And they adjust their behavior accordingly — which means the organization loses access to the honest intelligence it most needs, precisely when transformation pressure is highest.
An organization that says it values learning but punishes failure is not learning. It is performing.
What the methodology addressed — and why integration matters
The insight that shaped the framework we built was this: transformation is a system, and you cannot fix it piece by piece.
The Enterprise Transformation Framework was built around four integrated dimensions — business and strategy alignment, financial operating model, cloud operating model, and people and culture — not as sequential phases or independent workstreams, but as concurrent forces that constrain and enable one another. An organization could develop a technically excellent cloud operating model and plateau because its financial model still ran on legacy economics. It could invest deeply in people and change management and still stall because its leadership team hadn't resolved the strategic questions underneath. The dimensions were interconnected, and the methodology had to treat them that way.
The whole is only larger than the sum of its parts when the parts are genuinely working together.
This is not a framework designed to add complexity. It is a framework designed to reflect reality.
Why it all matters for AI — right now
Every one of these dynamics is active inside organizations attempting AI transformation today.
Executive misalignment — present, and more consequential than in cloud because AI changes operating models, workforce strategy, and competitive position at a level that requires genuine board-level alignment, not just executive sponsorship.
The underestimation of human and business impact — widespread, and possibly more acute given the pace of change.
The talent misreading — already repeating, with AI certification programs that build vocabulary without building judgment.
The performance of certainty — endemic, in an environment where the honest answer to most questions about AI's organizational impact is genuinely uncertain and leaders are under intense pressure to appear as though it is not.
The gap between stated values and lived reality — visible in organizations that announce AI as a strategic priority while the people closest to the work understand that what is actually being optimized for is short-term cost reduction and competitive optics.
And the most consequential dynamic: organizations are removing the people whose judgment, institutional knowledge, and experiential expertise is exactly what AI systems depend on — in the name of the efficiency AI is supposed to create. The people who understand how work actually happens. Who know where the data is unreliable and why. Who carry the organizational memory that cannot be recreated from a prompt.
This isn't a workforce decision. It is an AI infrastructure decision. And the consequences will surface slowly, long after the leaders who made them have moved on.
The organizations that will lead
The organizations that will lead in the age of AI are not the ones moving fastest on the technology.
They are the ones building the organizational infrastructure now — before the pressure is acute, before the shortcuts become structural, before the people who could have told them the truth have been given enough evidence that telling the truth isn't safe.
Here is the important difference between now and the early days of cloud: the AI capabilities themselves are not settled. The tools are evolving rapidly, the competitive landscape is shifting continuously, and the regulatory environment is being written in real time. Organizations are not navigating a large, complex change. They are navigating change that keeps changing — a pace of disruption that outstrips any organization's natural capacity to absorb it.
The organizations with transformation DNA are better positioned not because they have all the answers. Nobody does. But because they have built the organizational capacity to navigate not having them — to hold uncertainty without losing direction, to learn continuously rather than episodically, to close the gap between the culture an organization says it has and the one it is actually running.
That is the work.
Not implementing the technology — the technology will keep evolving regardless. Building the organization that can keep up with it. Building the leadership that can navigate it honestly. Building the culture where the truth is safe, learning is continuous, and transformation is not something that happens to the organization but something the organization knows how to do.
That has always been the work. It is more urgent now than it has ever been.
Amanda Rankin pioneered the organizational and human dimensions of enterprise transformation at AWS Professional Services at a time when the prevailing belief — inside AWS and across the industry — was that technology was the only lever that mattered. She championed and led the development of the practice and methodology that became embedded in AWS's most significant enterprise programs, including the Enterprise Transformation Framework and OCA 6-Point Framework, shaping cloud adoption across thousands of enterprises globally. She most recently led transformation from inside a large enterprise, applying these principles to a major data transformation program. She writes about enterprise transformation, organizational resilience, and what it means to lead through continuous change at amandarankin.me
