TIME Portfolio Triage

The idea

TIME is Gartner's way of triaging an application portfolio. Each application gets two scores: how much business value (functional fit) it delivers, and how good its technical quality (technical fit) is. The two scores place it in one of four quadrants:

1. Invest — high value, high quality. Keep developing it; it supports what the business needs and is sound.
2. Migrate — high value, low quality. The business needs what it does, but the technology is weak; move the function to a better platform.
3. Tolerate — low value, high quality. It works and is cheap to keep; leave it alone and spend nothing extra.
4. Eliminate — low value, low quality. Retire it.

The result is a portfolio view that says where to spend, where to move and where to stop.

Why it works

It separates two questions people blur. Business owners judge value; architects and operations judge quality. Scoring them separately stops a loved but fragile system, or a sound but pointless one, from hiding in the middle.

It turns a list into actions. An inventory of 600 applications tells nobody what to do. Four quadrants each come with a default decision and a funding posture.

It gives a shared language. "That's a Migrate" is quicker to argue about than a page of scores, and makes portfolio reviews faster.

Where it applies

• Application rationalisation after a merger or a period of uncontrolled growth.
• Annual budgeting and roadmaps, to steer spend away from Tolerate and Eliminate and towards Invest and Migrate.
• Cloud and data-centre exits, to decide what to move, rebuild or switch off before migrating anything.
• Regulatory and risk reviews, where low-quality applications holding critical processes need a plan.

How to apply

1. Fix the unit and scope. Decide what counts as an application and map each to the business capabilities it supports.
2. Score value and quality separately. Business owners rate functional fit; technical owners rate maintainability, risk, cost and alignment with standards. Agree the scales first.
3. Plot and challenge. Put the results on the grid and review outliers and anything close to a boundary with both groups.
4. Attach an action and a date. Every Migrate needs a target and funding; every Eliminate needs an owner and a switch-off plan.
5. Repeat yearly. Value and quality drift; a Tolerate can become an Eliminate when its last user moves.

Example scenario

An insurer's estate had grown to 420 applications after two acquisitions, and run costs were eating the change budget. Every review stalled because each system had a defender.

The enterprise architects ran TIME across the portfolio with business and technical owners scoring separately. Ninety applications landed in Eliminate, most of them duplicate reporting tools and acquired portals with few users. Twelve core policy and claims systems were Migrate. The board funded the Migrate list as a three-year programme and set a quarterly switch-off target for Eliminate, paid for by the licence and hosting savings.

Questions to ask

When not to use it

• Small portfolios, where a conversation with each owner is quicker than a scoring exercise.
• Strategic shifts, where future value matters more than current fit; pair TIME with capability mapping or a target operating model first.

How it misleads you