I've spent my career inside banks — running them, fixing them, and building them. And if there's one thing I've learned, it's this: transformation programs fail far more often than they succeed.

Not because the technology isn't good enough. Not because the people aren't smart enough. They fail because the approach is wrong. Banks treat transformation as a series of disconnected projects — a core system upgrade here, a process redesign there, a cost-cutting initiative somewhere else — and wonder why nothing fundamental changes.

Real transformation is different. It requires four things to move together: people, process, technology, and finance. Miss one, and the whole thing eventually stalls.

That's not a theory. It's what I've seen play out over and over.

How I think about transformation at banks

A simpler transformation framework that works

There are various transformation frameworks developed by top management consulting firms. All are great! But the one I find most useful in practice is from Deloitte. It recognizes that transformation isn't a single project. It's a structured process that moves an institution from its current state to a different operating model.

The methodology follows a clear sequence: understanding where you are, defining where you need to be, and executing a roadmap to get there.

In banking, that discipline matters. Banks are complex organizations with deeply interconnected systems, processes, and balance sheets. Without structure, transformation efforts become fragmented before they even start.

Understanding where you are

You can't fix what you don't understand.

So the first thing I do is get under the hood. Not just look at the org chart, but actually understand the technology architecture, the core systems, the operational workflows, the financial performance, and the governance structure. How do decisions get made? Where do things break down? What's actually causing the friction?

Most banks have accumulated layers of complexity over decades. Systems were bolted on to solve specific problems. Processes evolved to meet regulatory requirements. Teams built workarounds to compensate for platform limitations. Over time, it becomes hard to tell what's intentional and what's just accumulated.

A good diagnostic cuts through that. It identifies the real bottlenecks — whether they're in the technology stack, the workflows, the organizational structure, or the financial model.

Skip this step, and you'll end up solving the wrong problems.

Defining the Target Operating Model

Once you know where you are, the next question is where you need to be.

That's the Target Operating Model — the TOM, in consultant-speak. But I don't treat it as a theoretical exercise. It's a set of concrete answers:

  • How should this bank actually operate in three years?

  • What technology architecture will support it?

  • How will work flow through the organization?

  • Who makes which decisions?

  • How do we measure success?

The Target Operating Model brings together people, process, technology, and finance and aligns them around a clear direction. If you can't answer those questions clearly, you're not ready to move.

Building the transformation roadmap

With the current state understood and the future state defined, the next step is figuring out how to get from one to the other.

Large banking transformations are never single initiatives. They're portfolios of work: core system upgrades, process redesign, digital channel development, data platform modernization, operating model changes. All happening in parallel.

The challenge is sequencing. Some technology upgrades have to happen before process changes can be implemented. Organizational changes may need to precede system migrations. Financial constraints shape the pace of investment.

A good roadmap breaks the transformation into manageable phases while keeping the long-term architecture in view. It prioritizes what matters most and sequences everything else around it.

Program execution and governance

Roadmaps are easy. Execution is where programs die.

The difference between transformation that works and transformation that stalls is governance. Who makes decisions? How fast? With what information? Who's accountable when things go off track?

Deloitte's approach emphasizes strong governance structures — transformation offices, program management frameworks, executive steering committees. That sounds bureaucratic, but in practice it's essential. Large programs lose momentum fast without clear decision rights and regular performance monitoring.

In my experience, transformation is less about perfect planning and more about disciplined execution over time. You need a structure that catches problems before they become crises and keeps momentum when things get messy.

Without that, even the best plan falls apart.

Continuous evolution

Finally, transformation should never be viewed as a one-time project.

The banking industry doesn't stand still. New regulations emerge. Technology evolves. Competitors get faster. Customer expectations shift. Institutions that treat transformation as a finite initiative find themselves back where they started five years later.

The real goal is to build an organization that can adapt continuously — that has the internal capability to modernize, innovate, and evolve on an ongoing basis.

That's the difference between a bank that transforms once and a bank that stays relevant.

Why most transformations fail

If I had to boil it down to one thing, it's this: most transformations fail because banks treat people, process, technology, and finance as separate workstreams.

Technology teams go off and build platforms that don't align with how the business actually operates. Process redesigns are done in isolation from system constraints. Finance applies discipline too late, after investments have already spiraled. And people — the teams actually doing the work — are brought in at the end, asked to implement changes they had no part in designing.

Sustainable transformation only happens when these four elements move together. Technology defines what the bank is capable of doing. Processes determine how work flows through the organization. Finance enforces discipline around performance and investment. And people determine whether change actually happens.

Leave any one out, and transformation doesn't last.

Final thoughts

I've sat through enough steering committee meetings to know that transformation is often portrayed as a technology challenge. It's not. It's an institutional challenge, one that sits at the intersection of people, process, technology, and finance.

When those four are aligned, banks can modernize their operations, deliver better customer experiences, and build institutions that remain competitive for decades.

When they're not, even the most ambitious programs stall.

The framework matters. But execution matters more.