Three Horizons: Core, Growth, Future
Three Horizons splits energy across core defense, scaling winners, future bets at once. Use it when your roadmap is only incremental tweaks with no long-term bets. The footgun is seeing horizons as sequential stages, not parallel portfolios needing fuel today.
WHY IT EXISTS: Companies die when they optimize only for the present. Every mature business faces the innovator's dilemma: the core revenue engine demands more resources, incremental projects have clear ROI, and speculative bets look wasteful by comparison. The Three Horizons model was created to force leaders to manage the tension between extracting cash from today and building the capabilities that will matter tomorrow, so the organization does not slowly become obsolete while posting record profits.
THE MENTAL MODEL: Think of a farm. Horizon One is harvesting the mature crop that feeds you this year. Horizon Two is tending the young orchards that will produce in a few seasons. Horizon Three is planting experimental seeds that might become entirely new crops. You cannot skip to harvesting next year's fruit without tending saplings today, and you cannot survive this winter without bringing in the current harvest. All three must happen in the same calendar year with different tools and expectations.
HOW IT WORKS: Horizon One is the core business: existing products, current customers, and known margins. The goal is defend and extend, improving efficiency and maximizing cash flow. Horizon Two is emerging opportunities: proven concepts or new markets that are growing fast but not yet dominant. These need scaling investment and dedicated teams. Horizon Three is options on the future: research, prototypes, and radical experiments where success is uncertain and timelines are long. The framework insists that all three horizons receive resources simultaneously, with metrics matched to their maturity. Horizon One might target margin improvement, Horizon Two user growth, and Horizon Three learning velocity or option value.
WHEN TO USE IT: Use this when your portfolio feels lopsided. If every team is measured on quarterly revenue, you are effectively betting the entire company on Horizon One. It is also useful during planning cycles to justify protecting exploratory budgets, to explain to boards why you are funding projects with no near-term ROI, and to prevent high-growth startups from ignoring the core product that funds everything else.
WHEN NOT TO USE IT: Do not use it as a rigid chronological plan. Horizon Three is not something you start after Horizon Two succeeds; by then the market has moved. It also fails in organizations that cannot tolerate ambiguity, because Horizon Three projects will look like failures for years before they pay off. If your culture punishes teams for missing short-term metrics, the framework becomes theater.
ONE CANONICAL EXAMPLE: Amazon in the early 2000s ran Horizon One with its core retail marketplace, Horizon Two with the growth of third-party seller services, and Horizon Three with Amazon Web Services. Web Services began as a small internal platform with no clear retail revenue, treated as an experiment. Because leadership protected that Horizon Three bet while still optimizing retail, AWS eventually became the company's largest profit engine. The parallel investment was the point.
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.