Video Transcript

You bring up some good points around being able to interact with the business. So, you've got this capability over here in IT, the tools that allow you to look into the future, so to speak, and be able to identify where problems are occurring and really translate that to business language, if you will. And I think that's really key for businesses to bridge the gap between IT and the business side of the house. Do you have anything else you want to share there in terms of how you've been able to interact with IT and the business side of the house?

You stole my line: "bridge the gap." Bridge the gap is actually my motto in the company. We look to bridge the gap. If you look at it, I call it three different circles. The first circle is really technology, where we all sit, the majority of us sit in my company, like on my team. Then you have the middle area, which is that app dev, some of the business liaison. And then on the right side, which is the true business area. So you have the three circles, so to say, and the interactions and where they intersect with each other.

So we do a pretty good job of circle one talking to circle two. Circle one talking to circle three generally never happens. People put up their hands, they're afraid of talking to the business, and that's where we actually show the benefit to the business. I meet with business users all the time, and they come to us now to help them with a solution. They don't understand the technology side of it. They just need to know that "I need my processes done sooner, that I need my reports done earlier."

One of the big issues we had a couple years ago, especially in the COVID era, with liquidity and risk in the market, us being able to say we have to open the doors to start the bank up in the morning. We were delayed hours at times with our liquidity reporting. That's a true business area where they're reporting right to our Treasury Department, reporting right to the Federal Reserve saying, "Hey, we can start our day. We're liquid." The problem was we were running four to six hours late every day on these reports due to upstreams.

And so looking at, like I said, the integration with these tools, with the workload automation, with the AI, with some of this incident reduction stuff that we have in place, we're able to bridge that gap. And basically, a user coming to us, an end-user business user saying, "Hey, you got to give me my reports by 12 o'clock, otherwise the bank can't open its doors." And so looking at this, we were able to reduce it by almost four hours, which was significant.

We had a great partnership with the Broadcom team. We built solutions in the cloud, which were never there before. A lot of AWS type work with the S3 file watches and file box. We co-partnered with the Broadcom organization there, and we built this functionality in the cloud, on-premise. It was a hybrid solution, and that was a true business impact, start of day, that we were able to solve.

So that's one area. And then again, we meet with the business on a monthly basis: transaction banking, core bank, corporate banking, depending on the lines of business. And what we do is we share with them what we're doing, what we have from a technology perspective, and we ask them, "What do you need?" So us helping the people in that middle bucket, if we can make problems go away from incidents, the app dev guys aren't having to work as much to fix the incidents. We're identifying where we have challenges within like a workload automation process. We run this incident reduction program. We identify them. We run it quarterly. We fix the problems, and then that gives them the ability to work even closer with the business to give them what they need on the business side to roll out more applications and do things on their side. So, us helping the middle really helps the end user.
.
.


abstract ai

 

Note: This transcript was generated with the assistance of an artificial intelligence language model. While we strive for accuracy and quality, please note that the transcription may not be entirely error-free. We recommend independently verifying the content and consulting with a product expert for specific advice or information. We do not assume any responsibility or liability for the use or interpretation of this content.