You Can’t Buy Your Way Into the Future

Every year, banks spend billions of dollars on technology. New core systems. AI-powered underwriting platforms. Digital account opening tools. Workflow automation that promises to shave hours off back-office processes. And every year, a meaningful share of those investments quietly underperforms — not because the software was wrong, but because the organization was not ready for it.

The uncomfortable truth is that most technology failures in banking are not technology failures at all. They are change management failures. The software worked exactly as designed. The organization just never fully committed to using it.

The Shelfware Problem Is Still Very Real

Ask any seasoned bank technology executive about their organization’s software graveyard and you will get a knowing look. A loan origination system that never reached full deployment. A CRM that branch staff never stopped working around. A data analytics platform that IT maintains but business lines rarely open. These tools did not fail at the vendor demo. They failed at the organizational level, where actual adoption lives.

Research consistently shows that employee resistance and poor change management — not technical defects — are the leading causes of digital transformation failures. Some estimates put the failure rate of large-scale technology initiatives above 70 percent. In banking, where operational culture tends to be conservative and process-driven by necessity, the odds are arguably steeper.

The pattern is familiar. Leadership approves a significant technology investment. A project team spends months on configuration and integration. Training gets compressed into a few sessions in the weeks before go-live. The system launches. Adoption is uneven. Workarounds multiply. Within two years, the organization is evaluating replacement options.

Why Banks Keep Repeating the Same Mistake

Part of the answer is that buying technology is far more visible than managing change. A new platform shows up on the board deck. A ribbon gets cut, metaphorically. There is a launch announcement and a vendor press release. Culture change has none of that drama. It is slow, iterative, and resistant to milestones. It requires managers to shift their behavior, frontline staff to unlearn entrenched habits, and leadership to maintain pressure over months rather than weeks.

There is also a tendency in banking to treat technology as a substitute for the harder organizational work, rather than a complement to it. A bank struggling with inconsistent credit decisioning buys an AI model. A bank with siloed customer data buys a data warehouse. A bank with inefficient loan processing buys automation software. These are reasonable investments — but none of them solve the underlying problem if the people operating them do not trust the output, understand the workflow, or feel accountable for the outcomes.

Technology can surface better information. It cannot make people act on it.

What Actually Drives Adoption

Banks that consistently get strong returns from technology investments share a few common practices. None of them are particularly glamorous.

First, they treat the people side of the project as equally important as the technical side — with dedicated resources and accountability. This means assigning a change management lead who is not also responsible for implementation timelines, investing in communication that starts before go-live and continues well after, and building adoption metrics into the project scorecard from day one. Measuring licenses and logins is a start. Measuring whether behavior actually changed is the point.

Second, they engage the skeptics early. Every organization has them — the branch manager who has seen four systems come and go, the underwriter who knows three reasons why the new platform will create more work, not less. These voices are easy to dismiss as resistance. They are more accurately described as institutional memory. Bringing them into the process early, and taking their concerns seriously, tends to surface real implementation risks and build the credibility that makes broader adoption possible.

Third, they align incentives. If the new CRM adds five minutes to every customer interaction and performance evaluations still measure call volume, adoption will lag. If the new underwriting model requires a process change that makes one business line look slower on paper, that line will find ways around it. Sustainable adoption requires that the people being asked to change have a reason to change — and that the metrics they are measured by reflect the new reality.

Fourth, they invest in middle management. Research on organizational change is consistent on this point: frontline adoption rises and falls with direct managers. A senior leader can champion a platform at an all-hands meeting. A frontline employee’s day-to-day behavior is shaped by their immediate supervisor. If middle managers are not genuinely bought in — not just compliant — the transformation stalls at the branch or department level, even when executive sponsorship is strong.

Raising the Standard for What Success Looks Like

Banks have gotten sophisticated about vendor evaluation. They scrutinize integration capabilities, security protocols, and total cost of ownership. Fewer apply that same rigor to their own organizational readiness before they sign a contract.

A useful forcing function is to define adoption success before the project starts. Not feature delivery or go-live date — actual usage. What percentage of eligible staff will use the system as the primary workflow within 90 days? Within a year? What process outcomes should improve, and by how much? These targets create accountability that extends beyond the implementation team and keep the focus where it belongs: on whether the organization actually changed.

The technology industry has spent two decades making software easier to deploy. Implementations that once took 18 months now take six. Cloud migrations that required entire IT departments now happen in weeks. The technical barriers to getting a system running are lower than they have ever been.

The human barriers have not moved as much. And that is where the work is.

Banks that learn to match their technical ambition with genuine investment in culture and change management will not just get more out of each technology dollar. They will build an organizational capability that compounds over time — the ability to actually absorb change, rather than just purchase it.

Recent Articles

• 
  Team Spotlight: Michelle DeGray
  Michelle describes herself as efficient, thorough, and considerate, and those who work with her would say she lives up to every word. She is known for being conscientious in everything she does, from building a detailed project plan […]
• 
  You Can’t Buy Your Way Into the Future
  Why Change Management Is the Real Work of Banking Technology
  
  
  Every year, banks spend billions of dollars on technology. New core systems. AI-powered underwriting platforms. Digital account opening tools. Workflow automation that promises to shave hours off back-office processes. And every year, a meaningful share of those investments quietly underperforms — not because the software was wrong, but because the organization was not ready for it.
  
• 
  BankNews: De novo applications are on the rise but face many headwinds
  In the past 25 years, the number of community banks has decreased by half to right around 4,000 institutions. Part of the reason for the decline is the dramatic fall in the number of new banks starting up, particularly since the financial crash of 2008. As the community banking model continues to feel the stress of the contemporary landscape, and many seek efficiency through mergers in order to survive, where and how can a de novo effort succeed or fail?