OpenNashPodcasts

Banking Transformed with Jim Marous

How U.S. Bank is Building a Resilient Digital Bank

13 May 2025 · 44m · Dominic Venturo, Jim Marous · 26 quoted facts

▶ Play episodeOriginal source ↗

In brief

Dominic Venturo, U.S. Bank's chief digital officer, argues that resilience in banking is no longer just about uptime and disaster recovery. It is the ability to adapt quickly to changing customers, markets and technology. Banks get there by redesigning how they build products, how they plan, and how they use customer feedback, so changes ship in months instead of years.

The main tension is between speed and control. Venturo says rapid change works only if risk, compliance, engineering and product people sit together from the start, with success criteria set in advance. The same logic applies to generative AI, which he sees as a way to remove routine work so staff can focus on what sets their bank apart.

Key insights

  1. Resilience now means adapting, not just staying online

    Venturo says uptime, failover and backup power are only table stakes. Real resilience is bouncing back from competitive, market or technical shocks, such as the 2023 deposit crisis, by changing products fast.

  2. Product planning cut from 18 months to months

    Venturo says building a new offer used to take about 18 months of financial planning, product planning and engineering. After changing the technology stack and delivery model, U.S. Bank can ship from a whiteboard idea to production within one quarter.

  3. Set success criteria before launching any pilot

    Venturo says teams should pilot, test and kill products that do not work, with success criteria fixed in advance. Otherwise people move the bar later and keep 'zombie products' alive because of money already spent.

  4. Starting from zero fields simplified account opening

    When teams could not agree on which fields account opening needed, an executive removed all of them and made each addition prove it was mission critical. Venturo says the result was a handful of fields, and Marous jokes it is now two.

  5. Generative AI's big win is unglamorous back-office work

    Venturo says banks will not build their own large language models but can train existing ones on their policies and documents. The largest gains, he says, come from reading unstructured documents and removing key entry, freeing staff for customer conversations.

Questions

What does resilience mean for a bank, according to U.S. Bank?

Venturo says it includes the technical basics like uptime, geographic diversity and automatic failover. It also means being able to adapt quickly to competitors, market shocks and changing customer expectations.

How fast can U.S. Bank bring a new product to market now?

Venturo says the bank can go from a whiteboard idea to a version in production within a quarterly planning cycle, with multiple releases per quarter. He says this used to take about 18 months.

Why did U.S. Bank strip the fields out of its account-opening form?

Teams could not agree on what information was required for credit card, checking and savings accounts. An executive removed all the fields and made each one earn its place, leaving only a handful.

How is generative AI useful to a bank, according to Venturo?

He says banks can take an existing open-source language model and train it on their own policies and documents, so it answers within the bank's rules. It can also read unstructured documents like tax returns and enter the data, so people only review it.

What should a smaller bank do first to become more resilient?

Venturo says to build a product-focused organization with product owners who gather data and signals, and to make data-driven decisions rather than defer to the most senior person. He also suggests bringing risk, compliance and technology together to prioritize vendor capabilities.

Facts

Stated by the speakers. Each quote matches the transcript, which shows what was said, not that it is true.

Dominic Venturo says U.S. Bank grew from about 20-some thousand employees when he joined roughly 26 years ago to about 70,000 employees.

“We had 20-some thousand employees when I joined, and we have 70 ,000 employees now, so a little bit different over the years.”

0:01:55 · Dominic Venturo · Employee growth

Dominic Venturo says U.S. Bank created its Innovation Group about 14 years ago as part of its payments organization.

“I think the big change in my career was probably about 14 years ago when we created the Innovation Group at the bank, and that was part of the payments organization.”

0:02:26 · Dominic Venturo · Innovation Group

Dominic Venturo says U.S. Bank's early innovation group used a three-horizons approach, building prototypes, testing them with customers and then bringing them to market.

“thinking about the three horizons innovation, thinking about always looking up and over the horizon, doing applied research and development to build prototypes, to test them with customers, and then begin to bring them to market”

0:03:10 · Dominic Venturo · Innovation method

Dominic Venturo says he has run U.S. Bank's digital organization for about four and three-quarter years.

“And for the last four and three quarters, I guess, years, I've had the privilege to run what we call the digital organization at U.S. Bank.”

0:03:49 · Dominic Venturo · Digital organization

Dominic Venturo describes 'zombie products' as offerings banks keep alive despite little traction because they have already spent heavily on them.

“Which is why you see a lot of what I'll call zombie products that are around, which is, you know, we spent a lot of money on it and never really got traction”

0:06:44 · Dominic Venturo · Zombie products

Dominic Venturo says U.S. Bank invested in API development platforms and microservices years ago after seeing fintechs and technology firms move to well-documented APIs.

“we decided to invest in API development platforms and also the microservices capabilities within our technology architecture that would allow that to happen”

0:11:18 · Dominic Venturo · API investment

Dominic Venturo says U.S. Bank can take a well-defined idea to a production version within one quarterly planning cycle.

“we can go from this well-defined thing on a whiteboard that we want to do to a version of it that's in production within a quarterly planning cycle, which is pretty impressive.”

0:12:23 · Dominic Venturo · Delivery speed

Dominic Venturo says customer feedback showed that growing use of password managers caused login problems on banking websites, prompting U.S. Bank to redesign how passwords are entered.

“as the advent of people using password managers more often actually caused some problems with the way passwords are entered on banking websites”

0:13:24 · Dominic Venturo · Login redesign

Dominic Venturo says U.S. Bank has A/B testing capability that lets it deliver a change to a subset of customers and measure results before a full launch.

“we also have built A-B testing capability. So we can have a hypothesis, we can build a change, we can deliver it to a subset of customers and see if it actually performs better before we launch it to the entire organization.”

0:14:01 · Dominic Venturo · A/B testing

Jim Marous says WeBank, which he visited in Shenzhen, China, used four parallel cloud platforms to test ideas and innovated on a 14-day cycle.

“they had four parallel cloud platforms that allowed them to test new ideas instantaneously. They innovated on a 14-day cycle, very close to the time period you're looking at”

0:16:55 · Jim Marous · WeBank innovation

Dominic Venturo says U.S. Bank's digital account-opening team cut the data fields from about 16 to zero, then added back only mission-critical ones, ending with a handful.

“we're going to go from whatever it was, 16 to zero. And then each one that we add has to be mission critical to the objective. And we ended up with just a handful.”

0:20:40 · Dominic Venturo · Account opening

Dominic Venturo says U.S. Bank can now open a new account with two fields of information, with help from technology partners.

“Two fields of info, we can do a new account. Right. With some help from some technology partners.”

0:21:54 · Dominic Venturo · Account opening

Dominic Venturo says U.S. Bank built a banker-facing interface that is essentially the same as the customer interface, letting it reuse code and avoid maintaining separate systems.

“to build an interface for what we call the banker experience that is basically the same interface that the customer uses.”

0:22:25 · Dominic Venturo · Banker experience

Dominic Venturo says many smaller banks rely on core processing or card platform vendors for new capabilities.

“And I know that a lot of, especially the smaller banks, rely on either a core processing vendor or a card platform vendor and the like.”

0:25:52 · Dominic Venturo · Bank vendors

Dominic Venturo says the failure of SVB and other banks produced a deposit crisis that forced banks to make attracting deposits easier and bundle products differently.

“we saw as an industry a pretty significant change when we had the failure of SVB and the other banks. We had sort of the crisis of deposits, for lack of a better description.”

0:29:22 · Dominic Venturo · SVB failure · 2023

Dominic Venturo says U.S. Bank has spent about six years modernizing its architecture and systems, including moving digital applications to cloud-native designs.

“which we've been on that journey for the last six or so years, is modernizing the architecture, modernizing the systems where we can, moving to cloud-native applications in the digital space”

0:30:19 · Dominic Venturo · Modernization

Dominic Venturo says launching a product at U.S. Bank used to take about 18 months because of sequential financial planning, product planning and engineering.

“Because you do your financial planning, then you do your product planning, then you do your engineering, then it would take 18 months.”

0:31:22 · Dominic Venturo · Product timelines

Jim Marous says generative AI did not emerge publicly until November 2022.

“it is amazing in my mind to think that Genre of AI didn't raise its head until November 2022.”

0:31:59 · Jim Marous · Generative AI · 2022

Dominic Venturo says generative AI's breakthrough was enabled by cloud computing and improvements in network infrastructure.

“Part of that was enabled by cloud. Part of that was enabled by network infrastructure improvements and the speed at which we can communicate between where we are and where the cloud is.”

0:33:23 · Dominic Venturo · Generative AI

Dominic Venturo says earlier machine learning models at U.S. Bank were used for image analytics, check processing, fraud, and detecting networks of criminal actors.

“They allowed us to do things like advanced image analytics and check processing and fraud. They allowed us to do things like network detection, not the Internet, but networks of actors in things like fraud prevention”

0:33:57 · Dominic Venturo · Machine learning

Dominic Venturo describes starting with an open-source large language model and training it in the bank's own environment on a knowledge base of policies and documents.

“You start with an open source, a large language model, and then you train it in your environment on a knowledge base, a set of information.”

0:35:00 · Dominic Venturo · Training AI models

Dominic Venturo says banks will probably not build their own large language models because of the money, computing and power required.

“banks probably aren't going to build a large language model because that takes an enormous amount of money and compute and power and the like.”

0:36:41 · Dominic Venturo · Large language models

Dominic Venturo says one-to-one personalization has been hard because bank data is always dated, such as last month's transactions.

“a lot of the reason that that has been very difficult to do is because the data is always dated.”

0:37:04 · Dominic Venturo · Personalization

Dominic Venturo describes unstructured data as information not held in a database, such as financial statements and tax returns, which generative AI can read and extract.

“unstructured data, if you're not familiar, is just not a database. So financial statements, tax returns, people put them in different forms.”

0:37:37 · Dominic Venturo · Unstructured data

Jim Marous says U.S. Bank ranks about fifth among U.S. banks by asset size.

“you're at, I think, number five as far as size of assets.”

0:39:36 · Jim Marous · Bank size

Dominic Venturo says U.S. Bank uses co-browsing and does not force customers into a particular channel.

“We do co-browse and we don't force people into a channel.”

0:40:50 · Dominic Venturo · Customer channels

Chapters

  1. 0:01:55Venturo's career and the birth of U.S. Bank's innovation group

    Explains how a payments-side innovation team set up 14 years ago grew into the digital organization Venturo leads today, which shapes his view of speed and resilience.

    “I joined US Bank a little over 26 years ago.”
  2. 0:06:12Redesigning product development to pilot and kill ideas

    Shows why speed requires re-architecting the whole product and software lifecycle, with risk and engineering involved up front and success criteria set in advance.

    “build something, pilot it, test it, and kill it if it doesn't work”
  3. 0:12:23Resilience as competing and adapting quickly

    Contrasts back-office uptime with the broader idea of resilience, using early API investments and quarterly delivery cycles as evidence.

    “in production within a quarterly planning cycle”
  4. 0:13:24Customer feedback loops and A/B testing

    Describes how call center, chat and survey signals feed product teams in near real time and are tested on subsets of customers before wider launch.

    “what folks are having a problem with login over and over and again”
  5. 0:20:40Account opening cut from sixteen fields to a handful

    A concrete story of breaking consensus gridlock by starting from a blank page, and of reusing the same interface for bankers and customers.

    “Let's take all the fields off the table.”
  6. 0:25:25Advice for smaller banks: product ownership and data

    Venturo says smaller institutions should build product-owner thinking and data-driven decisions, and use a prioritization model to adopt vendor capabilities safely.

    “so that it isn't the most important person in the room deciding what to do next”
  7. 0:31:22Preparing for shocks like the SVB failure

    Argues that no one can predict crises, so the answer is modern architecture and planning that shrink delivery from 18 months to months.

    “then it would take 18 months”
  8. 0:35:33Generative AI in banking beyond the hype

    Venturo explains why generative AI took off, how banks can train models on their own rulebooks, and how it can handle unstructured documents.

    “Banks and credit unions. Documentation.”
  9. 0:41:10Differentiating by removing what distracts from purpose

    Venturo ties digital enablement to freeing time for personal, consultative service and urges banks to automate or simplify whatever does not set them apart.

    “find the things that distract you from your purpose and get rid of them”

Transcript

0:00:11
Jim Marous

hello everyone we've gone through this before we've gone we've had events you've seen me more than you ever wanted more than i want to see myself um this could be a great session um our our podcast today that we're recording and we'll actually publish it on both the audio podcast channels as well as YouTube is with a person who actually I've known even back before the financial brand who we've interviewed, I think, four times and has continually performed better than almost anyone else we've ever interviewed on a consistent basis.

0:00:46

My friend, Don Venturo from U.S. Bank is an innovator. And we'll talk a little bit about his journey because I think it's very interesting for marketers to realize the progression of where the business is going because he's on the cutting edge. I do want to also spend some time thanking Naehas for their sponsorship of this podcast. Without them, none of this would have been possible. So without further ado, I'd like to introduce Dominic Venturo. So Dom, as I mentioned, we've had you on the podcast.

0:01:13

We've interviewed you live two years ago at the Financial Brand Forum at a room that had nobody in because that's the way we did it back then. A little bit about your background. Can you talk about where you started, at least with U.S. Bank and maybe even before, and where you are today?

0:01:31
Dominic Venturo

How much time do you have? I've been at this for a long darn time. I guess the easiest way to think about it is I'll break it up into chunks. So I spent the first about 10 years with Bank of America and its predecessors on the West Coast. And I started in banking. A lot of people don't go to school to go start to be a banker. I actually did that. I did as well. So we had that in common.

0:01:55

Yeah. And so I started out in a training program and worked my way up through the ranks. But I quickly discovered that I really liked product, product management, product design. And so I spent an awful lot of time in the product side of the world. I joined US Bank a little over 26 years ago. So that's quite a long time. I think We had 20-some thousand employees when I joined, and we have 70 ,000 employees now, so a little bit different over the years.

0:02:26

A few mergers in between, acquisitions and the like. But from a career perspective, I've been in product. I think the big change in my career was probably about 14 years ago when we created the Innovation Group at the bank, and that was part of the payments organization. one of the things that we talk a lot or Jim talks a lot about is the competition from the fintechs the emerging the speed at which they change and if you can believe it or not way back when we created the innovation group that was the impetus for what we were doing I was in the payments organization and what we saw was the emergence of emergence of companies that were using new technology

0:03:10

stacks, new delivery models, and new capabilities to be able to rapidly build and deliver products and bring them to market. And our whole thinking at the time was we need to learn what's working there, and then we need to develop a way to be able to get that into our culture and our DNA as a company. And we started in the payments business with that mindset. So thinking about the three horizons innovation, thinking about always looking up and over the horizon, doing applied research and development to build prototypes, to test them with customers, and then begin to bring them to market were the early days of the innovation.

0:03:49

And for the last four and three quarters, I guess, years, I've had the privilege to run what we call the digital organization at U.S. Bank. And that organization just very simply is consumers, small business, and institutional customers, the digital solutions that serve them. So I'll just keep it simple. And then we still have the innovation practice. And then I also have the artificial intelligence COE. So that brings you current to today.

0:04:18
Jim Marous

So it's interesting. As a backgrounder to people that aren't familiar, one of the reasons why Dom has been on the show many times and why we've been friends for, not the only reason we've been friends for years, but has kept us both interested in each other's business is that when people ask me, what are the most innovative finance institutions in the U.S.? I will normally mention Chase, but I usually surprise them by saying, for my bank for the buck, the organization that's doing the best is U.S.

0:04:47

Bank. Most people don't know that because they do it in a rather silent way. It's a Midwestern style, if it were. And the reality is part of that reason is because, as Dom mentioned, how far back that innovation mindset was put in place. And we talk about putting innovation in a culture, but that was really one of your driving forces. Because when you're in the product area, as I understand it, you're kind of innovating, but you're within a nice little compartment.

0:05:14

but the innovation process as the spearhead for the way you're going to manage it really becomes key. So what did you take from your days in the innovation side to the digital side? Did it help? Because that digital progression was a whole lot faster than the innovation progression.

0:05:33
Dominic Venturo

Yeah, I mean, I guess you have to think about this thing in a couple of contexts. And I want to kind of just make it very tangible for the audience. one of the things that you ultimately have to be able to do is look at your delivery model you know financial institutions have legacy systems that a lot of them still do waterfall delivery we've talked about agile and the speed of agile and there's agile decision making there's agile organizations and then there's agile delivery and you have to be able to do all of those so you actually have to infuse that into the organization right so the speed at which make you decisions, the speed at which you then can

0:06:12

do your quarterly planning and your release management means you have to re-architect your software delivery lifecycle. You have to go back farther up the funnel and re-architect your product development lifecycle so that you can continue to do that and operate it at speed. And what we learned in the innovation group was that you also needed to be able to trust the ability to build something, pilot it, test it, and kill it if it doesn't work, which a lot of people have a hard time doing.

0:06:44

But if you think about the investment curve going sort of up and to the right, which is the bigger the project, the longer it takes, the more money you spent, the more money that you now have at risk on that decision. Right. Which is why you see a lot of what I'll call zombie products that are around, which is, you know, we spent a lot of money on it and never really got traction, but we can't kill it because we spent a lot of money on it.

0:07:06

What you want to really be able to do is compartmentalize down to your most lovable product or most valuable, you know, pilot, and be able to bring that to market. You have to redesign the whole system to do that. Like you can't just decide you're going to do that. You have to bring the risk team into the front end of product development. You need to bring the product owners into the front end of product development and the technology and the engineering and the architects, so that now the teams are able to sort of say, oh, I know what you want to do.

0:07:36

Here's how we're going to test it. Here's how we're going to make sure it's compliant. Here's our success criteria, which you've got to set in advance. Otherwise, you'll convince yourself later changing the bar is a good idea and it was good enough. Set your success criteria and then have a go-to-market and scale plan. And to do that across an entire company and an entire portfolio of products means you have to be consistent, you have to have a process, you have to have a machine, and you have to be able to monitor all of that at pretty significant scale for a bank our size.

0:08:12
Jim Marous

So the capsulized summary of what we're going to be talking about today talked about resilience. Now, we're among retail bankers, many of them managing front-facing systems. we're wondering about what's the next innovation that's come through and wondering how are we going to keep up with the pace of change. But when we talk about resilience in banking, it's usually a back office reference. It is usually about how do we keep uptime at a very high level?

0:08:42

How do we make it that if something happens, it unbreaks itself very quickly? I'm not the tech person, so I'm abusing the wrong terminology. But when you think about resilience in banking, it has always traditionally been How do I make sure that I never break the trust with the customer on a fraud, on a risk, on a technology, and in a digital world on an uptime basis? The difference, though, is as we look forward, that ain't enough.

0:09:09

So, Dom, compare what your definition of resilience and U.S. Bank's definition of resilience is and compare it and contrast it to what most institutions still define resilience as.

0:09:22
Dominic Venturo

Yeah, first, I'd like to say I don't use the phrase unbreak things. I use a different one. It's a little more colorful. But, you know, you think about resilience. You really need to think, like I used a terrible example, which is a car that doesn't dent, right? Because things are going to bump into it and the like. And, you know, you have to think about being able to bounce back from whatever that thing was. And sometimes that's a competitive dynamic.

0:09:48

Sometimes it's a market dynamic. and sometimes it's a technical challenge. The underlying table stakes for large financial institutions and small doesn't matter, is that the systems need to be uptime, they need to work, they need to have geographic diversity, they need to have automatic failover, they need to have battery backup, because there's a whole host of things that we can predict can and will go wrong. And so you plan for those. That's the technical side of the house.

0:10:14

I think the other part, though, that you're talking about, and we spent a lot of time around, is like, where is the future going? And what are the expectations going to be within the foreseeable future from our customers around how we deliver products and services and what kinds of things are available to them? And one of the tools we use is within the innovation group to be able to look far out onto the horizon, but also understand the emergence of technology and the landscape that's happening.

0:10:43

And I can't give you future examples, so I'm going to give you some older examples that hopefully will help. A number of years ago, we saw what was happening with information exchange with other parties. So think about FTP transfers or other data exchanges that happen. And we saw in the technology world and in some of the emerging fintech space that folks were moving to really simple and elegant, well-documented APIs, developer portals, and capabilities. And our prediction was that's the way business is going to be done in the future.

0:11:18

And this is years ago. The end result of that is we decided to invest in API development platforms and also the microservices capabilities within our technology architecture that would allow that to happen so that when a payments company wants to plug into us and be able to do payments on their end, but initiate them through the bank, we have an API for that. When they want to be able to validate that an account is valid and has a balance, et cetera, and they're permitted to do so, we have APIs for that.

0:11:52

So it's a good example of, at the time, they were not widely used in banking for connecting to other payments or financial services providers, but we saw that trend in the technology side of the house and in the technology world of products and services and saw that. And there are just a ton of those kinds of examples. The last piece is, remember I talked about the product development lifecycle has to be redesigned and the delivery model does, and all of that is around both agile speed and nimbleness.

0:12:23

If you've reduced everything that you're doing into quarterly sprints, planning cycle, or quarterly planning cycles and capacity, you have the ability to change either within a set of a quarterly planning cycle if it's really urgent, or to be able to get into to the next piece. And the end result of that is, in our example, we can go from this well-defined thing on a whiteboard that we want to do to a version of it that's in production within a quarterly planning cycle, which is pretty impressive.

0:12:53

And we can do multiple releases a quarter within the collection of applications that we have. So that's really resilience to be able to compete. It's resilience to compete and also to adapt. So I'll share one other item is we're constantly monitoring the feedback that we get from customers. And those signals come from call center, chat transcripts. They come from feedback on issues that we get from call centers or problem management and problem resolution. They come from complaints.

0:13:24

But they also come from the CSAT surveys that we do online and the feedback that we get from the customers. And all of that gets digested in near real time and gets fed back to the product organization to say, you know what folks are having a problem with login over and over and again uh this is an example of something that we saw as the advent of people using password managers more often actually caused some problems with the way passwords are entered on banking websites so we had to rethink the way that that's designed or bill pay doesn't work great when you're trying to pay more than five bills at a time and we get that kind of granular feedback

0:14:01

back to the product teams in real time and we can get it into the backlog and get it into production so that we can change it. When we make those changes, we also have built A-B testing capability. So we can have a hypothesis, we can build a change, we can deliver it to a subset of customers and see if it actually performs better before we launch it to the entire organization. That also allows us to be nimble because we might discover and often do that we need to refine it further.

0:14:30

All of that is resiliency. The last thing, sorry, I'm on a bit of a roll, but the last thing that I think is really important is then you have to look at the performance of all of your solutions. And what I mean by performance is how fast is the mobile app load? How fast is the page load? Is there a data element that's causing a problem at that kind of a granular level? because it may be that the API that calls the balance from the rewards card thing, which hops from here to here to here, takes too long, and that then hangs up the whole experience, which creates a bad experience for the customer.

0:15:05

So the level of detail and diagnostics that you need to be able to continuously improve is fairly tremendous. But when you have it, you can go from, oh, I think this is the issue, to a data-driven decision of this is the issue, This is how many times it happens and why it's important.

0:15:22
Jim Marous

Let's go fix it. So this, the foundation of a lot of this is the technology in the back office. We've talked about this. You were doing it when we talked about innovation. The only way you can make innovation work at speed and scale is to have the technology in a digital world that can adjust to that quickly and adjust to something that's completely unforeseen. You know, adjust to a COVID check program that had to be done in four days with the government game to be in a position to do that.

0:15:52

But I think what's interesting is when we're dealing with improvements, product improvements, when we're dealing with innovative new solutions, when the marketplace changes, when you go from a cash rich to a credit poor environment and you all of a sudden say, we need to come up with brand new products that don't exist today. Or let's find a way to let consumers access a line of credit that's smaller than we've ever done, but an instantaneous basis. Those type of things make you more resilient.

0:16:24

I think my best example is, I think we were talking about this once before, that in 2000, I was in Shenzhen, China, and was lucky enough to be able to visit WeBank. and the biggest digital bank in the world, they do most of their customer acquisition is providing financing for mobile phones. Very small loans. But what happened is they found ways to make the entire process of who they should target based on the way they use their phone.

0:16:55

Going further, along your line, they had four parallel cloud platforms that allowed them to test new ideas instantaneously. They innovated on a 14-day cycle, very close to the time period you're looking at, where they were able to get in and get out instantaneously. And it was interesting because their think tank is found by windows. And in that, you have all these empty desks. And I said, where are those empty desks? And they said, that's where the product managers will sit when they identify a problem that may have happened on a call center through another channel.

0:17:27

And they have the power to instantaneously fix it for the masses, which makes you, in the broad sense of resilience, resilient because that allows you to respond very quickly. At the end of the day, the consumer, be it the natural consumer or the small business or corporation, doesn't want you to be waiting for that answer. And you want to be able, as you said, to be able to say, okay, is this something that's going to be a massive change or a minor change?

0:17:55

You know, I think the last time we interviewed you, we talked about the new account opening process. It was relatively new at that process. And you talked about how you went about bringing the right people together. Is the bringing the team together part of that resilience process, not just on a technical

0:18:13
Dominic Venturo

basis, but on a human basis? Yeah, it's a really big part. And it's super important to understand that when, like, I'm talking about digital, which is my organization, but the reality is all of all of what we do and Jim is very kind and gives me credit for it but the reality is all of what we do is a whole organization body of work because you have to have the person that owns the operations in the call center as as part of that you have to have the connectivity to the fraud teams you have to have the connectivity to the risk and compliance teams and to and to be able to bring them in.

0:18:53

And that doesn't mean you have to have 50 people in the room. So you have to have a small group of owners, if you will, for those bodies of work to be able to do it. I think the other part is when I say product, there are the business line product owners. So we call them chief product officers. Then there are the digital product owners, their partners!! On the digital version of the solution for their product, just because we manage the container, how we do that is the collection of those experts.

0:19:23

And we want to get as much good information as we can about what it is that we're trying to accomplish really early. Because once we hand it off to the teams to put into quarterly planning, what we're telling them is, this is your success criteria. This is what we're trying to accomplish. We're not telling them how to design it or how to build it. We're telling them what we're trying to accomplish. So new account opening that Jim referred to, we had a collection of products.

0:19:52

They all had different fields of information that required in order to be able to get it. So credit card was one thing, checking account was another, savings was another. And there was some commonality in those fields of information, but not a lot. But what we were trying to do was build a digital onboarding experience that would allow a customer to be able to become a customer with as little information as possible. what was required, and to be able to get to it.

0:20:18

And the breakthrough that we had, and I had nothing to do with this. This was another senior executive at the time. But the breakthrough that we had with the team as they were struggling with trying to get everybody to align on what that data set would be, he said, okay.

0:20:34
Jim Marous

In a legacy, I mean, we have to remember, we take it for granted, but in a legacy organization, it's always done it a certain way.

0:20:40
Dominic Venturo

And this is five years ago. But the breakthrough was, okay, we can't get to consensus. This is taking too long. Let's take all the fields off the table. So we're going to go from whatever it was, 16 to zero. And then each one that we add has to be mission critical to the objective. And we ended up with just a handful. and that was a breakthrough in thinking, which if you think about taking away all of the constraints and starting over with a fresh sheet of paper, you remove that 20 years of this is the way we've always done it and you say we're going to do it completely different.

0:21:20

Now start with a blank page and come up with the best possible experience that you can and the reality is we came up with a great outcome.

0:21:26
Jim Marous

Well, it's a funny story because I remember when you said it, you added a little thing that you said, yes, we had 16 things. Let's say it was 16 things. And he goes, unfortunately, we realized how much of a legacy bank we were because we got people in the room. They came back and said, we now have 18. You know, because we can't get people together without adding new stipulations. And then you got down to zero and they moved from there.

0:21:50

You included - We're down to two now. Yeah, oh, exactly, exactly.

0:21:54
Dominic Venturo

Two fields of info, we can do a new account. Right. With some help from some technology partners.

0:21:58
Jim Marous

And think about what that means when you're trying to cross out, when you're trying to build relationships in a digital world, as opposed to making people come in and do things the way you'd like them to do, which is in person where I can go through all the steps. But you also, I think, mentioned that that digital accountability process then transcended into the brand, became everybody's modus operandi. So you didn't have a different system for the brand system than you did on the digital mobile way of doing things.

0:22:25
Dominic Venturo

Yeah, I know we have a lot of folks from retail banks that are here and also will listen later. So I want to talk about that for a minute. One of the things that we began doing as part of the digital organization a number of years ago is to build an interface for what we call the banker experience that is basically the same interface that the customer uses. and we used to have a platform for this and an interface for that and a tool for this or that.

0:22:55

And so just to keep it simple, and we started with new account onboarding, but now we're using it in the servicing center and other areas. And so when the banker logs in, because they have different permissions, they can do different things, but it's actually the same experience. Now, what's cool about that from my chair is that that means that I can reuse the code and the engineering and all of the work. And I don't have to now maintain six different systems.

0:23:23

And if I change something that affects this one over here, I don't have to go do all of the dependency reliance on when I deliver, I got to wait for these guys to keep up and the like, because we contain it all in one place. And that's very powerful. So that's a big deal, especially in the retail environment and in the call center environment.

0:23:43
Jim Marous

So, as you mentioned, that was a five-year back. Things have happened so fast. I think you probably still remember what it was like. You'd not worked in a small organization for quite some time, but the reality is the way you did things at U.S. Bank wasn't too unlike what many organizations are doing today in the marketplace. So we have a lot, both on the podcast and live today, that are the $10 billion or smaller organization.

0:24:12

I'm going to take you for a second and place you in one of those organizations, and you can make up where they are in that process. But when we talk about resilience, when we talk about resilience in the way of being prepared for the future to make it where you don't have to backtrack to go forward, or where you can actually be ahead of where the consumer, where the small business, where the government is, what would be the first thing that you'd be looking at to fix to get you in a position to go to the next step?

0:24:42
Dominic Venturo

Well, I mean, the first thing I would have is an organization that is focused on the product development. So I hate to keep it that simple, but the reality is...

0:24:51
Jim Marous

New product development or enhancements on their existing products?

0:24:54
Dominic Venturo

Well, I think... Both. So it depends on what the priority is of the company. Right. And new product development isn't the top... It is an important competitive thing, but a lot of times we're talking about feature improvements, we're talking about experience improvements. And so if you have product owners that think like a product owner of this and understand that they have to build the telemetry, the signals, the information that gives them good insights about what they should change next, that's the next piece, right?

0:25:25

This is one thing to have a product person. Then it's the second thing to say, well, I need data-driven decision-making so that it isn't the most important person in the room deciding what to do next. And sometimes they're very brilliant and they have great ideas, and sometimes the data doesn't bear it out. So you have the ability to make data-driven decisions, which will help you with the business case, the prioritization, the justification. Now, your development or our development doesn't always have to be completely in-house.

0:25:52

And I know that a lot of, especially the smaller banks, rely on either a core processing vendor or a card platform vendor and the like. But the reality is those companies are also innovating and continually bringing new capabilities to market. And one of the challenges that I hear from smaller financial institutions, and we have quite a number of them that are partners of the bank, right? So it's not like we don't get sort of this visibility.

0:26:19

One of the challenges I hear is it's hard to keep up with the changes on our bank side with what the vendors are offering. So they have capabilities. I want to be able to bring them into the bank, but it's difficult to do the change management. It's difficult to do the risk management. It's difficult to do those things. So part of the solve in a product organization is then to say, bring risk, bring compliance, bring technology in and develop a prioritization model that allows you to be able to chip away at those capabilities and be able to bring them to market and then really measure the results of those changes.

0:26:54

Because the more you do that, I'm pretty confident that the results will then create the empowerment that says, let's do more of that. That's a good thing. I saw that. That had good impact on deposits. that had a good impact on account opening, that had a good impact on customer experience. We like that. We want to do more of that. And you'll start to find those areas where you can turn it into more of a rhythm and a process as opposed to this big project, then it's done, then I go get a team and look at the next big project, and that's just a very difficult way to manage it.

0:27:25
Jim Marous

You know, it's interesting because we've had a lot of people that have spoken on the stage from the FormX thing that have talked about things like break it, test and be willing to let go of it, how you communicate with customers. And again, these all kind of roll up to that. Number one, know what your North Star is, and it can be on a project basis. If you don't know what your North Star is, you won't get there.

0:27:47

And I keep on emphasizing it because I think it's something I'm hearing more and more on the podcast. Leadership. It's interesting because the first thing you went to is not what I'm going to fix in the back office. It's a purse I'm going to put in place to make it all happen. And it is a people business. and the communication process. I think what's also interesting, Dom, is that as we look at what's going on in the marketplace today, the good news is we have a lot more partners we can use and they are more willing to play together.

0:28:15

We were talking about it at lunch that I think it was 2019 at this event that we started seeing vendors talking to vendors about how to work with each other, not a competitive basis, but a cooperative basis where if you're going to fix the data, then I may use your data fixes for my solution. I think that's important. When we look at what's in the future, and we'll talk about AI next, but when we look at what's in the future, what are you preparing for from a resilience standpoint?

0:28:47

It may just be, I don't know what I'm preparing for because that happened yet. But what are you trying to make more resilient within U.S. Bank in the context of everything?

0:28:57
Dominic Venturo

Well, I think, you know, I don't know that I would say, I don't know that it's more resilient, but the pace and change in this industry isn't going to get any slower. The external influences we can't control. So part of what we have to do, I mean, I guess if you want to stay sane, part of what you do is don't pay too much attention to the things that you can't control, but prepare for the fact that things will happen that you can't control.

0:29:22

No, and I'll use an example. You know, we saw as an industry a pretty significant change when we had the failure of SVB and the other banks. We had sort of the crisis of deposits, for lack of a better description. And then we saw the environment change pretty rapidly. And some of the other things that were happening at the time, you know, yield curve was changing, interest rate dynamics and the like. But the underlying thing then meant we all had to change.

0:29:50

We had to make it easier to be able to attract deposits. We needed to make it easier to be able to combine up where it made sense products and value propositions in order to make those economics work. And a lot of that had to happen at a very rapid scale. So part of the resiliency is understanding that you're never going to predict that failure and that cascading set of events. If you are, you're in a good place because you're in Vegas and you should go make a whole bunch of money.

0:30:19

But none of us are very good at that. But what we can do is organizationally be prepared. And part of the foundation that we needed to be able to build as a company, which we've been on that journey for the last six or so years, is modernizing the architecture, modernizing the systems where we can, moving to cloud-native applications in the digital space, changing the software development lifecycle, changing the product development lifecycle, and then enabling the organization at enterprise scale to be able to achieve the development.

0:30:55

adapt to, okay, the agenda changed. Now we're going to focus on this, which we do, and deliver. If you look at like our bank smartly checking accounts moved to savings account, then it moved to savings plus a rewards product with the credit card. Part of that was adapting to the market conditions and being able to be, have an attractive collection of products that are able to be delivered. And we delivered some of those in months from the world.

0:31:22

I'm sorry, you've been We didn't bank it long enough. We have to be able to do that. That used to be an annual plan. I know. Not too long ago. It used to be actually 18 months. There we go. Right? Because you do your financial planning, then you do your product planning, then you do your engineering, then it would take 18 months. And by the time you built it, it was too late and you were already behind because the world around you delivered things in months.

0:31:44

So, but we could do that. And we could do it because we changed the technology stack. We changed the environment. We change the delivery model and we change the way the organization thinks about planning and agility.

0:31:59
Jim Marous

So as we look at the future, it is amazing in my mind to think that Genre of AI didn't raise its head until November 2022. And it's not even November of 2025 yet. It's truly overnight. It has gone from, oh, it can answer an interesting question a little bit better than Google, to now it can create visuals, video, dynamics, personalities based on all that. That is something you have to get prepared for without knowing exactly where it will go or where U.S.

0:32:35

Bank may want it to go. How is that changing what you're doing? But more importantly right now, how does AI make an organization of any size more resilient? And I want to take the opposite of that. How does some, in some ways, make it less resilient?

0:32:53
Dominic Venturo

I think I'm going to come, yeah, I'm going to try to do those in order. I mean, so first of all, generative AI is a big deal. I'll grant it that. Part of what, and it's probably obvious to everybody, but part of what makes generative AI a big deal is because, number one, the amount of information that is in the training data that is available for its knowledge base. there were technological advancements that had to happen to enable that breakthrough.

0:33:23

And part of that was enabled by cloud. Part of that was enabled by network infrastructure improvements and the speed at which we can communicate between where we are and where the cloud is. And so that convergence sort of happened, you know, and then the lightning struck. And you saw ChatGPT was born. So that now is an artifact of the future. Yeah. Because it is part of what we will have. But artificial intelligence and banking has actually been part of what we've done for quite a number of years.

0:33:57

You know, advanced machine learning models. Then there was the transformer architecture and Burton the like that came out of Google DeepMind and the like. And there were some really advanced capabilities that came out of that that you don't hear anything about these days because everybody talks about generative AI. But those were really powerful engines. They allowed us to do things like advanced image analytics and check processing and fraud. They allowed us to do things like network detection, not the Internet, but networks of actors in things like fraud prevention, crime management, financial crimes, human trafficking and the like.

0:34:35

And these sound like not very sexy things, but there's a lot of money in the banking system that gets lost through fraud, crime and the like. And so there's been a lot of really, really important work that has gone on there that doesn't get tons of publicity. And that was sort of AI. Generative AI comes along, and I talked about a couple of things that made it a game changer, the last of which is the natural way that we can interact with it.

0:35:00

You no longer have to be a data scientist and a machine learning expert and a this or a that. You can actually just interact with one of these tools, and you can ask it questions, and you can get answers. Now, they may not be right. That's a whole other topic. But importantly, those found what we call foundational models are pretty easy to train. So let me explain. You start with an open source, a large language model, and then you train it in your environment on a knowledge base, a set of information.

0:35:33

Guess what banks are really good at? Banks and credit unions. Documentation. We have policies. We have documents. We have knowledge bases. We have tons and tons of rules. All of those rules are amazing tools to train a generative AI engine. So we take this thing that is general knowledge and then we give it very specific training and then we tell it because you have to. You're only allowed to work within the rules we gave you. So you can use the other knowledge to communicate like a human communicates, but we want you to stick within the answers of those that we have trained you on.

0:36:12

So you're taking general, making it specific, and then you can create those and start to create those for very specific use cases. General banking. Call center for customer service for support to be able to get to the right answer more quickly, not have to read through the policy and the like, just give me the answer and allow me to answer the customer's question. Fraud, fraud analytics and detection and the like, and the experts that do that to pre-prepare sort of case management and other sorts of activity.

0:36:41

There are on and on and on kinds of applications. but banks probably aren't going to build a large language model because that takes an enormous amount of money and compute and power and the like. And there's not really a business case to do it or a need, but being able to leverage those capabilities and then build agents or agentic solutions that allow us to deliver against that will be, I believe part of the, part of the future.

0:37:04

I'm missing the ultimate personalization. And yes. So within, Within the ability of this dream of one-to-one personalization, which has always been very complicated to do, a lot of the reason that that has been very difficult to do is because the data is always dated. The data are always dated by definition because it's last month's transactions or it's whatever. When you have these models running at machine speed and you can actually do real-time detection of changes in behavior, then you can provide a useful alert.

0:37:37

You can provide an insight. You can alert the fraud team. There's a whole host of things that you can do. The very last thing that I want to say on this is that generative AI is really, really good at is taking unstructured data. So just imagine, so unstructured data, if you're not familiar, is just not a database. So financial statements, tax returns, people put them in different forms. Other information customers might give us an offer letter for a piece of real estate.

0:38:07

another good example, to take that unstructured data, to understand the intent of the data, what is this document and what's it for, and then to be able to accurately extract that data and then put it in a system for processing. So if you can do those things and you chunk up bodies of work that you have within your institution, you've just created tremendous operational efficiency. Because I don't have to do swivel chair, I don't have to do key entry, I don't have to do anything, All I have to do is review it and make sure it's accurate and then post it.

0:38:39
Jim Marous

And generally, you're doing things that the consumer or small business or corporation doesn't do a really good job at, but we can actually, because of your scale, computerization, cloud, everything else, you can actually do that on behalf of the customer. That's exactly right.

0:38:53
Dominic Venturo

And it's, you know, like some of the biggest opportunities in banking, in my view, are not very sexy. but because they happen and thousands of people do them and it's lots and lots of work to be able to do it and it's not what i would call higher order human processing right um and so when you free that time up you then allow them to to actually work on things that are challenging and are engaging and value adding whether that's while i'm talking to the customer about their needs and goals instead of looking up a policy or an answer to a question or whether it's you know I'm going to go spend time more accurately working on this thing or

0:39:32

that thing, building a strategy, et cetera, because I don't have to do the other work.

0:39:36
Jim Marous

So finally, I had two different ways I wanted to go. One was what excites you about the future. But the one I really want to ask is, you're at, I think, number five as far as size of assets. But there's a big difference between number one and number five. There's even a bigger difference between number five and number 3 ,740. Part of resilience is how do I make it so my organization is always going to be able to compete for the consumer, for the customer in a really aggressive way without being aggressive.

0:40:08

When you look at that resilience in that way, what is U.S. Bank doing to differentiate itself and make it more resilient in the broad sense of the term?

0:40:17
Dominic Venturo

Yeah, I mean, I think that for so you heard a lot of the things that we've been doing in a number of spaces, but let me try to bring it together. We've been on a mission. We've been on a mission for a number of years to be able to digitally enable just about anything that a customer wants to do with us. and this is going to sound like a small thing, but the reason it's a big thing is because part of our delivery model with the customer is to be able to give consultative advice, to be able to give personalized service, to be able to give that human touch.

0:40:50

And that's part of our sort of mission, right? Which is we put people first and we're, you know, we're really trying to power the potential humans. But in order to do that, you have to get a lot of the busy work out of the way and you have to allow a customer to just get stuff done that they can either on their own or with customers. We do co-browse and we don't force people into a channel.

0:41:10

But the whole reason that we're on that journey is we then free up some of that time. And that allows us to then spend time on the value add and the purpose. Now, every bank is going to have a different lens on what they think their purpose is or what they think the value contribution is that they do. So the important thing is to say, find the things that distract you from your purpose and get rid of them.

0:41:33

And I don't mean don't do them because it might be like risk management. So it's pretty important, but find those things that are not allowing to do the thing that you think does differentiate from you. And if you can automate them, if you can simplify them, if you can do that.

0:41:47
Jim Marous

Find a partner that can do them.

0:41:48
Dominic Venturo

This is like the account opening, take away all the fields and only put back the ones that matter. So then you can focus on the things that matter that differentiate you from the competition and allow you to exceed in the area that you want to.

0:42:01
Jim Marous

Dom, it is always a pleasure to meet with you. I always learn a lot. Always get a sense for where banking can be. I would suggest the audience, the people who are watching the podcast, continue to investigate. You have ways now with ChatGPT to say, what is U.S. Bank doing in the resilience field? Or how are they addressing the X, Y, or Z issue that you may be addressing all the time? because they're a good model to follow.

0:42:29

They're not a big bank in the judicial big bank way. They're a Midwestern organization that's grown over time, but it's grown because of the innovation, the product development, the looking out for the people, not just the consumers. We didn't talk much about it, but the internal people as well. The culture is something unique from an innovation standpoint. But I think the most important takeaway is I hope that everybody realizes that the definition of resilience is the founding component that right now we need to work towards as an industry because of the fact that the world's changing so fast, because we don't know.

0:43:05

We just have to look at the last couple of weeks to realize the whiplash that goes on, and you don't know what's going to come up next. And that's not a political statement. That's the world today. And because we're in a global environment, we may not have control over that going forward. So how do we put ourself in a place that we can respond to things we don't expect? Dom, thank you so much for being with me again today.

0:43:29

I hope the audience appreciates it.

0:43:31
Dominic Venturo

Thank you. Great to see you, Jim. Thanks for the time. Thanks, everybody. Have a great rest of the conference.