Modern banking IT landscapes are complex beasts—an evolving mix of legacy mainframes, cloud services, SaaS vendors, regulatory systems, and sprawling on-prem infrastructure. As financial institutions chase digital transformation, what often gets left behind is a coherent strategy for technology governance.
Frameworks like FinOps, DevOps, SRE, ITSM, ITAM, SAM, TBM, TOGAF, and ITIL exist to manage this sprawl. Some are tactical—focused on uptime, cost, and compliance. Others are strategic—driving innovation, agility, and business value. But in banking, these frameworks often evolve in silos: IT builds one, Ops adopts another, Risk brings in a third. The result? Disconnected priorities, duplicated data, and missed opportunities.
Take a Tier 1 bank managing thousands of internal apps. Legacy COBOL systems run alongside microservices on AWS. Teams in different regions adopt their own tools to track usage and costs. One team runs ITIL, another builds SRE practices. Meanwhile, compliance demands constant reporting.
This fragmentation causes pain:
Tactical Governance:
A large bank uses ITSM (ServiceNow) to streamline incident response times. It hits its SLA targets and reduces outages. Good win—but it doesn’t ask why these outages happen or how infrastructure decisions tie to business outcomes.
Strategic Governance:
Contrast this with ING Group’s approach to DevOps and architecture. ING empowered “BusDevOps” squads—combining business, development, and operations in cross-functional teams. Architecture is guided by business value, not just compliance. Trade-offs are made deliberately, aligning technical debt with strategic flexibility. This is closer to a strategic governance model, with architecture acting as the connecting tissue.
Centralized governance sounds ideal—until regional regulatory teams block global rollouts. On the other hand, letting each country or product team run its own tooling creates silos. The most successful banks adopt a federated model:
Banks need strong architectural leadership—not just governance councils. Architecture must drive decision-making through principles like Werner Vogels’ Frugal Architect:
This approach could mean rejecting a “cool” new analytics platform if it doesn’t materially impact customer value or increase operational efficiency. For example, a regional bank in the U.S. saved millions by rationalizing duplicative risk platforms under architectural guidance rather than compliance mandates.
📈 Banking Technology Stack Insights – McKinsey & BCG Industry Reports
👉 https://www.mckinsey.com/industries/financial-services
👉 https://www.bcg.com/industries/financial-institutions
🧠 Frugal Architect by Werner Vogels
👉 https://www.allthingsdistributed.com/
📊 Apptio TBM Resources
👉 https://www.apptio.com/blog/
☁️ Cloud FinOps Framework
👉 https://www.finops.org/framework/
📘 The Phoenix Project – A Novel About IT, DevOps, and Helping Your Business Win
👉 https://itrevolution.com/product/the-phoenix-project/
🏛️ TOGAF and Financial Services – Open Group Whitepapers
👉 https://pubs.opengroup.org/architecture/togaf-standard
🔍 SRE at Scale in Finance – Talks & Slides from Google SREcon
👉 https://srecon.usenix.org/
(look for Goldman Sachs, Capital One, and Citi SRE presentations)
There’s no off-the-shelf solution to governance in banking IT. But success doesn’t come from piling on more tools or tightening central control. It comes from orchestrating the frameworks you already have, investing in architectural leadership, and aligning everything to real business value.
It’s not easy—but it’s necessary. And those who get it right will be the ones who innovate faster, manage risk better, and create lasting competitive advantage.