>>from >>around the globe. It's the >>cube >>With digital coverage of IBM. Think 2021 brought to you by IBM. >>Welcome back to the cubes, continuous coverage of IBM Think 2021. My name is Dave Volonte and I'm one of your hosts for our virtual coverage. We're gonna talk about cloud and hybrid cloud, what it is, what it means to clients and how the cloud journey will likely unfold in the coming several years with me to address these issues is varun vigilante. Who is the managing partner? Hybrid cloud transformation at IBM Welcome Baron. Good to see you. >>Thank you. Dave. Wonderful to talk to you. >>So you hear people talk about, you know, they say cloud first cloud, we've got a cloud first strategy. What does that even mean? What is a cloud strategy? Is it a technology roadmap? Is it is it an experience? Is it a business strategy? What really is a cloud strategy all about? And importantly how does it support business outcomes? That's really what matters? >>Brilliant. Great question. I always believe it's less about the journey to the cloud and it's more important what you do when you get there. That is, you know, what business outcomes does it actually support no many different starting points for an enterprise to embark upon a cloud enabled transformation, you know, things like reducing technical debt and costs, creating new products and services, accelerating time to market and even changing working practices in an organization. Now, as we work with clients, we are seeing increasingly value coming from open innovation. What I mean by that is expanded revenue opportunities with broad ecosystems, you know, new ideas, new platforms and increased time to market. Now accessing value from what we call those ecosystems and that open innovation we believe requires open hybrid, multi cloud architecture with that, it enables you to plug into those those ecosystems, allows you to fully consider modernization across your estate and creates consistent operating models also helps reduce talent and risk a skill risks that organization have. And interestingly, this is exactly where Red Hat also shines as it's the best hybrid cloud platform out there today. But coming back to the main objective around business objectives, we're seeing that when leaders anchor their transformation on such a holistic strategy, they are driving towards 2.5 times uh increased economic return as compared to let's say, just a you know, singular one single public cloud strategy. And they're able to drive impact on their business case across multiple dimensions. Things like accelerating the business or impacting top line new products services. Number two is around accelerating application development and optimizing costs associated with that estate, uh improving infrastructure, utilization, um reducing the cost of security and compliance. And that gives that architectural flexibility. But that was the basis of approach with clients like Delta and somebody used. Therefore cloud is absolutely about business outcomes. Both top line and bottom line. >>Yeah, really trying to change that operating model versus of the of the organization versus just the I. T. Model. And then we can talk about some of the headwinds that organizations face and maybe some of the typical challenges after they get to the to the cloud, whether its organizational technical, this integration, the security, maybe even culture. What are you seeing in that regard? >>Spot on. I think you've already started recognizing some of those, you know, when when uh clients started earlier in the journey, they started focusing on consumer driven innovation. They had digital and AI experimentation and we saw user applications moving to the glove. Now they are recognizing the need to look at enterprise driven innovation and how do you start embedding AI into the business at scale. And therefore they are now realizing that they need to look at their core portfolio, Their mission critical applications. You know, 90 of companies, Uh, we're on the cloud in 2019, but In all estimates only about 20 of their work lords actually move to the cloud. So, uh, there are a number of different challenges that our our clients face. You know, things like economic limits to how many work lords you can move to the public club, you called out security and regulatory challenges yourself speed to value or dealing with complex applications and the uncertain interactions, the data, gravity and dependencies. Sometimes they get into the loop of analysis. Paralysis. You know, another one that I get quite closely involved with this. Does the cloud technology transformation actually drive and deliver process change. Does it take your old business process and make it into an intelligent workflow? The other dimension is execution in silos today and Federated organizational constructs, the lack of the right skill and expertise and then finally is things like technology locking and and the struggle that people have with inflexible tools and methods which hinder scale and speed. So those are a few things >>when I think about just the history of cloud, modern cloud, you know, there was there was a lot of tire kicking early on and then the financial crisis actually accelerated some moves to cloud and then coming out of that there was a lot of shadow I. T. But was still, as you pointed out very early days. Uh and then you know, the comment you made about mission critical. It is kind of interesting to me because I'm curious as and you set out a vision before of what I call this, this layer of abstraction that hides the complexity. I don't care if I'm on prem in a public cloud across clouds. The edge. I I just I want you to take care of that in R and D. I want to worry about my business and so, so we're early days. Do people want to move their mission critical workloads to the cloud and why? Or do they just want to create a modernization layer and hide that complexity? You know, maybe in the context of some of those challenges that you can talk about. What are you, how are you advising clients that they take the next step in? And of course how IBM can help? >>Oh, spot on. So yes, I think now they're recognizing that there is value of looking at those complex core applications and looking at where should that what needs to happen to my complex core application? My mission critical applications. Do I need to uh defragment that? Do I need to decompose into uh new capabilities? Do I need to just move it to the cloud? Do I need to keep it where it is? Because in some instances that's where I get maximum security and data gravity. So if I reflect on this, I think there are four key things I would call out as what I would call the get rights. Uh Number one is ensure that we are aligning with business outcomes. Number two, clarity of target architecture and portfolio. Number three is accelerating the journey with the right methods, tools and patterns. And The 4th 1 which is closest to my heart is about delivering via an improved operating model. So let's let's just scratched the surface on this a little bit. Now, when you talk about aligning with business outcomes, first, of course is clear business ownership and alignment with the overall strategy. What's important is what capabilities does the business need to deliver that strategy and how is cloud going to help enable those capabilities? For example, you know, integration with ecosystem partners, faster launch of new products and services, monetizing data assets, things like that. And this was one of the key drivers for a health care company that I recently worked with in north America. When we talk about clarity of target portfolio, you know, this is about what's my architects are going to be across the edge on prem private, public. What should I do to my applications and where should they decide Should I keep, should I kill, should I modernize? What should I do? So for example, we've seen, you know, a lot of companies around 15 of applications. You may not touch at all. 20 of those applications you may replace with Saas solutions Uh 45-50 is where you start looking at modernizing and that's where you look at. What do you do with your monolithic applications and how do you modernize them? And around 15 you might say is building brand new native capabilities on the cloud. So that's kind of the second get right. The third was about accelerating with proven patterns and methods and tools and this is about increasing speed to value early wins and being able to analyze and decompose complex applications quickly and reliably and once they're executing on their journey, how do you grow from garage? Two skilled capabilities. Now here we've made some uh you know, strong focus and investments in this space. We have a set of standard patterns that allow you to modernize and migrate applications, you know, depending on looking at your operating system, the integration technology, the container standards and so on. And it's important to have the right tools that bring in AI and machine learning to bear. For example, we have our own, you know, card advisory tool that looks at the operating system and the code to explain and give guidance on what disposition and what container Ization is most applicable. And then finally, you know, this consistent operating model, how should the ways of working actually change on the ground? How should platform engineering and the application teams work together? Should I instant share that with a competency center that helps me get onto the journey, How do I have the right skills not being siloed? The consistent security approach, especially for companies that are looking at real complex mission critical workloads to them, that becomes even more important and in regulated environments. So to recap, I'd say those four things, alignment with the business clarity of target portfolio accelerating with the right methods and tools and of course embedding through a sustainable operating model cause they're >>Great, thank you for that. I would say my takeaway is this is not your grandfather's application rationalization exercise, which was a kind of a one shot deal every 10 years, oh y two K we're going to whatever it was and what you're describing is essentially a way to have continuous improvement. There's obviously a lot of automation there, but very importantly there's a gain sharing aspect where you can reinvest in innovation and I think, you know, one of the areas you mentioned is ecosystem, we haven't even talked about it, we don't have the time, but the whole data opportunity there for around innovation because that is how ecosystems they're gonna form around, you know, that data model and it's a it's a it's a new world and and ruin. Thank you so much for your very articulate vision that you set out and congratulations on all the progress that you've made and I really appreciate your time. >>Thank you very much. A wonderful to talk to you. Looking forward to more conversations. >>Alright. I am as well. And thank you for watching everybody's day volonte for the Cube. You're watching our continuous coverage of IBM think 2021 the virtual edition will be right back. >>Mm.