Always Be Reinventing & The Cloud of Youth

“The only thing that is constant is change.” — Heraclitus

Most executives that I talk to tell me that their journey to the cloud is more about business and cultural transformation than it is about technology adoption. To that end, I’ve been writing a series on a mental model that I call the Stages of Adoption, which highlights the pattern of activities we see inside large organizations that are reinventing their business using the cloud. I think of this pattern as an iterative and transformational journey, and one of my goals with this series is to give executives who are interested in transforming their organization an approach to do so.

When I first published the opener for this series, I called the fourth and final stage of adoption “Optimization.” I was trying to suggest that, as the gravity of your IT portfolio shifts from on-premises to the cloud, each application will be easier to constantly optimize once it is migrated from on-premises to the cloud. While this is true — and I’ll elaborate on this point in a moment — I’ve come to believe that the term “Optimization” undersells the possibilities for organizations that make it to this stage in their journey.

Most large cloud migration efforts are backed by a business case that quantifies an end state. When I was at News Corp, for example, our business case was to migrate 75% of our infrastructure to the cloud over 3 years to achieve $100M in annual savings. This type of objective seems to have become quite common — dozens of executives have since told me that they are looking to migrate 75–90% of their IT portfolio to the cloud in the next 3 years.

But realizing a business case objective like this is only the beginning. Organizations on this journey also have the opportunity to constantly reinvent their people, process, technology, and, perhaps most importantly, their culture. I sometimes think of this journey as a perpetual quest for a “fountain of youth” that will allow enterprises of all ages to continue to compete in a rapidly evolving marketplace. (Since its inception in 1955, for example, the Fortune 500 has seen between 20 and 50 companies fall off the list each year. Advances in technology are largely behind this steady rate of turnover, with the cloud being the most recent cause of large-scale disruption.)

So, to more precisely articulate what we see in organizations that are investing in cloud-first strategies as they constantly evolve their business, I’m rebranding the fourth — and never-ending — stage of adoption to “Reinvention.” I’m also kicking off a mini-series on what goes on inside companies that have migrated large portions of their IT portfolio to the cloud and modernized their culture in the process.

The 4 Stages of Adoption: Project, Foundation, Migration, Reinvention

Throughout this mini-series, my team and I are going to attempt to cover the impact on organizational culture, give some examples of customers who have reinvented themselves using the cloud, and show that migrating your IT portfolio to the cloud is only the beginning of what’s possible.

As a teaser to this mini-series, I’d like to offer a quote from one of the cloud’s earliest adopters:

“Our journey to the cloud at Netflix began in August of 2008, when we experienced a major database corruption and for three days could not ship DVDs to our members. That is when we realized that we had to move away from vertically scaled single points of failure, like relational databases in our datacenter, towards highly reliable, horizontally scalable, distributed systems in the cloud. We chose Amazon Web Services (AWS) as our cloud provider because it provided us with the greatest scale and the broadest set of services and features. The majority of our systems, including all customer-facing services, had been migrated to the cloud prior to 2015. Since then, we’ve been taking the time necessary to figure out a secure and durable cloud path for our billing infrastructure as well as all aspects of our customer and employee data management. We are happy to report that in early January, 2016, after seven years of diligent effort, we have finally completed our cloud migration and shut down the last remaining data center bits used by our streaming service! … Many new systems had to be built, and new skills learned. It took time and effort to transform Netflix into a cloud-native company, but it put us in a much better position to continue to grow and become a global TV network.”
— Yury Izrailevsky, Vice President of Cloud and Platform Engineering at Netflix. (Full quote here).

Yury’s seven-year cloud migration at Netflix is both instructive and inspirational, and the re-architecting he led helps explain how Netflix was able to remain a dominant brand in its industry as the video streaming market evolved.

Most companies aren’t Netflix, though, and we see a lot of companies that favor a rehosting (a.k.a. “lift-and-shift”) approach to migrate applications faster, which then makes it easier to optimize over time. I highlighted this natural tension between re-architecting and rehosting in a recent post on 6 Migration Strategies, and I’ll expand on it a bit more in my next post.

Before I close, I’d like to issue a call-to-arms to anyone who has experience leading their organization through the stages of adoption. Other executives are eager to hear about your journey, and I’m eager to host your experience here on my blog. Salvatore Saieva, the CTO Lead for Public Cloud Projects and Initiatives at AIG, recently wrote about AIG’s journey, and I know there are more good stories out there. If you’re interested in telling your story and attracting talent to your organization, please email me (orbans@amazon.com) with your ideas, and we’ll tell your peers about it!

Keep building,
- Stephen
orbans@amazon.com
@stephenorban
http://aws.amazon.com/enterprise/

Note: “Reinvention” is the fourth (and never-ending) stage of adoption I’m writing about in the Journey to Cloud-First series. The first stage is “Project,” the second stage is “Foundation,” and the third is “Migration.” This series follows the best practices I’ve outlined in An E-Book of Cloud Best Practices for Your Enterprise. Stay tuned for more posts in this series.