TIME Model

The TIME model is one of the most common ways to turn an application portfolio review into decisions. Each application is scored on two dimensions: how much business value it delivers and how sound its technology is. Plotting the scores on a simple grid places every application in one of four quadrants, each with a recommended action: tolerate, invest, migrate or eliminate. The model was popularized by the research firm Gartner and is widely used in application portfolio management and rationalization programs.

The appeal of the TIME model is its simplicity. Business leaders, architects and finance teams can all understand a four-box grid, and it gives a consistent starting point for discussing hundreds of applications. It does not replace judgment, but it focuses attention on the applications where action will make the most difference. For IT strategy and finance, the model links portfolio analysis to budget decisions, showing where to spend more, where to hold steady and where to cut.

Definition of the TIME Model

The TIME model is a two-by-two classification of applications used in application portfolio management. One axis measures business value, sometimes called functional fit, and the other measures technical quality, sometimes called technical fit.

The name is an acronym for the four recommended actions. Each action applies to one combination of high or low business value and high or low technical quality.

The Four Quadrants

Tolerate applies to applications with high technical quality but low business value. They work well enough and cost little to keep, so the organization maintains them without further investment.

Invest applies to applications with high business value and high technical quality. These are the organization's strongest systems, and further investment is likely to pay off.

Migrate applies to applications with high business value but low technical quality. The function matters, but the technology is a problem, so the organization moves the capability to a better platform or modernizes it.

Eliminate applies to applications with low value and low technical quality. They are candidates for retirement, with users and data moved elsewhere where needed.

Measuring Value and Quality

Business value usually combines user satisfaction, the importance of the capabilities supported, how well the application meets current needs and its contribution to strategy.

Technical quality usually combines vendor support status, the age of the technology, security exposure, reliability, integration complexity and the level of technical debt.

Scores are typically gathered through short surveys of application owners and users, supported by technical data. Using the same questions for every application keeps comparisons fair.

Importance of the TIME Model in Enterprise Architecture

The TIME model turns a long inventory into a short list of actions. Instead of debating each application separately, leaders can agree on rules and apply them consistently.

It links architecture to budgets. Invest applications receive development funding, tolerate applications receive only maintenance, and migrate and eliminate applications feed modernization and retirement plans. This connection makes it easier to explain why budgets for some applications rise while others are frozen.

It also makes trade-offs visible to business leaders, who can see why a familiar application has been marked for elimination and what it scored on each dimension.

Adding Cost to the Model

The standard TIME model does not include cost directly. Two applications in the same quadrant may differ greatly in what they cost to run.

Many organizations add total cost of ownership as a third dimension, often shown as the size of each point on the grid. This highlights expensive applications in the eliminate and migrate quadrants, where action will save the most.

Cost also helps prioritize within a quadrant. An eliminate application costing $500,000 a year is usually a higher priority than one costing $10,000. The same applies to migrate applications, where the most expensive systems on weak technology usually offer the largest combined benefit from modernization.

Limitations

The model simplifies complex situations. An application with moderate scores may sit near the center of the grid, where a small change in scoring moves it between quadrants.

It does not account for dependencies, so an application marked for elimination may support others that must be changed first. Checking dependencies before confirming each decision avoids surprises during retirement.

Scores can also be influenced by the people providing them. Combining survey results with objective data such as login counts and incident rates improves reliability.