Why does this actually matter?
Almost without fail, our clients come to us after they have tried to “move to” cloud, only
to experience some significant degree of pain and despair. As you might suspect, our
first endeavor is to better understand the work they have already done, and launch a
root-cause discovery for why it is not working out the way they projected. We have writ-
ten many times in the past about the usual blockers, so I will not rehash them here. Suf-
fice it to say, the one root cause we see that is more destructive than any other to the
success of a cloud transformation is the failure to understand that cloud truly is a new
and better way of doing things.
Let us do a little test to see if your organization is struggling with this nuance. If you read
The Doppler, you have likely heard about our best practice called the Cloud Business
Office (CBO). Think of a CBO as a decision-making body of all functional leaders who are
stakeholders (whether they know it or not) in the outcome of a cloud transformation.
As you can see in figure 1 below, there likely are more stakeholders than you may have
considered.
App Owners
Cloud Engineering
(LOB, Dev teams, etc.)
Technology Center of
Excellence (SMEs)
Information Security
Compliance & Risk
Communications
Cloud
Business
Office (CBO)
Operations
(Governance & monitoring)
IT Finance
Third Parties
(AWS, tool vendors, etc.) (Chargeback, budget, invoicing)
Enterprise Supplier
Management (Onboarding, Training)
HR
(Contract management)
Figure 1: Cloud Business Office
Ok, here is the test. If your organization is struggling with your cloud transformation and
you are having a difficult time figuring out the full extent of why that is, please go ask
the leaders (separately) of all the functions involved one simple question:
8 | THE DOPPLER |
SUMMER 2019