Change-the-Bank vs Run-the-Bank
Change-the-Bank vs Run-the-Bank is the framing — originally from banking IT planning but now used across enterprises — that splits technology spend into two buckets: Run-the-Bank (RTB) keeps existing systems operating (infrastructure, support, maintenance, license renewal, security patching), and Change-the-Bank (CTB) builds new capability (new products, modernization, transformation, automation). The strategic question every CIO and CFO faces: what should the RTB:CTB ratio be? Industry averages sit around 70:30 (70% RTB, 30% CTB). Best-in-class digital firms operate at 50:50 or even 40:60. The ratio determines whether the company is investing in the future or just keeping the lights on.
The Trap
The trap is treating RTB:CTB as a fixed ratio to defend in budget season rather than an outcome of architecture and operating model decisions. CFOs lock in 'CTB = 30% of IT budget' as a target, then engineering teams game the categorization (call maintenance 'modernization' to hit the target). The real issue: RTB spend is structurally driven by tech debt, vendor lock-in, manual ops, and architectural complexity. You can't budget your way to 50:50 — you have to architecturally simplify your way there. The other trap: optimizing CTB ratio while letting overall IT spend grow uncontrolled. A 50:50 split on a $200M budget that should be $120M is worse than 70:30 on a $120M budget.
What to Do
Manage RTB:CTB through architectural levers, not budget edicts: (1) Measure actual ratio honestly — categorize every line item, audit periodically. (2) Identify the top RTB cost drivers (legacy infrastructure, manual ops, license sprawl, integration tax). (3) For each driver, build a multi-year reduction plan — modernization, automation, consolidation. (4) Reinvest RTB savings into CTB rather than cutting overall spend (shifts the ratio without budget shock). (5) Tie CTB investments to specific business outcomes — when CTB has named sponsors and quantified benefits, the case for shifting the ratio survives CFO scrutiny. Goal: durable RTB:CTB shift driven by structural change, not categorization games.
Formula
In Practice
BCG and McKinsey both publish that top-quartile financial services firms operate at ~50:50 RTB:CTB while industry average is ~70:30. JPMorgan Chase has explicitly worked to shift its ratio toward more CTB through cloud migration, mainframe modernization, and platform investments — CEO Jamie Dimon's annual letters reference reinvesting operational savings into product innovation as a deliberate strategy. Goldman Sachs publicly stated a goal of moving from 80:20 to 60:40 RTB:CTB through engineering platform investment and cloud migration — explicitly framing the ratio as a strategic metric, not just a budget category.
Pro Tips
- 01
Audit RTB:CTB categorization once a year with finance and engineering together. Without joint review, every team self-categorizes generously toward CTB. The honest baseline is usually 5-15 points more RTB than the reported number.
- 02
RTB savings from automation and modernization should be 'reinvested' into CTB, not returned to the CFO. Without this commitment, the operating model never changes — savings just shrink the budget. The board-level commitment to reinvest is more important than the savings number.
- 03
Tech debt is the single biggest hidden driver of RTB. Every year you don't pay down debt, RTB grows because more workarounds and manual interventions accumulate. CTB investment in debt reduction has a higher long-term ratio impact than CTB investment in new features.
Myth vs Reality
Myth
“Industry average 70:30 is a healthy benchmark”
Reality
Industry average represents companies that have stopped investing in their future. Top-quartile competitors operate at 50:50 or better and are using the CTB capacity to outpace average competitors. Aspiring to industry average is aspiring to be left behind.
Myth
“Cutting RTB always helps the ratio”
Reality
Cutting RTB by deferring maintenance or skipping security patches creates technical debt that grows future RTB. Sustainable RTB reduction requires structural change — modernization, automation, consolidation. Cutting without structural change just delays the cost.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
Your IT organization spends $80M/year — $60M RTB, $20M CTB (75:25). The CFO mandates CTB to grow to 40% of total budget without overall spend increase. What's the right approach?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
RTB:CTB Spend Ratio (Financial Services)
Banking, insurance, asset management — where the framing originated and is most establishedDigital Native / Top Decile
40:60 to 50:50
Top Quartile
55:45 to 60:40
Industry Average
65:35 to 75:25
Lagging
75:25 to 85:15
Stuck in Maintenance
> 85:15
Source: BCG IT Benchmarking 2024 / McKinsey Tech Spend Diagnostics
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
JPMorgan Chase
2018-2024
JPMorgan Chase publicly committed to shifting its IT spend mix toward more CTB through a multi-year program of cloud migration, mainframe modernization, and engineering platform investment. CEO Jamie Dimon's annual letters explicitly framed the strategy: take the operational savings from modernization and reinvest them in product innovation rather than extracting them to shrink the budget. Annual tech spend grew from $11B (2018) to $14B+ (2024) while reported CTB share grew from ~30% to ~40%+ — the budget grew AND the ratio improved because modernization unlocked structural RTB reduction reinvested in change.
Annual Tech Spend
$11B → $14B+
CTB Share Shift
~30% → ~40%+
Strategic Driver
Cloud + mainframe modernization
Reinvestment Discipline
Savings → product innovation
RTB:CTB shift requires structural reduction in RTB AND a discipline of reinvesting savings into CTB. Without both, the ratio stays stuck.
Goldman Sachs
2019-2024
Goldman Sachs publicly stated an aspirational goal of shifting IT spend from 80:20 to 60:40 RTB:CTB through their 'Engineering at Goldman' platform program. Investments included internal developer platform (DevOps tooling consolidation), cloud migration to AWS and Google Cloud, and consolidation of duplicate systems acquired through M&A. CTO David Solomon framed the ratio shift as essential to competing with fintech and digital-native players. By 2024, Goldman reported substantial progress (specific public number ~70:30) — not yet at goal but materially shifted from baseline.
Aspirational Target
80:20 → 60:40
2024 Progress
~70:30 reported
Key Investments
Cloud + IDP + system consolidation
Strategic Frame
Compete with fintech / digital natives
Stating the RTB:CTB target publicly creates accountability. Goldman's stated ambition forced disciplined annual reporting and progress tracking — even though the goal is multi-year.
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Change-the-Bank vs Run-the-Bank into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Change-the-Bank vs Run-the-Bank into a live operating decision.
Use Change-the-Bank vs Run-the-Bank as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.