Keep Cloud Transformation on Track: Nine Best Practices to Avoid or Break Through a Stalled Cloud Transformation Program
Intended for customers who have (or will have) thousands of instances on AWS, this session is about reducing the complexity of managing costs for these large fleets so they run efficiently. Attendees will learn about common roadblocks that prevent large customers from cost optimizing, tools they can use to efficiently remove those roadblocks, and techniques to monitor their rate of cost optimization. The session will include a case study that will talk in detail about the millions of dollars saved using these techniques. Customers will learn about a range of templates they can use to quickly implement these techniques, and also partners who can help them implement these templates.
What to expect from the session
• Learn from research done by AWS Professional
Services to understand why many enterprise cloud
transformation programs stall in the field
• Discuss 10 best practices shared by enterprises
who were able to break through the stall
Most transformation programs
will stall in the field
Stall [stawl] verb
1.1 stop or cause to stop making
1.2 (of a motor vehicle or its engine) stop
running, typically because of an overload
on the engine
What we would like to see in a cloud
at around 20%
These groups share buying goals and buying
Because of the differences between buying
(This is the big one)
… several crises emerge in the process
Occurs because Early Adopters and
Early Majority are so different
• It is new to the market
• It is the fastest product
• It is the easiest to use
• It has elegant architecture
• It has unique functionality
What they want is different
• It is the de facto standard
• It has the largest installed
• It has most third-party
• It has great support
• It has low cost of ownership
Managers in enterprises behave the
same as consumers in consumer
Accelerating through the Great Stall
is the same as Crossing the Chasm
10 things you need to do differently
in your cloud transformation
Admit you’ve got a problem
01 Next step
What made your change initiative successful thus far
is not relevant for the next stage in adoption.
Do a Lean UX user persona workshop to understand
the Early Majority in your enterprise.
Change and give incentives to team members
02 Next step
Your cloud enablement team is likely full of innovators,
led by an early adopter, and very poachable.
Bring in new team members who can open doors into the
Early Majority market, bring key supplementary skills, and
provide lots of positive reinforcement.
Identify the beachhead
03 Next step
You need a strategic market entry project that you can
complete. Your victory will impress follow-on Early
Do a beachhead analysis workshop to develop your
decision rubric and analyze the context.
Identify the bowling pins
04 Next step
Don’t boil the ocean. It’s about momentum, not
Reuse your beachhead decision rubric, and run a
bowling pin analysis workshop.
05 Next step
Change the communications script to speak to the
Early Majority psyche.
Adopt a cloud-first strategy led from the top.
Throw out your existing communications plan and
do a new one.
Reprioritize the offering
06 Next step
Deliver the product halo and remember that
transformation != migration.
Revisit your MVP and start to experiment again with
the offering, but use a new group of target
Address the Early Majority org ecosystem
07 Next step
Clear barriers proactively, and don’t bring a knife to a
gunfight—bring in experts here.
Put cloud first into vendor RFPs.
Get on the front foot with finance and financial
reporting, security, legal, and procurement.
Be heard and be seen
08 Next step
Communicate wins. And then communicate wins.
After that, communicate wins.
Develop a communications tactical plan that reflects
Early Majority values, and start delivering it.
09 Next step
Leaders must stay engaged and visible. They must
also discipline with carrots and sticks.
Require middle managers to get certified, and
encourage senior managers to set examples by
sitting beside them.
10 Next step
It was fine to do things manually in the early phase,
but that will never scale to thousands of apps.
Get your people trained with DevSecOps and
DevSecOps on AWS. Reuse a Bot Army like GE or a
Simian Army like Netflix.
Recap: your actions
1. Admit you have a problem
2. Change the team members
3. Identify the beachhead
4. Identify the bowling pins
6. Reprioritize the offering
7. Work on the ecosystem
8. Be heard and seen