Central groups that control maintenance budgets can let a rival unit's systems decay until failures pile up, then present the new centrally controlled platform as the only safe way out.
An example
For two decades a regional airline had run its maintenance through a network of regional shops overseen by the vice president of operations. The new fleet director chaired the capital allocation committee, and for three budget cycles the tooling refresh for the regional shops was deferred while new hires for senior mechanics went to a central hub. The regional shops' turn times lengthened, deferred items grew, and two aircraft sat out of service waiting for parts that the hub's system controlled. The board risk report listed the regional network as an operational risk, with charts of the delays. The committee approved consolidation into the hub. By the time the vice president assembled the capital history, the leases on two regional hangars had been allowed to lapse, and going back would have meant grounding aircraft.
Why it works
Failure changes the politics of migration. Once the legacy setup is visibly failing, its users lose their "it works, leave us alone" defense, and moving becomes the low-risk choice. Starving maintenance destroys the old system's main benefit, its reliability for the people who use it. The costs of staying (outages, missed service levels, audit findings) land on the resistant unit and its reputation. When licenses, integrations, and staff are allowed to lapse first, going back becomes a failure in its own right. Deniable control of the budget, a "sunsetting" story, a unit without its own funding, and evaluators who look at symptoms and never at the resource history are what it runs on.
The thinking behind it
Oliver E. Williamson Williamson's The Economic Institutions of Capitalism (1985) explains that once relationship-specific investments are made, the parties are locked to each other. When data, integrations, and trained staff are moved onto the new platform and the old system's licenses and maintainers lapse, every user has made a specific investment in the new system. Going back stops being a choice, which is why parallel runs and funded fallbacks are the defense: they keep the investment reversible.
Lee Ross In The Intuitive Psychologist and His Shortcomings (1977), Ross named the fundamental attribution error: observers explain behavior by personal traits and underestimate the situation, even when the situational pressures are plain. Evaluators who see a failing system blame the unit that runs it and overlook the years of skipped funding behind the failures. Putting the resource history beside the incident history corrects the attribution.
Thomas C. Schelling Schelling's The Strategy of Conflict (1960) argues that the power to bind oneself, by visibly removing the option to retreat, forces the other side to adjust. A decommissioning calendar that lets the legacy system's leases and licenses lapse before the replacement is proven is a commitment of that kind, made on the organization's behalf. Reading that calendar closely, and insisting on a parallel run, keeps the retreat option open.
Warning signs
Incidents rise on a system after its maintenance headcount, refresh cycle, or patch cadence was cut. Leadership calls it sunsetting before any replacement is proven. Refresh cycles for one unit are skipped for several quarters, and the person skipping them chairs the committee that allocates capital. Licenses, integrations, and maintainers lapse ahead of the cutover. The old platform is frozen at its last version and cut off from upstream feeds. Incident reports show symptoms and leave the funding history out.
How to defend yourself
Treat the maintenance budget as part of the politics and track it as closely as the org chart.
- Raise under-resourcing in writing, as a budget issue, before the decay shows. Raised late, the same point sounds like an excuse.
- When replacement comes up, put the resource history beside the incident history for the decision-makers.
- If you have your own budget, fund or in-source the maintenance.
- Read the decommissioning calendar as closely as the talking points.
- Ask the chief financial officer, audit committee, or board to require a parallel-run period, keep exit ramps in contracts, and fund a fallback until the new system is proven.
How a leader shuts it down
Separate the people who fund maintenance from the people who sponsor the replacement. Require incident reviews and board risk reports to show resourcing history next to symptoms. Make a proven parallel run the condition for retiring anything critical. Treat a failure that follows a funding cut as a question about the funding before it becomes an argument for replacement.