Building to Last- How Standard Chartered's Group CIO Balances Bold Innovation with Uncompromising Resilience CIO Leadership Live: ASEAN ยท 11 May 2026 Source: https://chrt.fm/track/3B598B/traffic.megaphone.fm/FCI4781843316.mp3 Transcript: https://podcasts.opennash.com/shows/cio-leadership-live-asean/building-to-last-how-standard-chartereds-group-cio-balances-bold-innovation-with-774efb/ (via OpenNash Podcasts, machine-generated) Welcome to CIO Leadership Live ASEAN. My special guest today is Guillermo Vega, Group CIO of Standard Chartered. In a relatively short time, he has led one of the more comprehensive transformation agenda I've seen, spanning people, platforms and client experience across the most complex global markets. What is particularly interesting is not just the scale of what he has delivered, but the way he has approached it, starting with leadership and culture, rethinking about client journeys end-to-end, and balancing innovation with resilience in a highly regulated environment. Today, I'll explore not just what he has built, but how he has led the change at scale. Guillermo, welcome. It's a real pleasure hosting you today. Thank you very much. How about you start by sharing with our CIO audience your background and career trajectory. How did you rise to become the group CIO at Standard Chartered? Thank you. Yes, absolutely. So I started at the Standard Chartered relatively, let's say, not a long time ago, in September 2023. I started as CIO for Wealth and retail bank. So with a mandate, let's say to improve innovation at the scale, improve our clients experience and actually simplify also technology. And I define a strategy around people, processes and technology that I can develop also further if you want. So that was when I started Standard Chartered after a while and actually one year ago I was promoted to Group CIO to actually expand this strategy also for corporate and investment bank and also for the group technology of the bank right so i could expand that that remy and bring the woodwork that we did at wealth and retail to the rest of the organization before that i worked as a head of technology and operations for santander in the wealth and insurance division so i gained experience not only on technology but also on the operation side that's essential to somehow drive join strategy and deliver outcomes and i had experience there around the asset management business also the wealth and the insurance business so before that it's my career is not let's say all life typical i would say financial institutions career because before that i was working for amazon in the early stages of Amazon Web Services. I was more on the business side for a technology organization, so I was working as a country head for a couple of markets. And before that is the beginning with my engineering background when I was working for Cisco as a systems engineer, designing all types of networking solutions, data center solutions from cyber to storage to switching, routing, etc. That was my beginning, I would say, as deep engineering roots. That's such a very yet stellar career you have, Guillermo. Now, in less than two years, you've led some of the most foundational technology transformation at Standard Chartered. You've mentioned you've moved from CIO of Wealth and Retail to become the Group CIO. I'd like to explore not just what you've achieved, but also how you've led it at scale. You started the bank's digital transformation by resetting leadership and culture before technology. Why Guillermo was it critical to begin with people and not platforms? That's a very good question and something that I learned some time ago and that confers me every time that I start with people. So my mindset in terms of leadership is to have a people-centric culture, because I believe that the transformation needs to be, let's say, thought and executed by the people. And we need to have the right skills to drive the transformation. So it's not very useful if we only think about technology and processes and what technology can bring if we don't have the right people to drive it. Right. So for me, people always goes first and to have the right, let's say, skills, the right operating model, give clarity to the people leaders and have the right people network is essential to any transformation and actually any project or delivery in the bag and probably in any organization. So the way I did it, not thinking only on the outcome, but the way I did it was want to look at the people leadership structure and what was the operating model. So when you look at an organization, you can see how the past history has somehow shaped the technology, the architectures, and the operating model. An organization has gone through acquisitions, The business models have changed. And then you can see how this alignment usually creates some silos. In the past, that was fine. We didn't have the technology tools to actually bring scale. But nowadays, scale and simplicity is extremely important, right? So how to make sure that we have an engineering organization with the adoption of agile, that's also one of the key, let's say, priorities. How to achieve it? I did a zero-based people transformation. So looking at the roles and the skills that I needed and what was the shape of the organization. And then the important was to be very mindful of the people's career and make sure that we were running a very, how to say, data-driven process to make sure everyone had the right opportunity to apply to the right roles. Why to start from the leadership? because the leadership will drive the rest of the organization. And why, for example, to include things like technical assessments and leadership assessments is because you can see that in many organizations, especially in the tech world, many people have become also people leader because it's the way to promote and to move forward in an organization. But sometimes they may perform better or they even prefer to be fantastic engineers, individual contributors. So one of the things was also to allow people to go back to individual contributor careers and actually allow them to thrive on what they are best at. At the same time, we had people with very good people leadership skills that we also wanted to invest and develop all that, let's say, leadership mindset. So it was to create an engineering culture and was also to create clarity on the roles and the operating model, making sure we were using chapters and we were removing all the silos and barriers from the teams. What would you say is the hardest part for you to drive this at scale? So I always think that the hardest part in any transformation, this is a people transformation and cultural transformation, but it also comes with other ones is how to bring the people along the journey. and what I've learned with the time is that one, you cannot rush many of the decisions and you need to bring the organization along because when you do something that may look slightly radical or that the organization is not used to it, you need to take the time to explain why are you doing, what are the pros and cons. This is the most difficult part of it. Now, you need to invest the time before executing. Otherwise, you cannot execute at the speed. Now, afterwards, of course, you need to execute at the speed because you don't want to have, let's say, a people transformation intention for a long time. You want to bring clarity. The people wants to know what's their role, what's their career. And this is probably the most challenging part. And then, of course, to have the right team, the right leadership, and also I would say to roll up a few sleeves, right? When you do a transformation like this one, you cannot just delegate and take all the decisions. You need to go very deep, be as data-driven as possible so you make the right choices. You would agree with me, Guillermo, that client onboarding is an area many banks talk about but few transform end-to-end. What leadership choices or trade-offs has enabled you to succeed in this initiative at scale in Southeast Asia and globally? Yeah, so client onboarding is, well, I would say it's a pending task for many organizations, right? It's very challenging because it touches directly the clients. It's one of the frustrations from the clients if you don't have, let's say, a streamlined onboarding. Many of the clients can drop from the process, also drives very high cost, let's say in operations and a lot of frustration from the business. So it's one of the areas of focus that we have in a standard chocolate and one of the first ones that we have transformed. For example, we had 85 % of activations were paper-based before, right? And how to achieve, now for example, 95 % of the onboarding is digital and 90 % is a straight-through processing. What it means is straight-through processing that actually doesn't require a human touch and it goes end-to-end as much as possible digitally. So removing the friction from our clients. So the way we approach the situation is in two folds. One is to make sure that the people that has the knowledge of the processes involved, for example, the relationship between technology and operations is extremely important because operations knows very, very well how the process is running and what are the pain points? Technology can find solutions for operations, but this relationship is extremely important that works well. Another one is not to try to do incremental, let's say, benefits, taking compromises on old systems and just, let's say, automating parts of the processes when the process may not be ideal or broken or a process from the past. It requires an end-to-end process redesign, thinking about it from scratch, and also being involved on the technologies that you're using, because in many cases, you actually need to use new technologies almost end-to-end. And then to make sure you take the client first and you're very centric on what are the friction points. So that client feedback on the onboarding is also very important. Thank you for outlining that in detail for us Guillermo. Now, as an international bank operating across fragmented regulation, infrastructure, data residency and maturity in Southeast Asia, what architectural or operating principles have helped you scale digital platforms across this region? Yeah, so we could take the approach that actually in the past, it was probably, I would say, the only way to do it that's trying to customize the solutions for the markets, for each of the markets, for each of the regulation, right? Because we have to recognize that every market is different. Even though in Asia, we can think that Singapore and Hong Kong, for example, they are similar. They have significant differences on client behaviors, what are their preferences, and also the regulation. So you could take the approach on customizing, having dedicated systems, but this one doesn't scale. It also brings resilience issues and also can bring security issues, right? So how to achieve that compromise between global systems and local nuances and customization goes around standardizing the core and then making sure that we're flexible at the edges, right? So we look not to standardize everything because that would not bring, let's say, the edge for the features that we require in each of the market. But let's make sure that those capabilities that are common, they are managed by a single system, ideally a global system that can provide those core capabilities. And those journeys, then they would connect through APIs. If you have an API-first strategy, would connect to those APIs that are common capabilities that you can reuse so you can drive that customization. And of course, to meet not only their local regulation, but their local needs. So I would say standardize the core, flexible, at the age, simplification as much as you can. Thank you. I love your strategy. Now from your CIO 100 Awards 2025 submission, I gather that you are driving AI adoption, launching regulated digital assets, trading platform and simplifying a complex legacy estate all at once. In this highly regulated market, where do you push the boundaries on innovation and where do you hold the line on resilience and risk minimization? So I always think they are not contradictory, right? We're a regulated organization, so we have no option and we care about our clients. So we want to make sure that resilience and risk and regulation, there is no compromise. There are ways to innovate without confronting with these concepts. There are many technical tools. For example, we can master client data. We can use the cloud. There are many ways to innovate and to make sure that at the same time we are resilient and we don't compromise on risk. So once this is all the innovation phase, to make sure we have the right ingredients to allow innovation. For example, we have clear objectives for innovation. We don't just want to innovate for the sake of innovation. We want to make sure there's the right atmosphere, the right skills. we have the right budget, but when it comes to implementation, we will not compromise on risk, resilience or regulation. At the end, part of the innovation cycle is adding the regulation as one of the inputs. Otherwise, it would be easier. Yes, I agree, but that's the challenge of innovation. Innovation is to take a difficult challenge and how to make it simple and how you can deliver on that charge. Guillermo, you would agree with me that fraud today is cross-channel, AI accelerated and socially engineered, especially in the mobile-first ASEAN markets. How has this changed your strategies for fraud detection? So I always think for JumpPol, AI is one of JumpPol in the past. It was also cloud. It was one of the drivers of innovation and growth. Both AI can be used, I would say, by the fraud, let's say, authors, right? The bad guys. And it can be at the same time by us. So we need to make sure that we're ahead of the curve. And we are also using the tools that some of the threat actors are also using. So, for example, if AI is accelerating, let's say, the fraud flows or thinking multichannel, we are counteracting, trying to be proactive and using similar tools to detect that fraud earlier. So for us, a proactive approach on how to combine all the data from multiple channels and run threat models is what we're doing now. So we're trying to innovate and be ahead of the curve. Also looking at multi-channel data driven approaches to make sure fraud is not something that take us out of work. I also understand that you're already pioneering the use of AI in software development lifecycle. And many banks are already exploring agentic AI. Are you also doing that? Yes, absolutely. And this is one of my passions, right? It's one of the things that I enjoy the most, I would say, because I can see the amazing, let's say, benefits that we can have and how our developers can now also focus on higher value tasks. So we're definitely working on AI for SDLC, not only looking at, I would say, the pure software development lifecycle, but starting from drafting what are the requirements. So we're partnering also with the business to make sure that the end-to-end delivery is also powered through AI. So we have an internal AI platform to make sure that, of course, the use of AI, we have ethical AI, we don't run any risk, any security, let's say also risk, and how to enable AI for the, let's say, not only the developers, as I said, for all the people that's involved in the delivery. We're seeing amazing results, and we are also making sure that the AI is somehow augmenting the capabilities of our developers. This is also an important concept. We don't see a replacement. We see a tool, how we can develop 10 times faster, how we can somehow code security by design or some controls earlier and we can have less mistakes or less bugs when we go into production. So we're making sure now and we're looking on how to scale AI safely for all our developer communities. We have thousands of developers in the organizations and we need to make sure that this scales safely and efficiently to all our delivery community. Tell us, Guillermo, where should we draw the line between automation and autonomy? It's a good one because sometimes the terms get confused, right? So I would say that we had automation for a very long time. We have automation tools. And what AI is bringing us is so autonomy, so autonomy. And what I mean with autonomy, it means that AI, based on probabilities, can decide the next best action. It's not an automation that's very deterministic, well-defined. If the input is A, the output will be Y. In this case, autonomy brings a lot of opportunities, but also brings a lot of risks if, let's say, the AI model do not have all the inputs that are required. So nowadays, we are testing autonomy. For example, when we have a platform that's for monitoring of all of our systems, applications, infrastructure, and we're having all those trillions of data inputs to understand earlier what's happening when something fails. Now, we're testing autonomy in terms of how the AI can suggest a possible resolution. but we are also looking at the plus radius of a possible, let's say, autonomy mistake because it can be a disaster. We don't want to bring the clients down. So we're still on the testing phase to see how much autonomy and what guardrails, and the word guardrails is extremely important with AI, what guardrails are we giving to the AI to make sure we can let the AI to be as autonomous as possible. So today, I would say the autonomy is for low risk tasks, but there's always with human supervision. So that's the phase that we are now. I'm sure that this level of comfort with AI will start increasing. We'll find ways to give more information to the AI to make more autonomous decisions. But as I said before, we don't compromise on risk. with uncompromised on resilience and with uncompromised on regulation. So we're taking this concept of autonomy very careful and step by step. Thank you so much, Guillermo. Now, traditional risk and compliance frameworks were built for deterministic systems. How have you had to rethink model risk assessment as AI becomes more probabilistic and conversational? Well, I think it's clear we need to look at the frameworks, right? Because I totally agree. The frameworks are very used to be able to explain in a very deterministic way what is the behavior. So now we're looking at the frameworks and finding ways, one, to make sure that the accountability is still with the humans, is still with us. Even if we use AI, we cannot just defer accountability. It didn't happen in the past. I don't think it will happen in the future. We need to make sure that the accountability is still where it has to be. The other one is making sure that we prove that it's not only about accuracy in a deterministic model, but it's also the right behavior. So we can prove that the behavior is consistent with the framework, with what we want. Making sure there are the right guardrails, making sure that the right inputs provide the right outputs, but not only assessing inputs, outputs, and the accuracy, but also the behavior of the tool. And for that, we also need to adapt the framework. Now, of course, also, we need to work with regulators because regulators also expect deterministic outcomes for many of the processes. So we need to be able to explain why there is a result. And if, let's say, the behavior is unpredictable and we cannot explain it, we cannot just use it. It's not acceptable for us. It's not acceptable for the regulators. So it's about relooking at the framework, but also running enough tests and enough guardrails so we are comfortable with the behavior of the AI. Thank you, Guillermo. Now, looking back on your journey to become Group CIO of Standard Chartered, what capability and mindset has helped you succeed? So I think the capability and mindset, it's been one, people first. But I always have put as a priority to make sure there's the right leadership culture, there's the right leadership skills, and how people can help me to scale. I always think that my role is to make sure the team has the right conditions to succeed, to scale and to perform. So I think having that focus is one of the key, I would say, skills to succeed. Another one is think long term. So I believe it's very difficult to think long term with the fast cycles that we have in the financial industry with our quarterly, let's say, results and the pressure that we have not only from clients, but also from regulators and from our investors. But to keep that long term thinking, it also pays back. So not only thinking on the short term, how to achieve the next quarter delivery, it's something that in the long run proves that sustainable, I would say, innovation and to make the right decisions. This is one of those because you also want that the transformation, for example, is repeatable. What I always think on, what do I need to do that transformation is repeatable? how I need to make sure that one transformation is real transformation, not incremental, I would say, improvements, and how I make sure that this transformation can be structural, not automated, but somehow it can scale. It doesn't depend on heroics or it doesn't depend on single individuals. I think those are probably key things. And also, I'm thinking about simplification, right? Simplification is an important concept. Simplification, as I said before, without losing customization, right? Nowadays, technology can give us higher levels of customization while running simplification. Simplification also in the long run allows us to have less maintenance, to dedicate more budgets to innovation, less to BAU, I would say, maintenance tasks, allow us to run more resilient systems, focus on less systems, more critical, and run upscale, I would say, resilience, and focus on the right things rather than having a dispersed, extremely complex landscape of systems or applications. So simplification is something that I always have in my mind, and in the decision process. Thanks Guillermo. What guidance would you offer to CIOs who are stepping into enterprise-wide leadership roles like yours? So I would say that very similar to what I answered in the previous question, right? One is, so if I have to reinforce things for newer CIOs, I would say one, be patient. Why don't try to rush? I've seen many CIOs, and we also have a lot of CIOs, of course, in Standard Charter, that try to rush decisions, try to deliver results very, very fast. I would say find the right balance between low-hanging fruits and the long term. Get your principles right and discuss them in advance with the rest of the organization. CIOs is not a role that you can do and succeed individually. You're providing a service to the business, you're providing a service to the clients, and you're working with regulators all day long. So make sure you bring, let's say, the people along. And let's make sure you have very clear scorecards and what you want to achieve and focus on that path. And again, don't focus only on the short term. Thank you, Guillermo. That was a truly insightful conversation. Thank you very much, Estelle. That's a pleasure. What stands out to me is your clear focus on building transformation from the inside out, starting with people and culture, great imagining, client journeys, and creating platforms that can scale across complex and diverse markets. Equally, your emphasis on balancing innovation with discipline, whether in AI, digital assets, or simplifying legacy systems, is a powerful reminder of what leadership should look like in today's environment. While CIO audience, the takeaway is clear. Sustainable transformation is not just about moving fast, as Guillermo has shared, but also about building with clarity, resilience and long-term intent. Thank you for joining us today. Thank you very much. It's been a pleasure.