1. What Is McKinsey Three Horizons of Growth?
The McKinsey Three Horizons of Growth is a corporate and portfolio strategy framework that helps leaders balance performance today with the creation of tomorrow’s growth engines. It segments a company’s growth initiatives into three “horizons” that differ in maturity, risk, and management approach:
- Horizon 1 (H1): Core businesses at scale that require continuous improvement and defend/extend measures.
- Horizon 2 (H2): Emerging businesses with product–market fit in sight that need scaling, resource infusion, and selective innovation.
- Horizon 3 (H3): Options for future growth—early-stage ideas, experiments, or technologies being validated.
In plain terms, it is a portfolio lens and operating discipline for running the present, building the near future, and planting seeds for the longer term—at the same time. It is commonly used by consultants and executive teams to set growth ambition, shape resource allocation, and design governance and metrics appropriate to each horizon.
Crucially, the Three Horizons model is not only about time. While “horizon” once mapped loosely to years, practitioners today use it to reflect the maturity and uncertainty of initiatives. Some H3 bets can mature quickly; some H2 scale-ups may take years. The value is in matching management style, metrics, and capital to the maturity of each initiative.
2. Origin and Background
The framework was developed and popularized within McKinsey & Company and brought to a broad audience by Mehrdad Baghai, Stephen Coley, and David White in the 1999 book “The Alchemy of Growth.”
Why it was created: Many companies either starved innovation to prop up the core or chased distant opportunities while neglecting near-term performance. The Three Horizons concept provided a simple, shared language and structure to manage a balanced growth portfolio—protecting and optimizing H1 while systematically building H2 and planting H3 options.
How it became known: The book, subsequent articles, and widespread consulting practice embedded the model in corporate strategy toolkits and business school curricula. Over time, it has been adopted beyond strategy—informing budgeting, R&D governance, venture incubation, and corporate venture capital.
3. How McKinsey Three Horizons of Growth Works
The framework segments initiatives into three horizons and prescribes distinct objectives, operating modes, and metrics for each.
Horizon 1: Run and Extend the Core
- What it is: Mature, cash-generative businesses with clear customers, channels, and economics.
- Management focus: Defend share, improve productivity, optimize pricing, refresh offerings, and reduce risk.
- Typical metrics: Revenue and margin, cash conversion, ROIC, share, NPS, productivity/quality.
- Examples: Core product lines, flagship geographies, established service franchises.
Horizon 2: Scale Emerging Growth Engines
- What it is: Adjacent businesses and scale-ups with evidence of product–market fit and repeatability, but not yet at core scale.
- Management focus: Accelerate growth, professionalize operations, build capabilities, and selectively invest ahead of demand.
- Typical metrics: Growth rate, unit economics (CAC/LTV, contribution margin), sales productivity, time-to-breakeven, leading indicators of adoption and retention.
- Examples: New geographies showing traction, digital add-on services to a physical product, initial platform monetization.
Horizon 3: Create Options for the Future
- What it is: Seed-stage ideas, explorations, or technologies under validation; uncertain but potentially material in the future.
- Management focus: Learn quickly and cheaply. Run experiments, validate customer problems and solution feasibility, and stage-gate further investment.
- Typical metrics: Problem/solution validation, technical feasibility milestones, time to proof points, option value, cost-to-learn, and kill/scale decisions hit rate.
- Examples: New business model pilots, early AI products, novel channel experiments, moonshots in R&D.
Portfolio logic and transitions
- Balance across horizons: Set overall ambition (e.g., percentage of growth from H2/H3 in 3–5 years) and target resource allocation (often—but not dogmatically—similar to 70/20/10 across H1/H2/H3, adapted to context).
- Stage-gates and governance: H1 uses annual/quarterly performance cycles; H2 blends commercial scale-up reviews; H3 uses venture-style gates (e.g., discovery → validation → build).
- Transitions: Define criteria for moving an initiative from H3 to H2 (validated problem/solution, early unit economics) and from H2 to H1 (repeatable growth engine, positive returns at scale). Avoid “horizon drift,” where H3 languishes or H2 is held to H1 standards prematurely.
- Capabilities and talent: Different skills dominate by horizon—operators and optimizers in H1; scale builders and cross-functional leaders in H2; entrepreneurial, customer-discovery, and R&D talent in H3.
In practice, companies create a visual “horizons map” of initiatives, codify resourcing rules, and embed horizon-specific metrics and cadences into planning and performance management.
4. When to Use McKinsey Three Horizons of Growth
Most helpful for:
- Multi-business corporations that need a common language to balance today’s performance with future bets across divisions.
- Mid-to-large enterprises seeking disciplined growth beyond the core while protecting cash-generative franchises.
- Sector contexts where technology or regulation is changing the game and leaders must nurture new engines without derailing the core.
- Strategy refresh cycles to translate a growth ambition into an executable portfolio, capital plan, and operating model.
Especially powerful when:
- Short-term pressures crowd out innovation, and leadership needs explicit, protected capacity for H2/H3.
- The organization struggles to compare unlike initiatives (e.g., a plant debottlenecking vs. a software venture).
- You need to move from “innovation theater” to evidence-based, staged investment in new growth.
Less effective or potentially misleading when:
- Teams equate horizons strictly with calendar years (e.g., H3 = 5+ years), leading to misclassification and poor governance.
- The core is structurally unattractive or underperforming and requires transformation first; horizons won’t fix a broken H1 thesis.
- It’s treated as a labeling exercise, without changing resource allocation, metrics, or talent to fit each horizon.
Practice evolution: Modern practitioners treat the horizons as maturity and uncertainty bands rather than rigid timeboxes, use venture-style governance for H3, apply product/lean metrics for H2, and pair the model with explicit capital rules and real-options logic. The framework remains widely used, but more dynamically than in its early, time-based form.
5. How to Apply McKinsey Three Horizons of Growth: Step-by-Step
- Clarify growth ambition and time frame
Define where growth must come from over 3–5 years (organic vs. inorganic), the role of new businesses vs. core, and the minimum contribution you expect from H2/H3. Articulate the strategic problem this portfolio must solve (e.g., offsetting core decline, capturing adjacencies, leapfrogging with new tech).
- Inventory the current portfolio and classify by horizon
List all material initiatives across businesses (core improvement, adjacencies, new ventures, platform bets, M&A theses). Classify each into H1/H2/H3 based on maturity and uncertainty, not age. Document for each: value-at-stake, stage, owner, and next major milestone.
- Define horizon-specific criteria and metrics
Set explicit criteria for each horizon:
- H1: ROIC, EBITDA uplift, share, productivity, risk reduction.
- H2: growth rate, contribution margin, sales productivity, retention/cohorts, CAC/LTV, breakeven path.
- H3: validated customer problem, prototype/technical feasibility, early unit signal, partner interest, cost-to-learn.
Align on decision cadence and stage-gates by horizon.
- Size value-at-stake and risk-adjusted returns
Estimate ranges for revenue, margin, capital required, and probability of success for each initiative. For H3, focus on option value and cost-to-learn; for H2, use scenario-weighted NPV; for H1, use standard financials. Avoid false precision; comparability matters more than exactness.
- Set portfolio guardrails and allocation targets
Agree top-down resource envelopes (capital, OPEX, leadership bandwidth) by horizon and business. The oft-cited 70/20/10 split can be a starting point but must be tailored to industry maturity, disruption risk, and balance sheet.
- Decide initiative-level funding and milestones
Allocate capital and talent to initiatives with clear milestone-based tranches:
- H1: fund fully when NPV and risk are attractive; hold teams to operational KPIs.
- H2: tranche funding tied to unit economics and scale milestones; invest ahead of demand selectively.
- H3: small “seed” tranches to buy learning; scale only upon hitting validation gates.
- Design governance and operating model by horizon
Establish who decides and how:
- H1: business reviews, cost/productivity councils, risk committees.
- H2: growth boards with cross-functional leaders (sales, product, ops, finance) and customer metrics.
- H3: venture board that runs discovery/validation gates, approves pivots, and enforces kill criteria.
Ring-fence H3 from H1 processes that would slow it down; ensure H2 does not get held to H1 ROI hurdles prematurely.
- Align talent, incentives, and capabilities
Match leaders to horizons (operators in H1, scale builders in H2, entrepreneurs in H3) and tailor incentives. Build enabling capabilities: experimentation tooling for H3, product-led growth and pricing for H2, continuous improvement for H1.
- Communicate the horizons map and narrative
Create a visual portfolio map with initiatives, values, milestones, and owners. Share the “why” and the rules of engagement broadly to align investors, boards, and teams.
- Run the cadence and refresh
Hold horizon-specific reviews monthly/quarterly. Move initiatives across horizons when criteria are met. Rebalance allocation at least annually or when disruption/market shifts occur.
6. Example: Three Horizons in Action
Context: A $2.8B global industrial automation company with strong H1 businesses in motion control and sensors. The CEO aims to accelerate growth to 9–11% CAGR while digitizing offerings and creating data-driven services.
Problem: Core growth has slowed; competitors are bundling software. The company has scattered pilots in predictive maintenance and robotics but no coherent growth portfolio or governance. Capital is constrained, and short-term cost pressures are high.
Applying the Three Horizons framework:
- Portfolio inventory and classification:
- H1: Pricing/pack refresh for sensors, a lean transformation in two plants, and a channel mix optimization in DACH.
- H2: A predictive maintenance service for installed motors with first lighthouse customers; an integrated safety system bundle in two verticals.
- H3: An AI-based vision inspection prototype; a subscription platform concept for mid-market OEMs; a JV idea for cobotics accessories.
- Value sizing: H1 initiatives show 180–220 bps EBIT uplift. H2 has a $250–400M revenue potential at 20–25% gross margin over 3–4 years. H3 options have high uncertainty but a combined option value of ~$50–100M with small seed investment.
- Allocation targets: Leadership sets a tailored allocation: 72% H1, 20% H2, 8% H3 for year one, with a glidepath to 65/25/10 by year three if H2/H3 gate progress holds.
- Governance: An H3 venture board is created with monthly discovery gates; H2 growth boards are set in the two target verticals; H1 continues under operational reviews with new pricing forums.
- Milestones:
- H2 predictive maintenance: reach 50 paying sites, 80% gross retention, and field-service productivity uplift by 15% within 12 months.
- H3 vision AI: achieve 95% defect detection on three reference datasets; secure two design partners; decide on productization vs. partner route.
- Talent and incentives: A growth GM with SaaS experience is appointed for H2; H3 teams get milestone-based variable pay; H1 leaders’ incentives include a modest growth component to support cross-sell into services.
Outcomes (18 months): H1 achieves 190 bps EBIT uplift and recovers 2 points of share in sensors. H2 predictive maintenance hits milestones and scales to $85M run-rate with 24% gross margin; the safety bundle expands to a second region. H3 vision AI validates technically but fails commercial tests in a key vertical; the team pivots to partner-first monetization. Overall growth accelerates to 9.4% with a visible path to 10–11%, and the board gains confidence in the disciplined pipeline.
7. Strengths and Limitations
Strengths
- Creates a simple, shared language to balance short-term performance and long-term growth.
- Clarifies management approach, metrics, and governance appropriate to the maturity of each initiative.
- Enables disciplined, staged investment—particularly for early-stage H3 bets—reducing “innovation theater.”
- Supports transparent resource allocation across unlike opportunities and counters present-bias in budgeting.
- Helps manage leadership bandwidth by separating H1 operational cadence from H2/H3 growth governance.
Limitations
- Can be misused as a rigid time map (e.g., H3 = “five-year bets”), leading to misclassification and poor decision-making.
- Risk of labeling without action if incentives, capital rules, and governance are not adjusted by horizon.
- Oversimplifies interdependencies; some initiatives straddle horizons and require hybrid governance.
- May underweight existential core issues; a weak H1 cannot be patched by H3 options alone.
- Requires strong portfolio analytics and stage-gate discipline; otherwise H2/H3 become pet projects.
8. Common Pitfalls (and How to Avoid Them)
- Equating horizons with years
What goes wrong: Fast-moving H3 ideas never get funded; slow H2 scale-ups are treated like H1.
How to avoid: Classify by maturity and uncertainty; set explicit criteria for each horizon. - Applying H1 metrics to H2/H3
What goes wrong: Early ventures are strangled by ROI hurdles meant for the core.
How to avoid: Use discovery and unit-economic milestones; tranche funding to evidence. - Starving H2 while over-funding diffuse H3
What goes wrong: Many small experiments, but nothing scales.
How to avoid: Protect H2 with dedicated capital and talent; cap the number of H3 bets; enforce kill criteria. - Innovation theater without kill rules
What goes wrong: Pet projects linger; costs accumulate without learning.
How to avoid: Predefine validation gates and “stop” thresholds; celebrate well-run terminations. - No clear path between horizons
What goes wrong: H3 never transitions; H2 stalls at subscale.
How to avoid: Document transition criteria and integration plans; assign owners for the “lift” from H3→H2 and H2→H1. - Single-speed operating model
What goes wrong: H1 processes (procurement, compliance, budgeting) slow H3 discovery and H2 scale-ups.
How to avoid: Ring-fence H3; create fast lanes and tailored governance for H2/H3. - Ignoring talent fit
What goes wrong: Operators are placed to build ventures; entrepreneurs are asked to run the core.
How to avoid: Staff horizons with the right profiles; enable rotations at transition points.
9. How McKinsey Three Horizons Relates to Other Frameworks
- Ansoff Product–Market Matrix: Ansoff describes directions of growth (market/product). Three Horizons structures the portfolio and governance across maturity stages for those growth moves.
- BCG Matrix / GE–McKinsey Nine-Box: These assess current business attractiveness and strength. Use them for H1 portfolio health and to identify candidates for H2/H3 seeding; Three Horizons then manages the growth journey.
- Adjacency Expansion Matrix: Use adjacency scoring to prioritize near- vs. far-core moves; map selected moves into H2/H3 and govern accordingly.
- Real Options and Stage-Gate: Three Horizons benefits from real-options thinking and stage-gate processes, especially for H3 experiments and H2 scale-ups.
- Lean Startup / Product Operating Model: Lean methods provide the tactics for H3 validation and H2 product–market fit; Three Horizons provides the enterprise-level portfolio frame.
- Corporate Scope / Make–Buy–Ally: Once a horizon initiative is chosen, scope and governance frameworks decide ownership (own vs. partner) and integration path.
- OKRs / Performance Management: Apply different OKR patterns and KPIs per horizon—outcome and discovery metrics in H3, unit and scaling metrics in H2, financial and operational metrics in H1.
10. Key Takeaways
- The McKinsey Three Horizons of Growth balances running today’s core with building tomorrow’s growth engines.
- Classify initiatives by maturity and uncertainty—not by calendar—into H1, H2, and H3, and tailor metrics, talent, and governance to each.
- Set explicit portfolio allocation targets and stage-gate funding to evidence; protect H2 from being crowded out and cap H3 bets.
- Define transition criteria between horizons and run distinct cadences to avoid “single-speed” management.
- Pair the framework with adjacency, real-options, and product/lean tools to turn ambition into disciplined execution.
11. FAQs About McKinsey Three Horizons of Growth
Is the Three Horizons framework still relevant today?
Yes. If anything, it’s more relevant as technology compresses cycles. Practitioners treat horizons as maturity/uncertainty bands, not rigid timeframes, and combine them with lean, product, and real-options practices to manage faster transitions.
How is this different from the BCG matrix?
BCG assesses current businesses based on market growth and share to guide resource allocation within H1. Three Horizons governs the evolution of growth initiatives across stages—from core improvements to scale-ups and options—using different metrics and cadences.
What is the right resource split (e.g., 70/20/10)?
There is no universal ratio. 70/20/10 is a helpful starting heuristic, but the right allocation depends on industry maturity, disruption risk, and balance sheet. Set targets based on value-at-stake and refresh as initiatives pass gates.
Can small or mid-market companies use it?
Absolutely. A lightweight version works well: list initiatives, tag H1/H2/H3, set two or three milestones per initiative, and earmark modest budgets for H3 learning. The discipline matters more than the formality.
How do we measure success in H2 and H3?
For H2, focus on unit economics, customer adoption/retention, and repeatable scaling. For H3, use discovery metrics (validated problem, solution, and viable unit signals), cost-to-learn, and milestone hit rates. Avoid holding them to H1 ROI too early.
How long does it take to implement a horizons-based portfolio?
A pragmatic first pass can be done in 4–6 weeks: 1–2 weeks to inventory and classify, 1–2 weeks to size value/uncertainty and set allocation targets, and 1–2 weeks to establish governance and milestones. Embedding cadences and incentives follows over subsequent quarters.




