The real ROI of digital transformation: why most financial institutions are measuring the wrong things

I’ve been in hundreds of technology evaluation and implementation conversations, sitting on all sides of the table, as a banker making buying decisions, as a consultant helping institutions identify, quantify and ultimately extract value from the technology solutions they have already purchased, and of course as the software / technology provider. That unique perspective has provided me with a front-row seat to a pattern that keeps repeating itself across the industry.

Financial institutions spend enormous amounts of capital on technology and digital transformation. Core system maintenance, upgrade, or replacements, digital banking platforms, CRM systems, data and analytics tools, and loan management software. Technology budgets represent a significant and increasing portion of an organization's operating budget with no signs of it slowing down. But when we ask the question, "Did we actually get the digital transformation ROI we expected?" The honest answer, more often than not, is; we're not sure.

Key takeaways

Most digital transformation ROI shortfalls in banking come from process, adoption, and measurement gaps, not the technology itself. Institutions that close the gap treat tech purchases as business transformation programs, not software installs. That means clear outcome ownership, a defined measurement cadence, and process redesign built in from day one.

Why ROI projections fall short

The numbers are staggering. McKinsey research found that 70% of digital transformations in banking exceed their original budgets and 7% end up costing more than double the initial projection. Only 30% of banks report successfully implementing their digital strategy and meeting the original, stated objectives.

In my former life, I led a team of dynamic, innovative (reformed) bankers working with hundreds of banks, credit unions and fintechs. Our job was to help them get measurable value from the technology investment they made in our company. What I found consistently, was the gap between projected and realized ROI almost never came from software. It came from four recurring strategic and execution failures.

Processes didn’t change. New technology went live and everyone adapted their new tool to match their old processes or workflows. When you don’t redesign direct and downstream processes around the new capabilities, you’re simply paying for a more expensive version of what you had before, often with much less efficiency.

Nobody owned the adoption. Software gets implemented; required behavior change gets ignored. The go-live celebration is the beginning, not the end. The institutions that realized the most value from any tech investment had someone - a real person with accountability - responsible for driving and measuring adoption and utilization, typically by customers and employees.

Success was defined as go-live. Most institutions track implementation timelines and budgets obsessively which is important and necessary, but it is just the first phase of achieving the promised value of the technology investment. Many abandon the disciplined measurement once the system is live. Research consistently shows that early stakeholder engagement and sustained change management remains the most underfunded and overlooked part of a transformation strategy.

Features were delivered; outcomes were assumed. Contracts in our industry are almost universally written around feature delivery. The vendor commits to giving you the capability; your organization assumes capability will translate to value. Oftentimes, the new technology or system is handed over to the operational leader / team ultimately responsible for achieving the promised ROI, without the clarity and resources necessary to accomplish the objectives.

Institutions need a clear strategy, a willingness to evaluate operational processes, and an execution plan that reaches across the impacted areas of the organization, the technology will almost always fail to achieve the objectives by itself.

This is where the solution provider has some responsibility. They frequently overestimate a financial institution's ability to achieve measurable value. The provider sees their responsibility ending with implementation and that their now live client will change the world with their new found capabilities. The very simple, but profound oversight is this; if the technology is compelling enough for a financial institution to purchase, then it is providing a capability they have never been able to do (or do as well) before. Recognizing this is a new Assuming that to be the case, why would we assume the same institution has ever developed a STRATEGY to maximize this new capability, or OPERATIONALIZED this new capability?

The reason why this should matter to the solution provider is the strategic and operational execution gaps are now framed as technology deficiencies. Which most frequently manifests at contract renewal. What should be a deepening of relationships and a strategic expansion conversation, quickly becomes a retention drill with concessions being made by the provider.

A better framework

The institutions I've seen get this right operate with a different mental model from the start. They treat technology purchases not as software installs, but as business transformation programs. Before the ink is dry on any significant tech investment, they've answered these questions:

• What specific business outcomes are we trying to move?
• Who in our organization owns the behavior change required to realize those outcomes?
• How are we measuring success at 6, 12, 18, and 24 months?
• What process redesign work needs to happen alongside the implementation?
• How is my solution provider supporting me as a strategic partner, not simply a vendor?

You can't buy a $2M platform and allocate $50K for change management. The ratio doesn't work.

The lending-specific problem

In lending, this challenge is compounded by a few industry-specific dynamics. Lending operations tend to be deeply process-dependent, decades of workflow have calcified around legacy systems. When a new loan management platform or origination system goes in, the natural tendency is to configure it to replicate existing workflows rather than rethink them.

The result: you've paid for a modern, capable system and you're using it to do exactly what your old system did. McKinsey's research on large-scale IT implementations found that 56% of projects deliver fewer features than originally planned, and the average cost overrun is 45%. The root cause is almost never technical — it's cultural and organizational.

What good looks like

The institutions that consistently realize tech ROI share a few traits:

• They have executive sponsorship that doesn't evaporate after the contract signing.
• They build dedicated internal implementation teams.
• They create feedback loops — regular business reviews, utilization metrics, outcome tracking — that keep the investment accountable past go-live.
• They actively engage their solution provider as the conduit into the broader industry trends and best practices
• Most importantly, they're honest about what they're actually buying.

They're not buying software. They're buying the capability to change how they operate. The software is just the enabler. If the organization isn't ready to change, no tool will force it.

The lenders that will win the next 12-24 months won't simply be the ones with the best technology. They'll be the ones who leverage their technology investments into operational reality. That's a leadership opportunity and it starts long before the contract gets signed.