Who’s driving the cloud strategy in your organization? Recently we had a team of cloud experts join Dell technologists including myself (@NickBrackney) for our #CloudTweetChat. Having a chance to interact with and learn from so many knowledgeable folks with varied backgrounds and approaches is critical for our team as well as our customers. What makes these chats great is we go beyond the buzz words and marketing fluff that permeates the discussion and get right into strategies and implementation. As we prepare for our next CloudTweetChat on March 12th it seemed like a good time to reflect on what we learned in our last conversation.
Experts in attendance included:
- Tim Crawford, CIO Strategic Advisor, AVOA, (@tcrawford)
- Keith Townsend, Co-Founder, The CTO Advisor (@CTOAdvisor)
- Eric Kavanagh, Bloor Group CEO, Tech Evangelist, and Media Innovator (@eric_kavanagh)
- Adam Post, Principal Consultant, IT Partners (@semi_technical)
- Ned Bellavance, Founder, Ned in the Cloud, LLC (@Ned1313)
- Bob Ganley, Senior Marketing Consultant, Dell EMC (@ganleybob)
- Josh Fidel, Principal Solutions Architect, Rolta|Advizex (@jcefidel)
- Brian Solis, International Keynote Speaker, Thought Leader and Analyst, (@briansolis)
- Arjan Timmerman, Co-owner and Analyst, TECHunplugged, (@Arjantim)
- Matt Baker, SVP of Strategy and Planning, Dell EMC (@mattwbaker)
- Phil Bradham, Azure Stack Applications Architect, Dell EMC, (@PBradz)
Who’s driving the cloud strategy?
To better understand the role of IT, we need to understand if there is a centralized cloud strategy and who is driving it. I believe that strategy should be coming out of the CIOs office. It could also be a combined effort with the CTO, IT operations, security and developers forming a cross-functional team.
Keith Townsend countered that most companies don’t have a CTO, and functionally, enterprise architects fulfill that role. He believes enterprise architecture should be driving cloud strategy. “CIO’s should leave the “how” to lieutenants. They should hire people to make those functional decisions and sign off as a sanity check.”
Tim Crawford added that, “the CIO should be the one taking point on the cloud strategy. However, likely others within their org will be more engaged on the execution.” Tim reminds us, “Technology is a team sport. But, not everyone plays the same roles or speaks the same language.” Phil Bradham concurs that input from multiple disciplines should be in the plan.
Josh Fidel breaks down ownership this way:
- Executives (CxO/VP) should set high level strategy based on desired outcomes.
- Management (Director/Manager) should define use cases to achieve those outcomes.
- Architects should help choose which cloud technologies and providers meet those use cases.
- Engineers should train for the chosen technology.
Rob Steel also agreed that multiple business leaders should be involved in the process, in order to assure each department’s requirements are met.
From my perspective, it’s easy to see the benefits of centralizing your cloud strategy. It should help deliver better security postures, accelerate innovation, and improve service levels. You’ll likely see cost savings, too.
Adam Post weighed in, “one of the primary downsides of a fragmented cloud strategy is the additional complexity required to both architect and maintain applications across platforms. Having a centralized strategy goes a long way toward addressing this.”
Any fragmentation works against efficiency and drives down value, and cloud strategy is no different, as Tim Crawford observed. Matt Baker agreed that a fragmented strategy breeds complexity, drives up costs and slows down the organization.
The struggles with creating a consistent cloud strategy
Getting the entire organization to support a cloud strategy is key, Phil noted. Saying it’s important to share a clear explanation of the plan in business terms.
“A barrier to consistency is commonly the difference in underlying platforms and the methods of interfacing with them. Some tools attempt to abstract away the differences, leaving a lowest common denominator of features. A common underlying platform avoids this,” says Adam.
Ken said that he believes multi-cloud in the context of a single application is a myth, or possibly a trap. But Tim countered that most enterprises are using multi-cloud quite successfully.
Shadow IT and internal delays were at the top of Josh’s list of challenges. Others chimed in about the struggles with other departments deploying applications without IT. But, Tim observed that transformative CIOs can find value in shadow IT.
The Lift and Shift Controversy
The conversation shifted when I commented that I think lift and shift can still offer value, but absolutely agree that loud native and using HCI and API driven architectures on-premises is helping IT to deliver IaaS capabilities everywhere.
This kicked off a spirited debate between our participants. Tim disagreed: He considers lift and shift only useful in specific use-cases with a very defined time frame. He doesn’t recommend making it a core strategy. But Keith noted that this has been the historical use case for cloud.
Matt also added fuel to the fire with a controversial statement, “cloud is ALWAYS more expensive because renting assets is ALWAYS more expensive…However, that doesn’t mean Public Cloud isn’t critical and important.”
I think where we landed on is cloud not done properly can limit the benefits of this model, and the idea cloud saves money is largely inaccurate. Mike says the cost narrative is only true if you treat cloud as a data center. This brings us back to the key strategy points:
- What do you need to run where?
- What are the economics for your organization?
How can technology partners make it easier for IT to drive innovation with cloud?
My thoughts were that technology partners must embrace openness and support customers on whichever cloud they need/want to run on. The idea of a single source for IT just doesn’t work in the as-a-service economy, because no one vendor has all the answers.
Arjan Timmerman advised technology partners to “listen to the customer and sell them the product(s) they need, not what has the biggest profit.”
Adam agreed, stating “partners should take the opportunity to help customers re-evaluate their requirements and be open to a change in approach, where it makes sense.”
Tim echoed the other sentiments in the group: “Technology partners need to clearly understand their customer’s business objectives, challenges and current state,” he says.
“We now need (trusted technology vendors) to help tell us how to solve business challenges. Public cloud enables businesses to do tech, vendors should enable IT to do business,” Keith concluded.
For the bonus round, we asked: In organizations where developers or lines of business (LoB) units have led the charge, how can IT regain control? Eric Kavanagh suggests launching a Kubernetes instance and having an IT director take the lead.
Josh Fidel sums up a winning strategy:
- Stop playing politics.
- Have conversations.
- Understand business needs from the views of the stakeholders.
- Work TOGETHER to find solutions.
Consider the importance of what is already in place, and don’t try and move mountains overnight. Instead, build a sustainable cloud strategy that is staged to avoid undue risk or halting innovation.
Make sure you join the 3/12 Cloud Native #CloudTweetChat
Mark your calendar for the next #CloudTweetChat on 3/12 . Our topic is: Kubernetes and Cloud Native.
You can follow @DellTechCloud for insights anytime for always-on insights and discussions on cloud.