Application Rationalization
Definition
Application Rationalization
Application rationalization is a periodic review that sorts every system in an estate into keep, merge, replace or retire. It is a decision exercise, not a clean-up project — the hard part is agreeing which applications lose their funding.
Estates grow by accretion. Mergers bring duplicates, departments buy their own tools, and nothing is ever switched off because somebody somewhere still uses it once a quarter.
The review imposes a single comparison across all of them. Each application is scored on business value and technical health, then placed in one of four dispositions on that basis.
Savings are real but slow. Licence costs stop at the renewal date, infrastructure costs stop at decommissioning, and staff costs only fall when the supporting team is redeployed — typically a year or more after the decision.
Key takeaways
- Every application is scored on business value and technical health, then given one disposition.
- The four standard outcomes are tolerate, invest, migrate and eliminate.
- Duplicate capability across business units is the largest single source of savings.
- Benefits lag decisions by months, because licences and contracts run to their terms.
How it works
The review starts with an inventory, because most organisations cannot say how many applications they run. Discovery tooling and expense analysis usually find between 20 and 40 percent more systems than the official list holds.
Each application then gets two scores. Business value covers how many people depend on it and what breaks without it. Technical health covers supportability, security posture, integration debt and vendor viability.
Plotting both produces four quadrants — and each quadrant carries a standard action. High value with poor health means invest or replace. Low value with poor health means eliminate, and that is where most of the savings sit.
| Business value | Technical health | Disposition |
|---|---|---|
| High | Good | Tolerate and maintain |
| High | Poor | Invest or re-platform |
| Low | Good | Consolidate into a shared instance |
| Low | Poor | Eliminate |
Public-sector practice pushes hard on the consolidation quadrant. The UK Technology Code of Practice asks organisations to “avoid duplicating effort and unnecessary costs by collaborating across government and sharing and reusing technology, data, and services”.
Architecture frameworks supply the method underneath. The Open Group’s TOGAF standard is described by its authors as a proven approach “used by the world’s leading organizations to improve business efficiency”, and rationalization is one of its ordinary outputs.
Examples
Rationalization looks different depending on what created the duplication in the first place. The examples below come from three common triggers, and each produces a different shape of saving.
A manufacturer completing an acquisition finds four expense systems across the merged group. Consolidating to one removes three licence contracts, but the cost-benefit case only clears once the migration effort is priced in alongside it.
A bank facing a data-centre exit reviews 900 applications before choosing what moves. Anything scored low on both axes is left behind, which turns a private cloud outsourcing programme into a smaller, cheaper migration.
A retailer running annual licence true-ups uses software audit tools to find seats nobody has logged into for a year. Reclaiming those seats funds the rest of the exercise without retiring a single system.
Related terms
Rationalization overlaps with several adjacent disciplines, and the differences are about scope rather than method. Each entry below handles one part of the estate question, so they are worth reading as a set.
- IT transformation outsourcing: the programme that carries out what the review decides.
- Application maintenance outsourcing: the running cost the review is trying to reduce.
- Architecture outsourcing: the design capability that scores technical health.
- Shared services: the operating model that consolidation usually feeds into.
- Cloud based: the destination for most of the survivors.
FAQ
How often should the review run?
Annually for the scoring refresh, with a deeper pass every three years. Anything more frequent produces churn without changing enough decisions to justify the effort.
Who decides the dispositions?
A joint group of business owners and architects. Architecture alone will under-weight political dependencies, and business owners alone will protect everything they sponsor.
What is the usual reduction in application count?
Reported reductions vary widely by estate and starting condition, so treat headline percentages with caution. Duplicate-heavy estates after a merger have the most room.
Does rationalization mean cutting costs?
Not only. It also concentrates spending on systems that matter, which sometimes means increasing investment in a high-value application with poor technical health.
Why do the savings arrive late?
Because contracts run to their terms. A decision made in March may not reduce spend until the licence anniversary, and infrastructure costs persist until the system is switched off.
How does this differ from portfolio management?
Rationalization is a periodic exercise with an end date. Portfolio management is the standing discipline that acts on its findings and keeps the inventory current between reviews.
Compare providers who can run an estate review in the Outsource Accelerator directory.
Independent
