Why TIME Without Strategy Is Just a Coloured Spreadsheet
The TIME model — Tolerate, Invest, Migrate, Eliminate — has become the default vocabulary for application portfolio management. Ask any EA practitioner how they classify their estate and they'll reach for TIME. It's simple, communicable, and widely understood. So why do most organisations that implement it end up with a beautifully coloured spreadsheet that drives almost no decisions?
The answer isn't the model. The model is fine. The problem is isolation.
How TIME Gets Implemented
In practice, most TIME implementations follow a similar pattern. Someone — usually a new EA, an IT director, or a consultant — decides it's time to understand the application landscape. A workshop is scheduled. A spreadsheet is circulated. Applications are scored against criteria: technical health, vendor support, duplication, usage.
Within a few weeks, every application has a colour. The portfolio map goes on a slide. Leadership nods appreciatively. The EA files it under "done."
Six months later, nothing has changed. The portfolio decisions that needed to happen — decommissioning the old CRM, consolidating the three HR tools, getting off the legacy middleware — are still in a backlog somewhere. The TIME assessment gathered dust.
This isn't a failure of discipline. It's a structural problem. TIME without strategic context produces a technically accurate picture of the present, not a decision-relevant guide to the future.
The Missing Dimension
When you score an application as "Tolerate," what does that mean? It's technically adequate but not worth investing in. Fine. But tolerated until when? In service of what? If your strategy calls for entering a new market in 18 months, tolerating a customer-facing application that can't support that market is a different decision than tolerating an internal scheduling tool.
The same logic applies to "Invest." Invest in what? Toward what outcome? An application supporting a strategic capability deserves a different investment rationale than one supporting a commodity process.
Without connecting TIME classification to strategic intent, you're doing technology triage, not portfolio management.
Playing to Win as the Missing Link
Roger Martin's Playing to Win framework — originally designed for corporate strategy — offers a useful structure for connecting business direction to portfolio decisions. The framework asks five cascading questions: What is our winning aspiration? Where will we play? How will we win? What capabilities must we have? What management systems are required?
The fourth question is the bridge to EA. Capabilities are the link between strategy and applications. An organisation that decides to win through operational efficiency in distribution needs different capabilities than one winning through product innovation. Those capabilities require different applications to support them.
When you overlay a capability map onto your TIME assessment, the colours get sharper. An application classified as "Tolerate" that underpins a strategic capability is actually "Invest." An application classified as "Invest" that supports a capability you've decided to exit or outsource should probably be "Eliminate."
This is not academic. One manufacturing company working through this exercise found that their legacy ERP — comfortably classified as "Tolerate" — underpinned three of their five strategic capabilities. The TIME score was technically correct. The strategic implication was the opposite.
What a Strategy-Informed TIME Model Looks Like
The mechanics are straightforward. Before scoring applications, map your strategic themes to business capabilities. Not an exhaustive capability library — that's a year's work. A focused L1-L2 map of the capabilities that actually matter to your strategy over the next two to three years.
Then, when you score applications, score them twice: once on technical health (the traditional TIME dimension) and once on strategic relevance (how directly does this application support the capabilities we've prioritised?). The intersection of those two dimensions is where the decisions live.
High technical health, high strategic relevance: Invest. Low technical health, high strategic relevance: Migrate — this is urgent, not optional. High technical health, low strategic relevance: Tolerate or exit via consolidation. Low technical health, low strategic relevance: Eliminate, and do it soon.
This four-quadrant view still uses TIME vocabulary, but the decisions it drives are grounded in where the organisation is going, not just where it is.
The Organisational Dynamic
One more thing worth saying: TIME without strategy is also vulnerable to politics. When applications are scored in isolation, business owners reliably find reasons why their applications are more strategic than they appear. The debate becomes technical. "Our system is more stable than you think." "We've just upgraded the vendor contract."
When TIME is grounded in a shared understanding of strategic priorities, the conversation changes. It's no longer about the application — it's about the capability it supports and whether that capability is strategic. That's a much harder argument to game.
This is what we built Atlas to solve — connecting TIME to strategy so the model drives decisions, not just colours.