Embracing culture change on the path to digital transformation

Meanwhile, young financial services companies were coming to market with innovative products and services and NAB was finding it difficult to compete. “Many customers today are expecting an Amazon experience, a Google experience, a Meta experience, but we were still operating in the 1990s,” says Day. “We stood back, and we looked at it, and we decided that our entire culture needed to change.”

What ensued was nothing less than an internal transformation. “Our original teams didn’t have a lot of tech skills, so to tell them that they were going to have to take on all of this technical accountability, an operational task that had previously been handed to our outsourcers, was daunting,” says Day.

Day and his team rolled out a number of initiatives to instill confidence across the organization and train people in the necessary technical skills. “We built confidence through education, through a lot of cultural work, a lot of explaining the strategy, a lot of explaining to people what good looked like in 2020, and how we were going to get to that place,” says Day.

This episode of Business Lab is produced in association with Infosys Cobalt.

Full transcript:

Laurel Ruma: From MIT Technology Review, I’m Laurel Ruma. And this is Business Lab. The show that helps business leaders make sense of new technologies coming out of the lab and into the marketplace. Our topic today is digital transformation. Most organizations have begun the journey to digitize their services and operations, and some are further along than others in bringing disruption to the marketplace. How do you bring transformation to organizations that are in highly regulated, service-based industries where competitive differentiation requires innovation?

Two words for you, internal transformation.

My guest is Steve Day, the chief technology officer of enterprise technology at National Australia Bank.

This podcast is produced in partnership with Infosys Cobalt.

Welcome, Steve.

Steve: Thank you, Laurel. It’s a pleasure to be here.

Laurel: National Australia Bank or NAB is undergoing a significant digital transformation. Gartner recently found that IT executives see the talent shortage as the largest barrier to deploying emerging technologies, specifically cloud-based technologies, but NAB uses insourcing. Most listeners are familiar with outsourcing, what exactly is insourcing and how does it relate to outsourcing?

Steve: Yeah. I think it’s all in the name. Insourcing would be the exact opposite of outsourcing. And to give you a little bit of history, National Australia Bank, like many banks, decided to outsource a large part of its operations in the 1990s. We basically pushed all our operations and a large part of our development capability out to third parties with the intent of lowering costs and making our operations far more process driven. I think those two objectives were achieved, but we did have an unintended consequence. We basically froze our operations in time, and that created a situation. If you roll forward to 2018, we realized that we were still operating like we’re in the 1990s. We were very waterfall driven. Our systems were highly processed driven, but in a very manual way, and it took us a very long time to roll out new products and services that our customers really needed.

It was about at that time that we realized we needed to do something different. We spoke with our outsources, of course, but to be honest, they weren’t motivated to reduce our internal costs and to help us become far more agile. They were very happy for us to be paying them large amounts of money to do large amounts of work. So at that point, we decided to bring our capability back into the business.

Laurel: So waterfall being the opposite of agile, right? You were finding that was hindering your progress as a company, correct?

Steve: It really was hindering our progress. We were very slow. It took us years to roll out new products and services. We had some young financial services companies knocking on the doors, startups, and the like, that were agile and able to compete really quickly, and we needed to change. We needed to look at a different way to roll out our products so that we could give customers what they’re expecting. Many customers today are expecting an Amazon experience, a Google experience, a Meta experience, but we were still operating in the 1990s. That’s when we really pushed our call too. We stood back and we looked at it, and we decided that our entire culture needed to change.

We did that by building a series of tech guilds. We built a cloud guild, a data guild, an insourcing framework. We built our NAB Engineering Foundation and with a goal of building a culture of innovation of cloud, of agile, and being able to deliver great products and services to our customers in a cost effective, but very safe way. And as part of that, we started on our cloud migrations and that is really moving at pace now.

Laurel: Insourcing seems to be working so far, but it didn’t happen overnight, as you said. And even though 2018 wasn’t that long ago, what was the journey like to first realize that you had to change the way you were working and then convince everyone to work in a very different way?

Steve: We did realize that if we didn’t get the culture embedded that we would not be successful. So building that capability and building the culture was number one on the list. It was five years ago. It feels like a very long time ago to me. But we started that process and through the cloud guild we trained 7,000 people in cloud and 2,700 of those today are industry certified and working in our teams. So we’ve made really good progress. We’ve actually moved a lot of the original teams that were a bit hesitant, a bit concerned about having to move to this whole new way of working. And remember that our original teams didn’t have a lot of tech skills, so to tell them that they were going to have to take on all of this technical accountability, an operational task that had previously been handed to our outsourcers, was daunting. And the only way we were going to overcome that was to build confidence. And we built confidence through education, through a lot of cultural work, a lot of explaining the strategy, a lot of explaining to people what good looked like in 2020, and how we were going to get to that place.

Laurel: NAB’s proportion of apps on public cloud will move from one third to about 80% by 2025, but security and regulatory compliance have been primary concerns for organizations and regulated industries like healthcare and financial services. How has NAB addressed these concerns in the cloud?

Steve: Initially, there was a lot of concern. People were not sure about whether cloud was resilient, whether it was secure, whether it could meet the compliance requirements of our regulators, or whether the board and our senior leadership team would be happy to take such a large change to the way we did business. We actually flew the board over to meet with many of the companies in the Valley to give them an idea of what was going on. We did a huge education program for our own teams. We created a new thing called The Executive Guild, so that middle management would have a great feel on what we were doing and why we were doing it. And as part of that, we created a set of tools that would help us move safely.

One of those was CAST, a framework that we use to migrate applications to cloud. CAST stands for Cloud, Adoption, Standards, and Techniques. And it really covers all the controls we use and how we apply those controls in our environment to make sure that when we migrate applications to cloud, they are the absolute safest they can be. It’s safe to say that when we built CAST, we actually did an uplift in our requirements. That enabled a lot of people to see that we were taking it very seriously, and that it was actually quite a high bar to achieve this compliance. But we were willing to invest, and we invested a lot in getting the applications to that level.

Another thing we did was build compliance as code. Now, infrastructure as code, what cloud is built on, allows you to then create compliance as code. So all of the checks and balances that used to be done manually by people with check boards, I used to say, are now being done in the code itself. And because a server is no longer a piece of tin in the corner, it’s an actual piece of code itself, a piece of software, you can run a lot of compliance checks on that, also from software.

A third thing that we did to give everyone a sense of comfort is we didn’t pin the success of NAB to the success of any one cloud company. We came up with a public, multi-cloud strategy, and that meant that at least for all our significant applications, we would run them on two different cloud providers. Now that would be expensive if you did every cloud in the most robust way, which would be active-active across both clouds. So we created our multi-cloud framework, which was about categorizing each application across multi-dimensions, and then assigning that workload to one of six multi-cloud treatments. Multi-cloud treatment one being, basically no multi-cloud, it’s an app for convenience. It doesn’t really matter if that application goes away. We allow that to sit in one cloud all the way through to our most critical applications, which we insist on running active-active across both clouds. And in our case, that would be MCT6. So given all of those frameworks, the tools, and the focus that we put on that, I think we gave the organization and the leadership at the organization some confidence that what we were doing was the right move and that it would give us our ability to serve customers well, while also remaining safe.

Laurel: How has cloud enabled innovation across NAB? I can see it in the teams and you’ve even upskilled executives to be comfortable with technology and what agile means and how you’re going to change the way that things are done. But what else are you seeing that’s just brought some kind of a particular efficiency that is a particularly proud moment for you?

Steve: I think I would go back to that description I just gave you about infrastructure as code being an incredible enabler of innovation. I mentioned compliance as code, but there’s also all kinds of operational innovation that you can perform when your infrastructure is software rather than hardware. Just being able to replicate things very quickly. The fact that you can have as many development environments as you need to develop your applications quickly and efficiently, because when you’re finished with them, you just turn them off and stop paying for them. The fact that we can move to serverless type applications now that don’t actually require any infrastructure sitting below them and enable our application team to not have to interact with anyone and just get on and develop their applications. Things like grid computing, which create massive computing power for a short burst of time. You pay a lot, but you only pay a lot for a very short amount of time. So you end up paying not very much at all. But to achieve massive things in predicting what the market’s going to do at times of concern and things like that.  Infrastructure-aware apps, some of the amazing things we are doing in cyber at the moment to understand cyberattacks, to be able to thwart them in a much more elegant way than we have in the past. Financial operations that enable us to take control of the elasticity of that cloud environment. And all of those things sort of add up to this platform of innovation that people can build things on that really create creative innovation.

Laurel: And how does that turn into benefits for customers? Because user experience is always an important consideration when building out tech services and as you mentioned, customers certainly expect Google- or Meta-like experiences. They want online, fast, convenient, anywhere they are, on any device, so how is something like artificial intelligence at an ATM serving both the need for improved security and improved user experience?

Steve: Great question. I think for improved security, fraud is a great one. There are so many scams going on right now, and AI has really enabled us to be able to detect fraud and to work with our customers, to prevent it in many cases. We’re seeing patterns of fraud or the ways that fraudsters actually approach their victims, and we’re able to pick that up and intervene in many cases. Operational predictions on things that are going to fail or break. And then things that are just better for customers like faster home loans. A large number of our home loans are approved in under an hour now because the AI allows us to take calculated risks, basically to do risk management in a really fast and efficient way. And then there are small things. There’s some great stuff like if I get a check, I just take a picture of it from my banking app on the iPhone and it’s instantly processed. Those sorts of things are really leading to better customer experiences.

Laurel: That’s my favorite as well, but a home loan under an hour, that’s pretty amazing.

Steve: And that’s because we have a history of what that customer’s done with us. We no longer have to have that customer fill in large surveys of what their monthly spending is and what their salary is and all of that. We have all that data. We know all that about the customer and to have to ask them again, is just silly to be frank. We can take all that information and process it directly out of their account. All we need is the customer’s permission. The open banking legislation and things that have come through at the moment that allow us to gain access to information with the customer’s permission through their other financial services, that also enables us to have a good understanding of that customer’s ability to meet their repayments.

We also do a lot of AI on things like valuations. The amount of AI going into valuing the property now is absolutely incredible. In the past, you’ve had to send somebody out to a house to do the valuation so that they can appreciate things like road noise, right? How much road noise does that property have? What are the aspects of that house? And through being able to look at, say, Google Maps and see how many cars per hour are flowing past that house, what the topology of the landscape is around that house, we can actually do calculations and tell exactly what the road noise is at that property. And we’re able to use layers and layers and layers of information such as that and that goes along with, is the house on a flood plain? Is the house overflown by aircraft, what material is the house made of? We can pick all of that from satellite imagery. Does it have a swimming pool? Does it have solar panels? We can gather a lot of that and actually do the valuation on the property as well, much faster than we have in the past. And that enables us to then provide these really fast turnarounds on things like home loans.

Laurel: That’s amazing. And of course, all of that helps keep innovation up at the bank, but then also improve your own efficiencies and money. Making money is part of being a business. And then you put the money back into making better experiences for your customers. So it’s sort of a win-win for everyone.

Steve: Yeah, I think so. I haven’t loaned money for a house since all of that has been put into place, but I’m really looking forward to the next time I do and having such a good experience.

Laurel: Collaborating with your customers is very important and collaborating with your competitors could be as well. So NAB teamed up with cloud providers and other global banks on an open digital finance challenge to prototype new banking services on a global scale. Why did NAB decide to do this? And what are some of the global financial challenges this initiative was looking to solve?

Steve: I think creating great partnerships to encourage innovation is a path forward. Like everything, we don’t have a monopoly on great ideas. And I think if we limited ourselves to the ideas we came up with, we wouldn’t be serving our customer’s best interests. Searching globally for great ideas and then going through a process of looking to see whether they can actually be productionized, it’s a great way of bringing innovation into the bank.

My favorite at the moment is Project Carbon, which is seven banks around the world all getting together to create a secure clearinghouse for voluntary carbon credits, which if you think about that and where the world’s going and how important that will be going forward, it’s just absolutely wonderful that we’ve got this situation being built today. But yeah, there’ll be things that create more secure payments, faster payments, more convenient payments, more resilient ledgers, and I mentioned faster home loans, etc. It’s just an exciting time to be in the industry.

Laurel:  And to be so open and willing to work with other folks as well. What else are you excited about? There’s so much innovation happening at NAB and across the financial services industry, what are you seeing in the next three to five years?

Steve: I’m seeing a faster pace of change. One of the things I’m aware of at the moment, things are changing so fast, that it’s really hard to predict what is going to come up in the near future. But one thing we know for sure is we will need a platform that enables us to pivot quickly to whatever that is. So I’m actually most excited about the opportunity to build a platform that is incredibly agile and allows us to pivot and to move and to exploit some of these great ideas that are coming in from global partners, or internally or wherever they’re coming from. Our new graduates come up with quite a few themselves. How do we get those ideas to production really quickly in a safe way? And I think that is what really excites me is the opportunity to build such a platform.

Laurel: Steve, thank you so much for joining us on the Business Lab. This has been a fantastic conversation.

Steve: Thank you, Laurel.

Laurel: That was Steve Day, the chief technology officer of enterprise technology at National Australia Bank, who I spoke with from Cambridge, Massachusetts, the home of MIT and MIT Technology Review overlooking the Charles River. That’s it for this episode of Business Lab. I’m your host, Laurel Ruma. I’m the director of Insights, the custom publishing division of MIT Technology Review. We were founded in 1899 at the Massachusetts Institute of Technology. And you can find us in print, on the web, and at events each year around the world. For more information about us and the show, please check out our website at technologyReview.com.

This show is available wherever you get your podcasts. If you enjoyed this episode, we hope you’ll take a moment rate and review us. Business Lab is a production of MIT Technology Review. This episode was produced by Collective Next. Thanks for listening.

This content was produced by Insights, the custom content arm of MIT Technology Review. It was not written by MIT Technology Review’s editorial staff.