I used the term myself for years. "Digital transformation." It sounded serious. Strategic. Like something important was happening.

Then I sat through enough steering committee meetings to realize the term had become meaningless.

Every bank was doing "digital transformation." Some were replacing core systems. Some were building mobile apps. Some were automating manual processes. Some were just updating their websites and calling it a day. All of it got called the same thing.

The problem isn't the term. The problem is what it obscures.

Why I stopped believing in "Digital Transformation"

Digital transformation became a label for spending money

If you were investing in technology, you were transforming. Never mind whether the technology actually changed how the bank operated. Never mind whether customers noticed any difference. Never mind whether costs went down or efficiency went up. The spending itself became the proof of progress.

I've seen banks pour eight figures into digital channels while keeping the same broken back-office processes. Customers could open accounts on their phones in five minutes — and then wait three days for someone to manually verify their documents. That's not transformation. That's a nicer front door to the same old house.

I've seen banks launch award-winning mobile apps while their call centers remained understaffed and their branch networks continued to bleed customers. The app got the press release. The operational problems got ignored.

Real transformation is invisible to customers

The things that actually change a bank — core modernization, operating model redesign, financial discipline — don't make for good press releases. Customers don't see them. Analysts don't ask about them. But they're what determines whether a bank can compete five years from now.

Digital transformation, as commonly understood, became about the visible layer. The app. The website. The chatbot. All important. All insufficient on their own.

I've watched banks invest heavily in visible digital capabilities while their underlying architecture grew more fragile. New channels layered on top of old systems. Customer-facing innovation masking back-office decay. Eventually, the weight of the legacy becomes unsustainable, and the whole thing starts to crack.

The metrics problem

Banks measure what's easy to measure. App downloads. Active users. Digital adoption rates. All of these can go up while the bank's fundamental competitiveness goes down.

I started asking different questions. What's our cost-to-income ratio trend over five years? How many systems support customer onboarding? How long does it take to launch a new product? Where are our biggest operational risks?

Those questions tell me whether real change is happening. The answers are rarely exciting. They're rarely in the annual report. But they're what matters.

What I look for instead

These days, when someone tells me they're doing digital transformation, I ask them to define it. Most can't get past the marketing language.

The ones who can — the ones who talk about architecture simplification, operating model redesign, financial discipline, and governance — are usually the ones actually getting somewhere. They understand that transformation isn't about the visible layer. It's about the foundation.

I've learned to look for banks that are willing to invest in things no one sees. The data migration project that enables real analytics. The core modernization that enables faster product development. The operating model changes that reduce decision friction. The financial discipline that ensures investments actually pay off.

Those banks rarely call what they're doing "digital transformation." They just call it fixing the business. And that's exactly what it is.