In December 2022, a winter storm swept across the United States and Southwest Airlines cancelled roughly 16,900 flights. The investigation pointed to outdated IT infrastructure. The main failure was SkySolver, the tool the airline used to reassign crews when schedules break. It could not handle the volume of disruptions, and schedulers ended up sorting records by hand. The US Department of Transportation fined Southwest $140 million, about thirty times larger than any earlier penalty against a US airline for an IT failure. Most of the money is structured as compensation for future passengers, with $35 million going to the Treasury.
Nobody at Southwest chose to build a system that would fail in a storm. The tool worked for years under ordinary conditions. Technology debt accumulates in exactly that way: each year the system keeps working, the cost of replacing it feels easier to postpone.
What Technology Debt Looks Like on the Ground
Think of it as a loan taken out every time an organization chooses a shortcut, delays an upgrade or adds another connection to a system nobody fully understands. The interest arrives as outages, slow change, security exposure and staff time spent keeping old systems alive.
The United States Government Accountability Office publishes one of the few detailed inventories. The federal government spends over $100 billion a year on IT, and agencies typically report spending about 80 percent of it on operating and maintaining existing systems. GAO identified the 11 legacy systems most in need of modernization. They range from 23 to 60 years old. Eight of the 11 lacked fully documented modernization plans. Eight use outdated programming languages, and seven have known cybersecurity vulnerabilities.
Age of the 11 federal legacy systems GAO flagged as most in need of modernization, years
60 yrs
59 yrs
55 yrs
51 yrs
51 yrs
41 yrs
31 yrs
30 yrs
30 yrs
25 yrs
23 yrs
Private organizations rarely publish a list like this. The question behind it is easy to borrow: how old is the oldest system the business cannot do without, and what is the plan for it?
Five Verdicts for Every System
Modernization begins with business requirements and a current-state analysis. Each system then earns one of five verdicts:
- Retain. The system does its job, is supported and is secure. Leave it alone and say so deliberately.
- Improve. The core is sound and the surroundings need work, such as performance, security hardening or a better interface.
- Integrate. The system holds valuable data or logic that other systems cannot reach. Connect it properly and the value multiplies.
- Retire. Its function has been replaced, or nobody uses it. Switching it off removes cost and risk.
- Rebuild. The business needs something the system can never provide, or its risk has grown beyond what the organization can carry.
Most estates contain all five. A program that treats every system as a candidate for replacement spends the most money and carries the most risk. A program that assigns verdicts first usually finds that the expensive decisions apply to a short list.
How to Put the Systems in Order
A simple scoring pass across five factors gives leadership a ranked view in a few weeks:
- Business criticality. What stops if this system stops, and for how long can the business tolerate it?
- Support status. Does the vendor still support the platform, and can the organization hire people who know it?
- Security posture. Are there known vulnerabilities, and can they be fixed without changing the system?
- Integration burden. How many other systems depend on it, and how well is that documented?
- Cost to run. What does it consume each year in licences, hosting and staff time?
The crew scheduling tool at Southwest would have scored high on criticality and high on risk long before the storm. A ranked list gives the board a reason to act on that system early.
Three Questions to Ask This Quarter
- Which systems would stop a core business process if they failed tomorrow, and when were they last tested under stress?
- Which of our critical systems have a documented modernization plan with an owner and a date?
- What share of our technology budget goes to keeping the current estate running, and is that share growing?
Technology debt rewards leaders who look at it early. The interest is small enough to ignore for years, and then a storm arrives.