Application Rationalisation
Systematically reducing the number of applications in an estate by consolidating duplicates and retiring low-value systems.
Estates accumulate. Acquisitions bring parallel systems, departments procure independently, and nothing is ever switched off because switching something off requires someone to take responsibility for the consequences.
The programme has a standard shape: inventory → capability mapping to find duplication → value and quality assessment → disposition → sequenced execution.
Where the savings actually come from, in order: retiring systems nobody uses much — licences, infrastructure, support and the security surface; consolidating duplicates onto one instance; and reducing integration count, which is a compounding saving because integrations cost more to maintain than the systems they connect.
Why it stalls, reliably:
Every system has an advocate, and the political cost of retirement is borne by whoever proposes it while the savings accrue centrally.
Data migration and retention are harder than expected — historical data must go somewhere, and the obligation to retain it often outlives the system.
Undocumented dependencies surface at cutover, which is why the discovery work is not optional.
What makes it succeed: an executive sponsor who owns the savings target, publishing the cost of each system to its business owner, and starting with genuinely unused systems to build a track record before touching the contested ones.