In short: An application landscape almost always grows faster than governance can keep pace with – redundancies, end-of-life systems, and quiet cost drains accumulate. An application portfolio analysis brings fact-based clarity: it assesses every application by business value and technical quality and translates the result into concrete decisions. This guide walks through our field-tested five-step approach – including the TIME model, assessment criteria, and roadmap. Everything here reflects real Portamus client projects.
The essentials at a glance
- An application portfolio analysis answers a simple question for every application: keep, invest, migrate, or retire?
- The TIME model (Tolerate, Invest, Migrate, Eliminate) is the established classification grid for this.
- In most large portfolios, 15–30% of applications are candidates for retirement or consolidation.
- The output is not a slide deck but a prioritised rationalisation roadmap with a business case.
Why an application portfolio analysis?
Most IT organisations know their portfolio less well than they think. Applications are introduced project by project over the years, owners change, functionality overlaps, and maintenance costs rise – often without matching business value. The result: a vague sense of running “too many systems”, but no defensible basis for decisions.
An application portfolio analysis replaces gut feeling with facts. It typically makes sense when application maintenance costs grow without business value, ahead of major ERP or platform migrations, during IT consolidation after mergers – or as a building block of Enterprise Architecture Management.
The TIME model in brief
The TIME model classifies each application along two dimensions – business value and technical quality – into four quadrants:
| Quadrant | Business value | Technical quality | Decision |
|---|---|---|---|
| Tolerate | low | high | Keep, do not invest further |
| Invest | high | high | Develop deliberately |
| Migrate | high | low | Move to a viable platform |
| Eliminate | low | low | Retire / consolidate |
The appeal of the model lies in its clarity: an assessment turns straight into a recommended action. What matters, though, is filling the two axes cleanly and traceably – and that is exactly what a structured approach delivers.
Application portfolio analysis: the five-step approach
Step 1 – Inventory and discovery
First comes a complete application inventory: which applications actually exist, who owns them, what costs (licence, operations, maintenance) they incur, and what integration dependencies exist. Each application is mapped to a business capability. In practice, this step regularly surfaces shadow IT and “forgotten” systems. If no reliable inventory exists, an IT Landscape Analysis is the usual starting point.
Step 2 – Fitness assessment
Each application is assessed for fitness for purpose: business fit, actual usage, technical health, vendor lifecycle status, and user adoption. This is where the two TIME axes are given substance – based on structured stakeholder interviews and, where available, data from the architecture repository.
Step 3 – TIME classification
Now each application is assigned to a TIME quadrant, and the classification is validated with business and IT stakeholders. Cross-domain applications require alignment across several business owners – we facilitate this in focused workshops so the classification holds up rather than existing only “on paper”.
Step 4 – Consolidation and TCO analysis
For the prioritised candidates – especially in the Migrate and Eliminate quadrants – we estimate the savings potential (licence, support, and integration costs) and assess migration complexity. This produces a realistic picture of effort versus benefit for each rationalisation initiative.
Step 5 – Roadmap and business case
The outcome is a phased rationalisation roadmap, sequenced by business impact and migration complexity, underpinned by a financial business case. Leadership gets a basis for decisions they can act on immediately.
Which assessment criteria matter most?
To make the TIME axes robust, we make them concrete through several criteria:
- Business fit and usage – Does the application cover a needed capability, and is it used?
- Technical health – architecture, technical debt, stability, changeability.
- Vendor lifecycle and support – end-of-life risk, upgradeability, vendor lock-in.
- Total cost of ownership – all cost types relative to business value.
- Integration dependencies – how deeply embedded, how high the retirement/migration complexity?
- Compliance and security – regulatory and security risk.
Typical outcomes
A cleanly executed assessment delivers a validated application catalogue, a portfolio heat map, a TIME classification register, a rationalisation roadmap, and a business case. The lever is real: when the identified Eliminate and Migrate candidates are consistently acted on, licence savings, lower support costs, and a simplified integration landscape typically contribute to measurable TCO reduction within 2–3 years.
Methodological basis
We work methodologically on the basis of TOGAF and model outcomes, where it makes sense, in ArchiMate – keeping the analysis traceable, reusable, and connected to the rest of your architecture work. How the two standards work together is explained in our article TOGAF vs. ArchiMate.
Conclusion
An application portfolio analysis turns a tangled landscape into a clear basis for decisions. The TIME model provides the grid, the structured five-step approach the substance – and the roadmap the path. Assessing your application portfolio before launching the next major programme means investing more deliberately and cutting costs sustainably.
Ready to assess your application portfolio and reduce costs? We guide you from the inventory to a defensible roadmap. → Discover Application Portfolio Management from Portamus