You've successfully completed proofs-of-concept using the cloud. You've staffed a cross-functional cloud tiger team to define standards. You've communicated broadly and won executive support. Why is your cloud transformation program stalling? If this sounds familiar, know that you're not alone. Many organizations experience program delays, with some delays lasting 12 months or longer. We spoke with leaders, project consultants, and engineers from mature organizations that have successfully accelerated through program delays. In this session, we discuss what we learned about why cloud transformation programs stall even when you do everything right and share nine best practices for avoiding or breaking through a delay.
2. 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
4. Stall [stawl] verb
1.1 stop or cause to stop making
progress
1.2 (of a motor vehicle or its engine) stop
running, typically because of an overload
on the engine
20. 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
It is the de facto standard
It has the largest installed base
It has most third-party supporters
It has great support
It has low cost of ownership
s
What they want
is different
Early Adopters
Early Majority
25. 10 things you need to do differently
in your cloud transformation
program…
26. 01
Admit you’ve got a problem
What made your change initiative successful thus far
is not relevant for the next stage in adoption.
Next step
Do a lean-ux user persona workshop to understand
the early majority in your enterprise.
27. 02
Change and incentivize the team members
Your cloud enablement team is likely full of innovators,
led by an early adopter, and very poachable.
Next step
Bring in new team members who can open doors into
the Early Majority market, bring key supplementary
skills, and provide lots of positive reinforcement.
28. 03
Identify the beachhead
You need a strategic market entry project that you can
complete. Your victory will impress follow-on Early
Majority buyers.
Next step
Do a beachhead analysis workshop to develop your
decision rubric and analyze the context.
29. 04
Identify the bowling pins
Don’t boil the ocean. It’s about momentum, not volume.
Next step
Re-use your beachhead decision rubric, and run a
bowling pin analysis workshop.
30. 05
Re-position / Re-communicate
Change the communications script to speak to the early
majority psyche.
Next steps
Adopt a cloud-first strategy led from the top.
Throw out your existing communications plan and do a
new one.
31. 06
Re-prioritize the offering
Deliver the product halo and remember that
transformation != migration.
Next step
Revisit your MVP and start to experiment again with the
offering, but use a new group of target customers.
32. 07
Address Early Majority org ecosystem
Clear barriers proactively, and don’t bring a knife to a
gunfight – bring in experts here.
Next steps
Put cloud first into vendor RFPs.
Get on the front foot with finance and financial reporting,
security, legal, and procurement.
33. 08
Be heard and seen
Communicate wins. And then communicate wins. And
then after that communicate wins.
Next step
Develop a communications tactical plan that reflects
Early Majority values, and start delivering it.
34. 09
Lead, lead, lead
Leaders must stay engaged and visible. They must also
discipline with carrots and sticks.
Next step
Require middle managers to get certified, and
encourage senior managers to set examples by sitting
beside them.
35. 10
Automate
It was fine to do things manually in the early phase, but
that will never scale to thousands of apps.
Next step
Get your people trained with DevSecOps and
DevSecOps on AWS. Reuse a Bot Army like GE or a
Simian Army like Netflix.
36. Admit you have a problem
Change the team members
Identify the beachhead
Identify the bowling pins
Re-position
Re-prioritize the offering
Work on the ecosystem
Be heard and seen
Lead
Automate
Say what?!?