Application Portfolio Management
Managing the set of applications as an investment portfolio — deciding what to invest in, maintain, contain and retire.
Definition
Portfolio management treats applications as investments with different returns and different lifecycles, and allocates deliberately rather than by inertia.
The two axes that produce decisions
Business value — how much the application matters, how differentiating it is, how much it is used.
Technical health — supportability, security posture, change cost, skills availability, obsolescence risk.
| Value | Health | Action |
|---|---|---|
| High | High | Invest. Keep it healthy |
| High | Low | Remediate or replace. The urgent quadrant |
| Low | High | Maintain cheaply. Resist the urge to modernise |
| Low | Low | Retire. The largest available saving |
The bottom-right quadrant is where most of the money is, and it is where organisations act least, because retirement has no champion.
Why retirement is the hardest and most valuable
Nobody is promoted for switching something off. There is no launch, no feature, and a small risk of breaking something. So applications accumulate, each costing licences, infrastructure, patching, security review and a share of attention, indefinitely.
Making it happen requires:
- A named owner for the retirement, with time allocated.
- Consumer identification — usage data, not assumptions.
- A migration path for the consumers who remain, which is the real work.
- Budget for the decommissioning, explicitly, or it competes with features and loses.
- Tracking "applications retired" as a metric with the same visibility as applications delivered.
Assessing honestly
Self-assessed health is always amber. Use evidence: incident count, change lead time, patch currency, open vulnerabilities, and — the most revealing — how many people are willing to work on it.
For value, use evidence too: actual usage data frequently reveals that an application everyone described as critical has forty users, three of whom are its own support team.
Failure scenarios
- Assessment without action, producing a report and no change.
- Everything classified as critical, because nobody will say otherwise.
- Retirement never funded, so the portfolio only grows.
- Health self-assessed by the owning team.
- A rationalisation programme that consolidates onto the wrong survivor, because the decision was made on system quality rather than on capability fit.
Interview question
"An estate has 300 applications and the organisation cannot support them. How do you decide what to retire?"