Somewhere inside every major bank's information technology department, there is a ledger that never appears in the annual report. It carries no formal interest rate, triggers no regulatory capital requirement, and draws no scrutiny from external auditors. Yet according to veteran financial technology commentator Chris Skinner, this invisible ledger — the accumulated weight of decades of deferred technology decisions — may represent the single most consequential liability on a bank's true balance sheet. Skinner, who has spent years in direct debate with senior bank executives on the subject, has now committed his argument to writing, and his central conclusion is as blunt as it is important: the technical debt crisis in banking is not fundamentally a technology problem. It is a leadership problem.
A Debt by Any Other Name
The conceptual power of framing outdated technology infrastructure as debt is not accidental. Bank for International Settlements research and broader industry analysis have long noted that legacy systems constrain banks' ability to compete, scale, and comply — yet the liability rarely appears where bank leaders are trained to look for it. Skinner's argument exploits precisely this gap. Banks, he notes, understand debt in its conventional forms with intuitive sophistication: principal, interest, refinancing schedules, maturity profiles, covenant structures. These are the instruments of their core trade. Technical debt operates by the same economic logic — deferred cost compounds over time, the interest accrues in the form of mounting maintenance expense and competitive disadvantage, and the longer refinancing is postponed, the more painful and disruptive the eventual restructuring becomes. By rendering the analogy in the vocabulary bankers already speak fluently, Skinner removes the excuse of incomprehension. If a chief executive would never allow a credit exposure to quietly compound on the balance sheet without active management, why would that same executive permit the technology estate to do exactly that?
The Leadership-Laggardship Divide
The most provocative element of Skinner's framing is his reduction of the entire technical debt debate to two categories of executive behaviour: leadership and laggardship. The distinction is not about technical literacy. Many of the most digitally advanced banks are led by executives who came up through traditional finance rather than engineering. The differentiating factor is willingness — willingness to confront an uncomfortable liability, to fund the unglamorous work of modernisation, and to accept short-term earnings pressure in exchange for long-term structural resilience. Leaders do this. Laggards defer, delegate, and ultimately pass the problem to their successors, who inherit a compounded version of the same challenge.
This divide has material consequences that extend well beyond the technology function. Institutions carrying heavy technical debt face longer product development cycles, higher operational risk, greater vulnerability to cybersecurity threats, and structural inability to integrate with the open application programming interface ecosystems that modern Revolut, Wise, and embedded-finance players exploit as a matter of routine. The laggard bank cannot move at the speed its customers increasingly expect, not because its people lack ambition, but because its systems impose a physical ceiling on velocity. Every new product must be threaded through infrastructure that was not designed for it. Every regulatory change requires custom intervention in code that nobody fully understands anymore. The costs are real, recurring, and corrosive — they simply do not appear on a line item that the board reviews quarterly.
Why This Conversation Has Stalled
Skinner's frustration — implicit in his admission that he has argued this case with bank executives for years without sufficient resolution — points to a structural problem in how institutions process uncomfortable truths. Digital transformation programmes are frequently announced with fanfare and genuine senior commitment, only to be quietly de-prioritised when quarterly earnings come under pressure or when the complexity of the underlying modernisation work becomes apparent. The result is a cycle of partial modernisation: enough investment to generate a press release, insufficient investment to retire the underlying liability. The hidden balance sheet grows, not shrinks.
Part of the difficulty is incentive misalignment at the executive level. Chief executives and chief technology officers who will move on within three to five years have limited personal incentive to initiate multi-year, balance-sheet-stressing technology re-platforming programmes whose benefits will primarily accrue to their successors. The rational individual calculus and the rational institutional calculus point in opposite directions. Regulators at the European Banking Authority and the European Central Bank have increasingly flagged operational resilience and information and communication technology risk as supervisory priorities, which creates some external pressure — but enforcement remains uneven and the liability itself remains off the formal balance sheet.
What This Means
Skinner's framing deserves to be taken seriously by bank boards, not merely by technology teams. If technical debt is genuinely a balance sheet liability — compounding, maturity-dated, and ultimately unavoidable — then the governance question is identical to the governance question that applies to any other material risk: who owns it, how is it measured, and what is the repayment schedule? The banks that answer those questions proactively, and that treat digital modernisation as capital allocation rather than discretionary spending, are the institutions that Skinner would characterise as leaders. Those that continue to defer the reckoning are accumulating a liability that their balance sheets do not yet reflect but that their future income statements most certainly will. The hidden ledger has a due date. The only question is who will be sitting in the chief executive's chair when it matures.
Written by the editorial team — independent journalism powered by Codego Press.
Top comments (0)