Three Horizons Analysis

Prime #

462

Origin domain

Futurism & Strategic Foresight

Also from

Organizational & Management Science

Aliases

Three Horizons Framework, Three Horizons Model, H1 H2 H3 Framework, Sharpe Hodgson Three Horizons, Mckinsey Three Horizons

Related primes

Scenario Planning, Backcasting, Visioning, Causal Layered Analysis (CLA), Systems Thinking, disruption theory

Core Idea

(1) Three Horizons Analysis is a structured framework for mapping the transition from current-dominant systems to emergent future systems by partitioning the forward-view into three overlapping horizons: H1, the current system with its near-term improvement trajectory; H2, the transitional space where disruptive innovations and alternative approaches are emerging and contesting the incumbent; and H3, the long-term transformative space where fundamentally different systems become possible and eventually viable. (2) The distinctive focus is on tri-layer temporal mapping with explicit attention to the dynamics between layers: how H1 (the fit-for-current-context dominant system) declines over time while H3 (the fit-for-future-context emergent system) grows, with H2 (the transitional space) as the contested zone where pioneers, entrepreneurs, and change agents operate — distinct from linear long-range planning (which treats the future as continuous extension of the present), from pure scenario planning (which focuses on alternative futures rather than transition dynamics), and from simple horizon-by-calendar-date planning (which lacks the system-transition structure). (3) The method typically involves: specifying the domain and scope; characterizing H1 (current dominant system, its strengths, its stress indicators); envisioning H3 (the transformed future system, its values, its operating principles); identifying H2 activities and actors (pockets of innovation, alternative approaches already emerging that point toward H3); analyzing transition dynamics (how H1 pressures, H2 innovations, and H3 aspirations interact); and developing strategy across all three horizons (maintain and improve H1 while H2 matures; invest in H2 and H3 even while H1 continues to produce value). (4) The deeper abstraction is that system change is rarely instantaneous substitution; it is overlapping transition in which the old system continues to produce value while the new system emerges, and strategic effectiveness requires simultaneous investment across all three horizons rather than premature abandonment of the first or premature commitment to the third. The framework also introduces an explicitly normative dimension — H3 is not merely "what will happen" but "what should emerge" — that connects strategic analysis to vision and values in a way that purely descriptive foresight methods do not.

How would you explain it like I'm…

Now, Soon, Later

Imagine your school is great now but in a few years there might be a much better way to learn, and right in between are some new ideas teachers are trying out. Three Horizons is a way to think about all three at once: today's school, the in-between experiments, and the cool future school — so you keep today running, try the experiments, and dream up the future, all together.

Three Time Horizons

Three Horizons Analysis is a planning tool that looks at the future in three layers. Horizon 1 is how things work today — the current system, which still gives value but is slowly running out of steam. Horizon 3 is the very different future system you want, far ahead. Horizon 2 is the messy middle — the new ideas, experiments, and startups already trying things that point toward H3. Good strategy means improving H1, supporting H2 experiments, and investing in H3 vision all at the same time, not jumping straight from old to new.

Three Horizons

Three Horizons Analysis is a framework for mapping how a system moves from its current dominant form to a very different future form. It splits the forward view into three overlapping horizons: H1, today's dominant system and its near-term tune-ups; H2, the contested transitional space where disruptive innovations and alternative models are emerging; and H3, the long-term transformed future you want to bring about. The key insight is that real change is rarely a clean switch — it is an overlap in which the old system keeps producing value while the new system grows. So strategy must run on all three horizons at once: keep H1 healthy, nurture H2 pioneers, and explicitly invest in the H3 vision, including the values it embodies.

 

Three Horizons Analysis is a structured foresight framework for mapping system transitions by partitioning the forward view into three overlapping horizons. H1 is the current dominant system and its near-term improvement trajectory; H2 is the transitional zone of disruptive innovations and alternative approaches contesting the incumbent; H3 is the long-term transformative space of fundamentally different, fit-for-future systems. The framework attends explicitly to inter-horizon dynamics — H1 declines as its fit-for-context erodes, H3 grows as conditions favor it, and H2 is the contested arena where pioneers and entrepreneurs operate. Method: characterize H1 (strengths, stress signals); envision H3 (values, operating principles); identify H2 actors and pockets of innovation pointing toward H3; analyze the interactions; build a portfolio strategy across all three. Unlike linear long-range planning or pure scenario analysis, it foregrounds transition dynamics and an explicitly normative H3 (what should emerge, not just what will happen), connecting strategic analysis to vision and values.

Structural Signature

The operation presumes (a) a domain where a dominant current system is visible and alternative futures are being actively developed, (b) strategic actors with horizons long enough to see beyond H1 operations, and © organizational or societal capacity to maintain and invest across all three horizons simultaneously. A Three Horizons analysis has six structural components. The component decomposition separates domain-boundary specification (a gating step) from the three substantive horizon-characterization activities from transition-dynamics analysis and strategy development; these are methodologically distinct and benefit from explicit separation:

1. Domain-boundary specification — scope-setting only: naming what system is under analysis with enough precision that H1/H2/H3 can be meaningfully distinguished, and with enough breadth that genuine transition dynamics can surface. No horizon characterization is done at this step; the output is a bounded domain statement.
2. H1 characterization — describing the current dominant system: its operating logic, its institutional and technical arrangements, its strengths, its dysfunctions, and — critically — its stress signals (the specific phenomena that indicate declining fitness for emerging context).
3. H3 envisioning — articulating the aspirational transformed system: its operating principles, its values commitments, its structural features, distinct from mere speculation. This step is explicitly normative in the Sharpe-Hodgson lineage and more instrumentally descriptive in the McKinsey lineage; the choice of emphasis here is itself a methodological commitment.
4. H2 activity mapping — identifying the specific actors, organizations, technologies, practices, and pilots that are already operating in the transitional space. H2 activities are concrete and locatable, not speculative; the analytical work is to identify them and distinguish seeds-of-H3 from H1-extensions.
5. Transition-dynamics analysis — analyzing how H1 pressures and H3 aspirations shape H2 activity; which H2 elements are seeds of H3 versus which are H1-extensions that will not scale beyond the current paradigm; and how the three horizons interact over time.
6. Strategy development — producing commitments across all three horizons with appropriate resource allocation: maintain and improve H1 capacity; invest in selected H2 activities for H3-alignment; sustain H3 envisioning as ongoing work. This step converts analytical output into organizational commitments; without it, Three Horizons analysis risks remaining insight without strategic purchase.

Structural distinctions include: the time-scale of the analysis (2-3 horizons within a decade for fast-changing domains; horizons spanning decades for slower-changing domains); the normative stance (the Sharpe-Hodgson version explicitly incorporates values and aspirations at H3; the McKinsey three-horizons-of-growth version is more instrumentally-descriptive); and the depth of transition-dynamics analysis (casual versus rigorous). The distinguishing structural commitment is the three-horizon overlap structure: other frameworks that use horizons without the overlap or without the transition-dynamics framing are not Three Horizons in the technical sense.

What It Is Not

• Not linear extrapolation — linear extrapolation treats the future as continuous extension of the present; Three Horizons explicitly includes system-transition dynamics where the current system's logic is superseded.
• Not pure scenario planning — scenarios construct alternative integrated stories of possible futures; Three Horizons maps the transition from current to future systems. The methods are complementary and often paired: scenarios can be mapped onto Three Horizons (different scenarios may feature different H3 configurations and different H2 actor mixes), and Three Horizons analysis often feeds scenario construction by surfacing transition pathways.
• Not backcasting — backcasting starts from a specified desired future and works backward to identify the pathway; Three Horizons explicitly holds H1, H2, and H3 in simultaneous view and emphasizes the overlapping transition rather than a single backward-traced pathway. Backcasting is often used within the H3 envisioning and strategy-development steps of Three Horizons.
• Not the McKinsey Three Horizons of Growth model, though closely related — McKinsey's portfolio-management application (H1 as current core, H2 as emerging businesses, H3 as venture options)^[1] shares the three-layer structure but is instrumentally descriptive for corporate resource-allocation; Sharpe-Hodgson Three Horizons^[2] is normative and transition-oriented. The frameworks share lineage but have substantively different uses.
• Not a prediction tool — Three Horizons identifies possible transitions but does not predict their timing or exact content.
• Not a single-method answer — typically paired with scenario planning, backcasting, visioning, or other methods for comprehensive foresight work.
• Not appropriate for all domains — domains with stable institutional arrangements and modest emerging-alternative activity may not benefit from Three Horizons analysis.
• Not static — the Three Horizons framing is most useful when iteratively updated as the horizon of emerging activity evolves; single-snapshot applications tend to become stale.
• Not value-free — the H3 envisioning process explicitly incorporates values and aspirations, which means the framework's outputs reflect the values of the participants; this is a feature when used reflexively and a concern when used naively.
• Not uniformly applied at all scales — the framework works differently at organizational, industry, national, and global scales, with different appropriate horizon-widths and different dynamics.
• Not sufficient without action — Three Horizons analysis that produces a map without organizational commitment to multi-horizon investment tends to produce insight without impact.

Broad Use

Three Horizons Analysis has two major lineages. The first is the McKinsey Three Horizons of Growth framework articulated in Baghai, Coley, and White's The Alchemy of Growth (2000)^[1], used extensively in corporate strategy and portfolio management for resource-allocation across existing core businesses (H1), emerging businesses (H2), and venture options (H3). The second is the Sharpe-Hodgson Three Horizons framework developed by Bill Sharpe and Tony Hodgson in the International Futures Forum^[3] context during the 2000s, with Sharpe's Three Horizons: The Patterning of Hope (2013)^[2] as the foundational reference. The Sharpe-Hodgson version has been applied extensively in sustainability transitions, public-sector foresight, community-development work, and educational futures, with applications including urban sustainability planning in multiple cities, food-system transition analysis in the UK and EU, health-system transformation work in Scotland and other contexts, and climate-transition work in multiple jurisdictions. The International Futures Forum, the Iknowlab network, and Sharpe's own H3Uni organization have produced training, methodology, and applied-work publications that have disseminated the framework widely.

In corporate strategy, both lineages are actively used, often with interchangeable terminology even though the substantive models differ. Consulting firms (McKinsey, BCG, Deloitte, Accenture) regularly use Three Horizons framing in strategy work. In innovation management, the framework supports portfolio analysis across core, adjacent, and transformational innovation. In government-level strategic planning, Three Horizons has been applied in Scotland (notably in the Scottish Futures Forum work), Wales, New Zealand, and other contexts. In NGO and social-sector work, the framework has been applied to large-scale social-change work including poverty reduction, climate action, and equity-focused work. In educational-futures contexts, Three Horizons has been applied to curriculum development, institutional transformation, and education-system-level change. In technology-roadmapping contexts, the framework is used alongside technology-maturity analysis (e.g., Gartner Hype Cycle) for roadmap development. In sustainability-transitions research, the framework has engaged with multi-level perspective (MLP) transitions theory^[4] in academic work (though the two frameworks have some tension, which the contested_construct flag partially captures).

Clarity

Three Horizons clarifies the simultaneous-investment imperative across temporal layers. In the absence of explicit three-horizon framing, strategy discussions frequently collapse into single-horizon focus: H1 operational excellence dominates because it produces immediate results; H3 transformational aspiration produces inspiration but often without operational grounding; H2 — where transitions actually happen — is systematically underattended because it lacks both the immediate-results quality of H1 and the inspirational quality of H3. The framework's explicit three-horizon structure forces attention to H2 as a distinct strategic zone with its own investment logic. The clarity also extends to the recognition of stress signals: in the Sharpe-Hodgson framework, specific attention is given to "signals of the future present" — current phenomena that are early expressions of H3 — and to H1 stress indicators — current phenomena that indicate the declining fitness of the existing system. The framework provides language for distinguishing these categories of signals and for tracking them over time. Finally, the framework clarifies the role of visioning and values: H3 is explicitly a zone where values and aspirations shape analysis, which legitimates values-based analytical work that purely descriptive foresight methods often marginalize.

Manages Complexity

Three Horizons manages the complexity of long-range transition through the tri-layer structure and the explicit attention to transition dynamics. Each horizon has its own interpretive register: H1 emphasizes operational performance, incumbent-system dynamics, and near-term metrics; H2 emphasizes emerging-actor mapping, alternative-practice identification, and transition-experiment tracking; H3 emphasizes values, aspirations, and system-level design principles. The framework provides a vocabulary (H1, H2, H3) that enables cross-horizon discussion without conflation. The transition-dynamics analysis provides structure for understanding how the horizons interact: H1 pressure creates space for H2 activity; H2 innovations point toward H3 possibilities; H3 aspirations inform the selection of which H2 activities to invest in. The complexity-reduction cost is that three horizons can be too few to capture some dynamics (in rapid-change contexts, multiple overlapping cycles may need to be analyzed), and the binary distinction between "signals of the future present" and "H1-extensions" can be difficult to apply to ambiguous developments. Mature practice addresses these through iterative updates and through use of Three Horizons alongside complementary methods (scenarios, backcasting, systems mapping).

Abstract Reasoning

Three Horizons embodies a deep principle about system transition: systems change not by instantaneous replacement but by overlapping transition, in which the incumbent system continues to produce value and meaning while the emerging system develops viability; effective strategic engagement requires simultaneous attention to maintaining and improving the current while investing in and legitimizing the emerging. This connects to several analytical traditions. Kuhn's paradigm-shift analysis^[5] describes scientific revolutions as involving anomaly accumulation in the dominant paradigm (H1 stress), alternative-paradigm proposals in the transitional space (H2 activity), and eventual paradigm succession (H3 emergence) — though with a normative valence that Kuhn did not supply. The multi-level-perspective (MLP) transitions-theory literature (Geels 2002 and subsequent)^[4] describes similar dynamics in socio-technical-systems transitions, with niche-innovations (loosely corresponding to H2), regime-level incumbents (H1), and landscape-level pressures (broader context). The innovation-management "s-curve" and "technology-substitution" literature describes similar overlapping-transition dynamics. Christensen's disruptive-innovation theory^[6] describes H2-type activities in specific technology-market-dynamics terms. Cognitive and organizational-psychological work on ambidexterity (O'Reilly and Tushman 2004 and subsequent)^[7] describes the organizational challenge of simultaneously exploiting H1 while exploring H2/H3. The abstract-reasoning depth of Three Horizons (particularly in the Sharpe-Hodgson lineage^[2]) lies in its integration of these analytical traditions with a normative and practical orientation that supports strategic engagement rather than pure analysis; the McKinsey lineage^[1] draws on a narrower subset — primarily the s-curve, ambidexterity, and portfolio-management traditions — without the explicit normative and transition-dynamics emphases.

Knowledge Transfer

Corporate strategy (traditional) → H1: core business, mature products → H2: adjacent-market entry, next-gen products → H3: business-model innovation, venture options Energy transition → H1: fossil-fuel dominated grid → H2: renewables integration, grid flexibility → H3: decarbonized grid, distributed energy Transportation → H1: private-car dominant urban system → H2: shared mobility, micromobility, EVs → H3: multimodal low-carbon mobility system Healthcare → H1: volume/fee-for-service, episodic care → H2: value-based, population-health, telehealth → H3: integrated care, prevention-dominant Food system → H1: industrial-agricultural, long supply → H2: regenerative practices, local systems → H3: regenerative / distributed food systems Education → H1: industrial schooling model → H2: blended learning, competency-based → H3: learner-centered / lifelong education Urban development → H1: car-oriented sprawl → H2: transit-oriented, mixed-use infill → H3: walkable / 15-minute cities Financial system → H1: bank-intermediated, centralized → H2: fintech, open banking → H3: post-scarcity or alternative financial architectures Manufacturing → H1: centralized mass production → H2: agile / flexible / digitally-enabled → H3: distributed / circular manufacturing Democratic governance → H1: representative + electoral → H2: deliberative additions, digital engagement → H3: integrated deliberative-representative systems

The shared structure across these contexts is the three-horizon overlap with explicit transition dynamics; the distinctions lie in the domain-specific content and the time-scale appropriate to the substantive transition. Corporate-strategy applications typically operate on 3-10-year horizons because product-market-cycle dynamics compress the transition; energy-transition, food-system, and healthcare applications typically operate on 20-40-year horizons because institutional, infrastructural, and behavioral change at system scale unfolds over decades. Urban-development and democratic-governance applications sit at the longest horizons, often spanning generations, because the physical capital stock (buildings, streets) and the institutional-cultural capital (political traditions, civic habits) change particularly slowly. The time-scale is itself analytical output — matching horizon-width to the substantive rate of system change in the specific domain is a judgment that the analysis has to make explicitly rather than importing from a standard template.

Example

Formal / abstract — International Futures Forum Scotland Health-System Three Horizons Work (2012-2018)

The International Futures Forum (IFF)^[3], a Scotland-based futures-research organization founded in 2001, conducted extended Three Horizons work on the Scottish health-system transformation agenda during 2012-2018, in partnership with NHS Scotland, the Health Foundation, and various Scottish civic and academic partners. The work is documented in IFF publications, in Sharpe's Three Horizons book^[2], and in peer-reviewed health-futures literature (including papers in the Journal of Futures Studies).

The domain scope: the health-system in Scotland faces structural pressures familiar across high-income health systems (ageing population with rising chronic-disease burden; workforce constraints particularly in primary care and certain specialties; cost pressures from pharmaceutical innovation and technology; health inequalities requiring population-health approaches; quality and safety improvement imperatives). The question was how to think about the long-term trajectory of the system beyond incremental improvement of the current model.

H1 characterization: the current dominant system is a universal-access NHS funded from general taxation, organized around hospital-centered acute care and general-practitioner primary care, operating with familiar institutions, professional structures, payment flows, and management practices. Stress signals identified include: workforce-supply gaps (particularly in primary care); structural mismatch with chronic-disease burden (acute-episode-centered design vs long-term-condition realities); health-inequalities persistence despite decades of focused effort; financial pressure exceeding incremental-improvement capacity; and cultural/workforce issues including burnout and retention.

H3 envisioning: the IFF-facilitated H3 work with diverse stakeholder groups (including patients, carers, community members, clinicians, managers, and policy actors) envisioned a transformed system emphasizing: prevention-and-wellbeing orientation rather than disease-treatment orientation; community-and-place-based organization rather than primarily institution-based; assets-based approaches that engage community strengths rather than deficit-based approaches; integration of health, social-care, and broader community support rather than fragmented service silos; and democratic engagement of patients, families, and communities as co-producers of health rather than recipients of services. This H3 vision was explicitly normative — it reflected values as well as analytical projection.

H2 activity mapping: the work identified specific existing Scottish initiatives as H2 activities pointing toward H3: Realistic Medicine (the Chief Medical Officer's initiative challenging disease-focused and over-medicalized approaches); House of Care (a primary-care model emphasizing collaborative care planning with patients with long-term conditions); Buurtzorg-inspired neighborhood nursing pilots; various community-health initiatives; integration of health and social care under the Integration Joint Boards legislation; asset-based community-development work; and participatory-budgeting and community-engagement experiments in specific regions. The analysis placed these initiatives as H2 activities with specific relationships to H3 aspirations and to H1 constraints.

Transition-dynamics analysis examined: how H1 financial and operational pressures create space for H2 innovations (scarcity forces reconsideration of how value is created); how H2 innovations face H1 resistance (professional roles, institutional structures, measurement systems, funding flows are all H1-configured); how H3 envisioning provides normative orientation for H2 investment selection (which H2 activities are seeds of H3 vs which are H1-extensions); and how H1 could be actively managed to create more space for H2 and H3 (policy-and-regulatory enabling of H2 activities, reduction of unnecessary H1 activity, transparency about H1 dysfunctions).

Strategy development produced commitments across horizons: maintain and improve H1 capacity (workforce, quality, operational performance); invest in H2 activities selected for H3-alignment; create policy-and-regulatory enabling conditions for H2 scaling; and maintain H3 envisioning as ongoing work that adapts as understanding deepens. The work was embedded in Scottish health-policy processes over multiple years and contributed to several specific policy commitments including continued integration-joint-board development, continued Realistic Medicine implementation, and various community-health investments.

Mapped back to the six-component structural signature: the domain boundary was specified as the Scottish health-system on a multi-decade horizon (component 1); H1 was characterized with stress-signal emphasis on workforce, chronic-disease mismatch, and inequalities (component 2); H3 was envisioned with explicit normative content including prevention, community-place-based organization, assets-based approaches, and integrated health-social-community support (component 3); H2 activities were concretely mapped to named Scottish initiatives (Realistic Medicine, House of Care, Buurtzorg-inspired nursing, Integration Joint Boards) with analytical placement distinguishing seeds-of-H3 from H1-extensions (component 4); transition-dynamics analysis examined how H1 pressures, H2 innovations, and H3 aspirations interact (component 5); and strategy development produced multi-year commitments across horizons embedded in Scottish health-policy processes (component 6). The example illustrates canonical Sharpe-Hodgson application: rigorous multi-horizon analysis with stakeholder participation, explicit normative engagement at H3, concrete H2 activity identification, transition-dynamics analysis, and integration with ongoing policy and strategic work.

Applied / industry — Regional Credit Union 2023 Member-Experience Three Horizons Roadmap

(Illustrative example; figures indicative rather than drawn from published data.)

A regional credit union serving approximately 480,000 members with $6.8B in assets across a multi-county area undertook a Three Horizons exercise in 2023 to develop a 10-year member-experience roadmap. The credit union's strategy team, led by the Chief Member Experience Officer, had been struggling with a persistent challenge: the organization's investment pipeline was dominated by H1 operational improvements (digital-banking-platform enhancements, branch-network optimization, contact-center modernization) with limited investment in emergent member-experience patterns, and when H3 aspirations were articulated (e.g., "we will be the financial partner embedded in our members' life goals"), they tended to remain disconnected from the operational investment pipeline.

The exercise, facilitated by an external foresight consultant with both McKinsey-style and Sharpe-Hodgson-style Three Horizons experience, ran over approximately 10 weeks with a cross-functional working group (strategy, member experience, digital, operations, marketing, risk, community engagement) plus member-input through focus groups, surveys, and community-advisory-board engagement.

H1 characterization: current member-experience is built on digital-banking-platform plus branch-network plus contact-center plus relationship-manager-for-high-value-members, with member-experience metrics (NPS, satisfaction, retention) at industry-respectable levels. Stress signals: declining branch utilization driving cost-per-transaction concerns; rising member expectations for financial-advisory services beyond traditional product set; demographic shifts in member base (younger members, more diverse members, members with different life-goal patterns); competitive pressure from national direct-to-consumer financial providers and fintech competitors; and internal complexity from the accumulation of product features and channels.

H3 envisioning: the working group with member input developed an H3 vision of the credit union as an "embedded financial partner" in members' life journeys, with several key characteristics: proactive anticipation of member financial moments rather than reactive service; cross-domain integration of banking, insurance, investment, advisory, community-resource, and life-goal services; member-and-community-centered design of services rather than product-centered design; distinctive community-anchor-institution role differentiating from commodity-financial-services competitors; and explicit orientation to member-and-community wellbeing, not merely transactional service. This vision was explicitly normative and reflected the cooperative-values heritage of the credit-union movement.

H2 activity mapping identified specific existing initiatives and opportunities as H2 activities: financial-wellness programming (pilot stage, with evidence of member value); life-moment financial coaching (small pilot with first-time homebuyers, with expansion potential); community-partnership integrations (with housing counselors, small-business development centers, nonprofit financial-education organizations); embedded-finance experiments (with employer-partners for financial-wellness benefits); data-driven proactive outreach (technology in place but underutilized for life-moment anticipation); and relationship-manager model extensions to broader member segments (historically restricted to high-asset members).

Transition-dynamics analysis: the working group identified how H1 operational-investment pipeline was systematically crowding out H2 investment (any investment had to justify itself against H1-framed ROI metrics that H2 activities could not satisfy); how H3 articulation was being disconnected from operational decisions (strategy documents mentioned the embedded-partner vision but operational commitments were H1-shaped); how H2 activities were being constrained by H1-era metrics (e.g., financial-wellness programming was measured by product-sale outcomes rather than member-wellbeing outcomes, constraining its design and scale); and how certain H2 activities (particularly community partnerships) could be scaled without substantial capital investment but required leadership attention and explicit strategic prioritization.

Strategy development produced commitments across horizons: continued H1 operational investment was maintained but with reduced growth rate (from approximately 85% of discretionary budget to approximately 65%); H2 investment was increased from approximately 10% to approximately 25% with specific program commitments (expansion of financial-wellness programming, new life-moment coaching programs for first-time homebuyers and near-retirees, community-partnership expansion, embedded-finance pilot with two employer partners); H3 work was sustained as ongoing strategy activity with quarterly reviews; and member-experience metrics were updated to include H2/H3-relevant measures (member-wellbeing indicators, community-impact indicators) alongside traditional H1 metrics.

The exercise informed specific capital and operational commitments amounting to approximately $18M over the 3-year plan window, with identified longer-term investment commitments of an additional $30-40M over the 5-10-year window. The CEO reported to the board that the Three Horizons framing had produced clearer strategic coherence across the investment portfolio than prior strategy exercises, and the framework was adopted as an ongoing strategic-planning discipline.

Mapped back to the six-component structural signature: the domain boundary was specified as the credit union's member-experience on a 10-year horizon (component 1); H1 was characterized with stress-signal emphasis on branch-utilization, rising expectations, demographic shifts, and competitive pressure (component 2); H3 was envisioned as the "embedded financial partner" with explicit cooperative-values grounding (component 3); H2 activities were concretely mapped to financial-wellness programming, life-moment coaching, community partnerships, embedded-finance experiments, and data-driven outreach (component 4); transition-dynamics analysis identified how H1 metrics were crowding out H2 investment and how H3 articulation was disconnected from operational decisions (component 5); and strategy development produced explicit budget-share shifts and multi-year investment commitments with updated metric architecture (component 6). The example illustrates Three Horizons at the institutional scale: the principles scale down from health-system-level applications while retaining analytical value, provided the transition-dynamics analysis is genuinely conducted rather than reduced to a three-bucket portfolio labeling exercise. Notably, this case also illustrates the integration of both lineages: the 85%/10%/5% → 65%/25%/10% budget-share shift is recognizable as McKinsey-lineage portfolio-management logic^[1] (explicit discretionary-budget reallocation across H1/H2/H3 as a resource-allocation decision), while the cooperative-values grounding of H3, the normative member-and-community-wellbeing metrics added to the measurement architecture, and the explicit attention to how H1-configured metrics were crowding out H2 activity are recognizable as Sharpe-Hodgson-lineage contributions^[2] (normative H3 engagement and transition-dynamics analysis of how incumbent-system measurement forecloses emergent-system development). The two lineages are complementary in practice rather than mutually exclusive, and mature applications often draw on both.

(Illustrative example; figures indicative rather than drawn from published data.)

Structural Tensions and Failure Modes

• T1: H1 Operational Pull vs H2/H3 Investment.
• Structural tension: H1 produces the cash, the measured performance, and the immediate credit that funds the enterprise; H2 and H3 produce neither reliably in the short term. The same quarterly performance system that funds the exercise also creates structural pressure to reallocate from H2/H3 back to H1 whenever short-term results wobble. The framework's prescription of simultaneous multi-horizon investment is a running argument against the organization's own metrics.
• Common failure mode: A credit union, hospital system, or corporate team produces a Three Horizons roadmap with explicit H2/H3 budget commitments, then experiences an H1 performance dip two quarters later and quietly moves the H2/H3 budget back into H1 "as a temporary measure." The reallocation is never formally reversed; eighteen months later the Three Horizons exercise exists as a slide deck and the investment portfolio looks exactly like the pre-exercise H1 dominance.
• T2: Normative H3 vs Descriptive Forecast.
• Structural tension: The Sharpe-Hodgson version of the framework explicitly makes H3 a normative envisioning — what should emerge, according to what values — while retaining the language of a "horizon" that sounds descriptive. This dual character is a feature when used reflexively and a problem when the normative layer is not named: participants read H3 as prediction and infer strategic commitments as responses to an anticipated future rather than as choices in service of a contested value position.
• Common failure mode: A Three Horizons workshop produces an H3 vision that reflects the values of the participants in the room. Leadership endorses the H3 as "where the industry is going" and commits investment on predictive grounds. Stakeholders with different values (board factions, regulators, customers, other geographies) do not share the implied future; the investment is contested not on strategy merits but on the undeclared normative content; and the organization has neither a clean predictive argument nor a clean values argument to defend it.
• T3: Three-Horizon Structure vs Multi-Cycle Reality.
• Structural tension: The framework imposes a single three-horizon structure on the strategic environment, but in fast-changing or multi-axis domains there are often multiple overlapping transitions at different timescales along different dimensions. Forcing all of them into a single H1/H2/H3 layout mixes together phenomena that have different dynamics and produces a composite picture that is coarser than the underlying reality.
• Common failure mode: A technology firm draws a single three-horizon map that combines a fast cycle (product architecture, 2-3 year) with a medium cycle (business model, 5-7 year) and a slow cycle (industry structure, 10-15 year). H2 ends up containing items at radically different maturity levels and transition speeds; the investment-allocation logic that works for one cycle is misapplied to the others; specific H2 bets fail not because they were wrong but because they were funded on the wrong clock.
• T4: H2 Identification vs H1-Extension Confusion.
• Structural tension: The framework requires distinguishing H2 activities that are seeds of H3 from H2-looking activities that are actually H1 extensions dressed in innovation language. The distinction is often the single most important analytical judgment in the exercise, and it is genuinely hard: many "transformation" initiatives are disguised operational improvements, and many genuinely H3-pointing activities look like marginal tinkering to H1-trained observers.
• Common failure mode: An organization classifies every active experiment and digital-transformation program as H2, producing an H2 column full of activities that in fact extend H1 with new tools. The framework's analytical value — separating incremental from transformational — is lost; the investment allocation against "H2" continues to serve H1 dynamics; retrospective review finds that the organization never actually funded a genuine H2/H3 transition despite the three-horizon language.
• T5: McKinsey Lineage vs Sharpe-Hodgson Lineage.
• Structural tension: The two lineages share a three-layer structure but answer different questions. McKinsey's framework is about corporate portfolio allocation across business maturity; Sharpe-Hodgson is about values-driven societal transition. Projects frequently use the label "Three Horizons" without specifying which lineage they are applying, and participants arrive with different mental models of what the exercise is for.
• Common failure mode: A strategy exercise billed as "Three Horizons" is conducted with a mix of participants — some expecting portfolio-management analytics with ROI logic at each horizon, others expecting normative transition work with values and communities at H3 — and the output satisfies neither. The portfolio-management camp finds the H3 work fluffy; the transition-work camp finds the H1 ROI discipline suffocating. The exercise produces a document that reads like two different frameworks spliced together, and the organization reverts to whichever lineage its existing strategy process already used.
• T6: Framework Snapshot vs Living Strategic Discipline.
• Structural tension: Three Horizons is most valuable when the H2 landscape and H3 envisioning are updated iteratively as the environment and understanding evolve. One-time exercises produce a snapshot that becomes stale within 18-36 months; sustaining the framework as an ongoing discipline requires dedicated attention and re-visioning that organizations rarely budget for explicitly.
• Common failure mode: An H2 activity that was correctly identified in the initial exercise matures faster than expected; it should be reclassified as transitioning from H2 toward H1 (or recognized as a seed of a more radical H3 than originally articulated). The framework is not revisited; the stale classification persists; investment logic from year one is applied to a situation year three has transformed. The same pattern happens in the opposite direction when H3 envisioning lags evolving context, producing strategic maps that look authoritative and are substantively outdated.

Scaling: Product Roadmap Application

The Three Horizons framework translates directly to product-portfolio strategy through what McKinsey-tradition practitioners call the "run-the-business / change-the-business / disrupt-the-business" articulation, the canonical formulation Baghai, Coley, and White (1999) develop in The Alchemy of Growth. ^[1] In a software product context, H1 includes the current product platform, its core customer base, the revenue engine it represents, and the near-term feature roadmap that improves competitive position against direct competitors. H1 products are typically measured on quarterly release cycles, customer-acquisition cost, retention metrics, and NPS (Net Promoter Score). The H1 strategic question is: how do we maintain and extend the dominance of this platform as long as possible while returning cash to fund exploration?

H2 in product strategy includes adjacent-market products, platform extensions, and technology-maturity advances that position the company for the next product generation, riding what Foster (1986) characterized as the S-curve transition between an incumbent technology approaching its limits and an emerging successor still climbing. ^[8] Examples include: a traditional on-premises software company building cloud-native extensions alongside the legacy product; a mobile-first company experimenting with wearables; a web-application platform adding AI-powered features as H2 positioning. H2 products typically have smaller customer bases, longer sales cycles, and lower immediate revenue, but they often have higher gross margins and stronger competitive differentiation potential. The H2 strategic question is: which adjacent or transitional technologies position us for H3 viability?

H3 in product strategy is the transformative-platform question: what entirely new capability, market, or user need becomes addressable if the underlying technology shift completes — the move that Christensen (1997) shows is decisive when disruptive entrants redefine the basis of competition rather than improve along incumbent dimensions? ^[6] Examples: a traditional relational-database company recognizing that graph-database and vector-database paradigms enable fundamentally different use cases; a file-sharing company recognizing that AI-native collaboration transforms the design of information work; a project-management company recognizing that AI agents change what "management" means. H3 is where the framework becomes explicitly normative: what should the company become in a world where the current platform's assumptions no longer hold? The H3 strategic question is not "what will the technology enable?" but "what do we want to build once the current system's constraints dissolve?"

The allocation tension at portfolio level is severe — a generalized form of the exploration-exploitation dilemma March (1991) formalized, in which the predictable returns of refining current capabilities crowd out the riskier, slower-paying investment in new ones. ^[9] A mature software company with strong H1 products experiences intense quarterly pressure to reinvest H1 revenue into H1 features: the sales team demands features that close deals; the customer-success team demands features that prevent churn; the competitive threat in H1 space demands responses. Every dollar allocated to H2 exploration is a dollar not invested in H1 defense. Yet without H2 investment, the company becomes vulnerable to H2-native competitors that treat the problem space differently. And without H3 exploration, the company becomes obsolete when the technology or market shifts that H3 anticipates actually occur.

Product-roadmap Three Horizons discipline forces explicit choice on these allocation questions, in line with Govindarajan and Trimble's (2010) argument that breakthrough innovation requires a dedicated organizational and budgetary track separated from the performance engine of the core business. ^[10] Organizations that apply Three Horizons rigorously to product strategy typically target allocations like: H1 (65-75% of product development resources), H2 (15-20%), H3 (5-15%), adjusted by industry maturity and competitive intensity. This is recognizably the same discipline as the credit-union example above, applied at product level rather than member-experience level. The discipline requires that H2 investments are tracked against H3 alignment (not just commercial viability) and that H3 exploration maintains ongoing visioning activity (not quarterly deliverables).

Scaling: Software Architecture Evolution

The Three Horizons framework also applies to software-architecture evolution — the long-term trajectory of system design choices that enable (or constrain) organizational capability — extending the original Sharpe-Hodgson (1999) "towards a new reality" formulation from social-systems foresight into technical-system trajectory analysis. ^[11] Architecture decisions made 5-10 years ago become infrastructure constraints that enable or prevent current work; architecture decisions made today shape what will be possible in 5-10 years. Three Horizons provides language for managing this temporal layering.

H1 architecture includes the systems currently in production, the technology stack that powers the revenue, and the institutional knowledge embedded in that stack — the "managerial" horizon Sharpe (2013) describes as fit for the current operating context yet increasingly stressed as that context drifts. ^[12] In a modernizing enterprise, H1 might include: monolithic applications built in older languages (COBOL, older Java versions) that are operationally stable but architecturally inflexible; legacy databases with high operational cost; familiar deployment infrastructure; and the accumulated customizations and integrations that make the system work in organizational context. The H1 stress signals in architecture include: difficulty deploying changes (long release cycles); difficulty scaling specific components; difficulty integrating new platforms (APIs that are hard to extend, data models that don't compose); workforce difficulty finding engineers who want to work on the legacy stack; and increasing operational cost for declining business value.

H2 architecture includes the transitional systems being built or deployed: the cloud-native microservices running alongside the legacy monolith; the data-lake infrastructure being stood up to enable analytics that the legacy warehouse cannot; the API-driven integrations that enable external partners; the AI-inference infrastructure being built for new product capabilities — what Geels (2002) describes in the multi-level perspective as niche-level innovations being incubated alongside the regime, gradually accumulating the technical and institutional support needed to displace incumbent configurations. ^[4] H2 architectural choices are typically made with an eye toward H3 possibilities: containerization and orchestration infrastructure (Kubernetes, etc.) are chosen because they enable the scaling and independence that H3 scenarios may require; event-driven architecture is chosen because it enables the loose coupling that complex adaptive systems may need; multi-cloud or hybrid-cloud approaches are chosen because they preserve options for H3 scenarios that might rely on specialized infrastructure. The H2 architectural question is: which choices position us for H3 viability while supporting current operations?

H3 architecture is the aspirational question: what architecture do we need if our fundamental assumptions about scale, distribution, real-time requirements, intelligence embedding, or user interaction change — the explicitly visionary horizon Curry and Hodgson (2008) characterize as "seeing in multiple horizons," requiring practitioners to hold the dominant present, the contested transition, and an aspirational future system in simultaneous view? ^[13] Examples: if we assume that large language models become embedded in every user interaction (H3 vision), what architecture supports that? (Likely: inference optimization, prompt-management infrastructure, knowledge-retrieval at scale, human-in-the-loop validation, user-data privacy controls.) If we assume that supply-chain visibility and responsiveness become competitive necessities (H3 vision), what architecture supports that? (Likely: real-time data integration from many sources, event-driven workflow coordination, semantic data modeling.) If we assume that regulatory requirements around data localization, algorithmic explainability, and AI governance become mandatory (H3 vision), what architecture supports that? (Likely: data governance infrastructure, audit trails, interpretability tooling, policy-as-code.) The H3 architectural question is explicitly normative and futures-oriented: given these aspirations, what architectural principles should we establish now?

The architectural transition challenge is that H1 and H3 often have tension in their design principles — the same incumbent-versus-emerging dilemma Loorbach (2010) treats in transition management, where regime structures optimized for stability actively impede the experimentation needed to develop their successor. ^[14] H1 architecture optimizes for efficiency in a bounded, known domain: tight coupling between components to reduce latency; monolithic deployment to simplify operational consistency; strong schema enforcement to catch errors early; centralized orchestration to maintain control. H3 architecture (in many scenarios) optimizes for flexibility and emergence in an unbounded, evolving domain: loose coupling to enable independent evolution; distributed deployment to enable autonomy; flexible schema to enable adaptive data models; decentralized coordination to enable responsiveness. The transition (H2) requires building new architectural capabilities without losing H1 reliability and performance. Organizations that do this well treat H2 architecture as a managed dual-run: new systems are built in H3-oriented patterns while H1 systems continue to operate; integration points between H1 and H2 are carefully managed; data models are bridged; operational insights from H1 are applied to H2. The architectural transition question is: what dual-stack capabilities do we need to maintain H1 performance while building H3 capability?

Scaling: Organizational Transformation

Three Horizons also provides a framework for thinking about organizational transformation — the large-scale change in how an organization operates, governs, makes decisions, and relates to its environment — the kind of values-grounded, system-level transition Sharma (2007) develops as "radical transformational leadership," in which the work is as much about reorienting purpose and identity as about restructuring operations. ^[15] Transformation initiatives frequently fail because they attempt to move from H1 to H3 without adequately funding and managing the H2 transition space. Three Horizons discipline provides language for managing this complexity.

H1 organization includes the current structure, governance model, decision-making processes, cultural norms, and role definitions — the patterned assumptions and behaviors Schein (1985) identifies as organizational culture, simultaneously the source of operational coherence and the most resistant constraint on change. ^[16] In a traditional hierarchical organization, H1 includes: formal reporting relationships and span-of-control principles; annual planning cycles with fixed budgets; role-based job descriptions and career ladders; decision authority concentrated at senior levels; functional silos with matrix coordination; performance management based on individual metrics; and cultural norms emphasizing execution of known plans. The H1 stress signals in organizational context include: slow decision-making in a fast-moving market; siloed thinking preventing integration across business units; difficulty retaining innovation-oriented talent who experience the structure as constraining; difficulty responding to emerging opportunities because the planning cycle is inflexible; and workforce disengagement when the rate of external change exceeds the organization's capacity to adapt.

H2 organizational activity includes the transitional experiments already underway: cross-functional teams with decision authority; agile delivery practices in some units; rapid-experimentation frameworks (OKRs, sprint-based planning); communities of practice that cut across formal structure; employee-engagement initiatives that distribute decision-making; product-thinking approaches that challenge functional silos — exactly the kind of "image-of-the-future" probes that Bell (1997) places at the methodological core of futures studies, where alternative arrangements are tested in the present as a way of learning what the emerging system might require. ^[17] H2 is where the organization experiments with what "operating differently" means: Does it mean flatter reporting relationships? Does it mean decision-making at the team level rather than through executive consensus? Does it mean fluid team composition rather than static roles? Does it mean learning-based evaluation (what did we learn from this experiment?) rather than outcome-based evaluation (did we hit our targets)? The H2 organizational question is: which capability transitions position us for H3 viability?

H3 organizational vision includes the aspirational future state: What organizational design do we need to operate in a more uncertain, faster-moving, more complex environment — and, in the futures-literacy framing Miller (2018) develops, what assumptions about the future are we using right now to shape that design, and what alternative assumptions would surface a different organization? ^[18] Examples: a knowledge-work organization that aspires to enable every team to make decisions within a clear strategy frame rather than seeking approval up the hierarchy (H3 vision of distributed decision-making); a manufacturing organization that aspires to continuous adaptation rather than annual planning cycles (H3 vision of real-time planning); a financial-services organization that aspires to embedded AI augmentation of human judgment rather than AI replacement (H3 vision of human-AI partnership); a civic organization that aspires to active community co-governance rather than service delivery to passive recipients (H3 vision of stakeholder participation). The H3 organizational question is explicitly normative: given our values and aspirations, how should we organize?

The organizational transformation tension is that H1 and H3 operate on fundamentally different logics of control, authority, and decision-making — a dual-mode demand the International Futures Forum (2017) operationalizes in its Three Horizons Kit, which gives facilitators explicit moves for holding managerial-system rigor and visionary-system experimentation in the same conversation. ^[19] H1 logic emphasizes coordination through hierarchy, planning through centralized strategy, control through role definition and measurement, and alignment through cascaded goals. H3 logic (in many scenarios) emphasizes coordination through shared context and trust, planning through emergent strategy, control through principle and autonomy, and alignment through shared vision and values. The H2 organizational question is: what dual-operating-model capabilities do we need to maintain H1 stability and performance while building H3 adaptability and responsiveness?

Structural Tensions and Failure Modes — Extended Application

The six core tensions identified above scale into applied domains with context-specific articulations:

T1: H1 Operational Pull vs H2/H3 Investment.

The same dynamics that constrain health-system innovation and credit-union strategy transformation apply to product roadmaps, software architecture, and organizational design. In product roadmaps, the quarterly revenue pressure from H1 products constrains investment in H2 innovation even when market analysis shows H2 positioning is urgent. In software architecture, the operational excellence and cost-efficiency of H1 systems make the "dual-run" cost of H2 architecture transition visible and contested, while the long-term capability advantage of H3-oriented architecture remains abstract. In organizational transformation, the performance stability of H1 organizational design makes change feel risky, while the agility and resilience benefits of H3 design are difficult to measure in the short term. The framework's prescription remains the same across domains: explicit multi-horizon investment discipline with budget commitment that survives H1 performance wobbles.

T2: Normative H3 vs Descriptive Forecast.

In product strategy, the tension appears as: is H3 "what the market will demand" (descriptive) or "what we aspire to build in a transformed market" (normative)? Different products companies choose differently — some position H3 as predictive market positioning, others as values-based innovation direction — and the choice shapes investment decisions. In software architecture, the tension appears as: is H3 "the architecture we will need" (descriptive) or "the architectural principles we choose to adopt" (normative)? In organizational transformation, the tension appears as: is H3 "what organizations must become to survive" (descriptive) or "what kind of organization we choose to be" (normative)? Mature practice treats H3 as explicitly normative while grounding it in credible transition dynamics, which requires naming the values and aspirations that shape H3 vision.

T3: Three-Horizon Structure vs Multi-Cycle Reality.

In product strategy, a company might be operating a traditional-product H1/H2/H3 cycle (3-10 years) while simultaneously operating a platform-feature cycle (quarterly) and a technology-infrastructure cycle (5-10 years). Forcing all into one three-horizon map produces confusion about investment allocation and time horizons. In software architecture, multiple cycles are simultaneously present: application architecture (3-5 year cycle), platform architecture (5-10 year cycle), infrastructure architecture (10-15 year cycle). In organizational transformation, the same pattern holds: operational rhythms (quarterly), strategic cycles (1-3 years), capability building (3-5 years), cultural transformation (5-10 years). The framework's limitation is that one three-horizon model cannot adequately represent this complexity; mature practice uses multiple, nested Three Horizons models at different scales or explicitly manages multiple cycles with clear integration points.

T4: H2 Identification vs H1-Extension Confusion.

In product strategy, the distinction between "genuine H2 adjacent-market product" and "H1 product-line extension with new branding" is often the most important analytical judgment. Many organizations classify any new feature as innovation and lose the framework's ability to distinguish incremental from transformational. In software architecture, the distinction between "H2 new-capability infrastructure" and "H1 legacy-system modernization" requires clarity about whether the new system enables genuinely different organizational capability or merely updates the delivery technology. In organizational transformation, the distinction between "H2 experimental new capability" and "H1 operational improvement with innovation language" determines whether the transformation discipline is genuine or performative. The common failure is to classify everything as H2 and lose analytical specificity.

T5: McKinsey Lineage vs Sharpe-Hodgson Lineage.

In product strategy, organizations that blend McKinsey's portfolio-management rigor with Sharpe-Hodgson's normative-visioning approach produce the strongest strategies, but this requires explicit attention to which questions are being answered. In software architecture, the same dual-lineage approach applies: McKinsey's lens enables disciplined portfolio thinking about architectural investment; Sharpe-Hodgson's lens grounds architectural choices in principles and values. In organizational transformation, the integration is essential: McKinsey thinking enables resource-allocation discipline; Sharpe-Hodgson thinking ensures that the transformation serves an explicit vision of what the organization should become rather than merely optimizing for operational metrics.

T6: Framework Snapshot vs Living Strategic Discipline.

In product strategy, the initial Three Horizons roadmap becomes stale as H2 products mature faster or slower than anticipated, as competitive dynamics shift, as technology-maturity timelines change. The most strategically effective companies revisit their Three Horizons model quarterly, updating H2 and H3 positioning as the landscape evolves. In software architecture, the same requirement holds: architectural decisions made for H2 transition need to be revisited as H3 becomes clearer or as technology shifts create new possibilities. In organizational transformation, the same pattern holds: organizational design choices made for H2 transition may need adjustment as the organization's capability and context evolve. The framework's value depends on treating it as a living discipline rather than a one-time plan.

Structural–Framed Character

Three Horizons Analysis is a hybrid on the structural–framed spectrum. Part of it is a bare pattern — partitioning the forward view into an incumbent system, a contested transitional space, and an emergent transformative one, three overlapping curves whose dominance trades off over time. Part of it is a frame inherited from futurism and strategic foresight, which supplies the practitioner's method and its assumptions about how change should be mapped.

The structural skeleton of three overlapping S-curves — a declining present, a turbulent middle, an emerging future — can be recognized in many domains of transition, from technology adoption to industry disruption to ecological regime shift. But the prime travels as a deliberate method, not just a shape. It presupposes strategic actors with long enough horizons, an organizational appetite for transformation, and a goal of steering toward a preferred future — a whole foresight perspective with its own vocabulary of horizons and transitions. That gives it substantial normative weight, since the framework is meant to guide intervention rather than merely describe. Because a domain-independent transition pattern underlies a substantial foresight frame, it lands in the framed-leaning middle of the spectrum.

Substrate Independence

Three Horizons Analysis is a narrowly substrate-independent prime — composite 2 / 5 on the substrate-independence scale. It is a strategic-foresight methodology from Curry and Hodgson for mapping current systems, transitional innovation, and long-term transformation, built specifically for organizational scenario planning and futures thinking. Its underlying present-to-emergent-to-transformative logic has conceptual cousins elsewhere, but the prime stays operationally and terminologically bound to strategic and organizational contexts. Pushing it into non-strategic domains would feel forced, leaving it tethered to the planning practice it was designed for.

• Composite substrate independence — 2 / 5
• Domain breadth — 2 / 5
• Structural abstraction — 2 / 5
• Transfer evidence — 2 / 5

Relationships to Other Primes

Parents (2) — more general patterns this builds on

• Three Horizons Analysis is a kind of Foresight

  Three Horizons Analysis is a specialization of foresight whose distinctive move is partitioning the forward-view into three overlapping horizons — the declining current system, the contested transitional space, and the emergent transformative system — and tracking their dynamics over time. It inherits foresight's commitment to structured anticipation of plural futures informing present action, and adds the specific tri-layer temporal architecture that makes the contest between incumbent and emergent systems visible, supplying a particular mapping component of the broader foresight methods stack.

• Three Horizons Analysis is a decomposition of Modal Reasoning

  Modal reasoning evaluates claims across a structured space of alternative possibilities rather than the single actual situation, quantifying over accessible alternatives via modal operators. Three horizons analysis is the specific shape this reasoning takes in foresight: it partitions the space of possible futures into H1 (current system with near-term improvement), H2 (transitional disruption), and H3 (long-term transformation), and reasons about dynamics across this tri-layer partition. It is a structurally-particularized instance of possible-worlds reasoning whose alternatives are organized by temporal horizon and incumbent-emergent dynamics.

Path to root: Three Horizons Analysis → Foresight

Neighborhood in Abstraction Space

Three Horizons Analysis sits among the more crowded primes in the catalog (34^th percentile for distinctiveness): several abstractions describe nearly the same structure, so a description that fits it will tend to fit its neighbors too — transporting it usually means disambiguating within this family rather than landing on it exactly.

Family — Strategic Foresight & Scanning (15 primes)

Nearest neighbors

• Future Wheel — 0.82
• Reversibility Horizon — 0.82
• Top-Down Perspectives — 0.81
• Boundary Critique — 0.79
• Critical Juncture — 0.79

Computed from structural-signature embeddings · 2026-05-29

Not to Be Confused With

Three Horizons Analysis must be distinguished from Horizon Scanning, its nearest neighbor (similarity 0.69), despite their complementary roles in strategic foresight. Horizon scanning is the systematic, continuous search for weak signals—early indicators of emerging trends, risks, opportunities, or disruptions that are not yet dominant but are becoming visible at the periphery of the current system. Horizon scanning asks: "What signals are emerging? What is changing at the edges?" It is a signal-detection and anomaly-identification discipline. Three Horizons Analysis, by contrast, takes a domain (or set of potential signals) and maps the transition structure: current dominant system (H1), transitional innovations and actors (H2), and emergent transformed system (H3). Horizon scanning provides input into Three Horizons work—the weak signals detected through scanning often populate the H2 mapping and inform the H3 envisioning—but they are methodologically distinct. You can conduct horizon scanning without Three Horizons framing (simply cataloging signals without organizing them into a transition narrative); you can conduct Three Horizons without horizon scanning (charting a transition based on interviews and theory without systematic signal detection). More importantly, horizon scanning is often probabilistic and predictive—what is likely to emerge? Three Horizons is often normative and deliberately strategic—what should we invest in to influence which H3 emerges? The distinction clarifies that horizon scanning and Three Horizons serve different strategic purposes and work at different speeds: scanning is ongoing continuous work; Three Horizons is a periodic strategic-mapping discipline that operates on the signals scanning has surfaced.

Three Horizons Analysis is also distinct from Backcasting, though the two methods often work together. Backcasting is a futures methodology that starts from a specified desired future state and works backward to identify the pathway from present to that future. You envision a desired H3, then ask: "If we want to arrive at this future, what must happen in the decade before? In the five years before that?" Backcasting produces a linear, backward-traced pathway. Three Horizons, by contrast, holds H1, H2, and H3 in simultaneous view and emphasizes the overlapping, messy transition dynamics—the competition between alternatives, the resistance from H1, the emergence of multiple possible H2 pathways, and the genuine uncertainty about which H3 becomes viable. Backcasting is typically used within Three Horizons analysis to develop a specific transition pathway once H3 is clarified; Three Horizons thinking broadens backcasting by acknowledging that multiple backward-traceable pathways exist and that H2 dynamics are contested, not predetermined. The relationship is complementary: backcasting at high quality requires the kind of system understanding (what is H1, what are the stresses, what are the alternatives) that Three Horizons provides; Three Horizons benefits from the rigor of backcasting to move from narrative aspiration (H3 vision) to testable pathway (what H2 actions lead there).

Three Horizons Analysis differs from Scenario Planning, another foundational futures methodology. Scenario planning constructs several fully-elaborated, internally-consistent narratives of alternative futures, each plausible, each internally coherent, but each representing a different outcome contingent on different assumptions or decisions. Scenarios are alternative stories: "In scenario A, AI advances rapidly and reshapes labor; in scenario B, AI plateaus due to technical limits; in scenario C, AI is heavily regulated and constrained." Three Horizons, by contrast, does not typically construct alternative futures; it maps a transition structure from current to one (or multiple) emergent system(s). However, the methods are highly complementary: multiple scenarios can be mapped onto Three Horizons, with different scenarios showing different H3 end-states and different H2 actor ecosystems leading there; Three Horizons can provide the scaffolding for scenario development by identifying key H2 variables and transition uncertainties. Practitioners typically use scenario planning to develop H3 options or to explore how H2 dynamics might unfold under different assumptions; they use Three Horizons to make strategic commitments across all horizons rather than engaging in exploratory scenario thinking.

Three Horizons Analysis is also not Linear Planning or Extrapolative Forecasting, though it is sometimes mistakenly practiced that way. Linear planning treats the future as a continuous extension of the present: the trends that are visible today will continue in the same direction and rate. Three Horizons explicitly rejects this by building system-change dynamics into the framework: H1 is under stress, H2 represents alternatives that challenge H1's assumptions, and H3 represents a fundamentally different system. Extrapolative forecasting takes historical trends and projects them forward; Three Horizons acknowledges that the dominant-system's trajectory is unsustainable or challenged and that transition to a different system is the strategic question. The failure mode is treating Three Horizons as "three time-periods in an otherwise linear-plan framework"—extrapolating H1 forward for three years (H1 horizon), five years (H2 horizon), and ten years (H3 horizon)—rather than recognizing that H1, H2, and H3 are about system types, not calendar horizons.

Finally, Three Horizons Analysis is not System Dynamics Modeling or Agent-Based Modeling, though it can be enriched by either. System dynamics models formal feedback loops and delays; agent-based models simulate how autonomous actors with heterogeneous behaviors produce emergent outcomes. Three Horizons is descriptive and strategic at a higher level than formal modeling: it maps systems and actors without specifying the quantitative parameters or simulation logic that dynamics models require. However, Three Horizons strategic frameworks often feed into system dynamics or agent-based models: the H1/H2/H3 structure and the identified actors, pressures, and innovations provide the structure and parameters for formal modeling. The distinction clarifies that Three Horizons can be conducted qualitatively (interviews, workshops, document analysis) at the organizational-strategy level, while formal modeling requires quantitative data and is typically deployed after the Three Horizons strategic mapping to test pathways and understand sensitivities.

Solution Archetypes

No catalogued solution archetypes reference this prime yet.

Notes

The review_flag contested_construct captures the methodological tension between the McKinsey Three Horizons of Growth framework^[1] and the Sharpe-Hodgson Three Horizons framework^[2]. Both are called "Three Horizons" in practice, both use three-layer structure, but they have substantively different stances — McKinsey is instrumental-descriptive; Sharpe-Hodgson is normative-transformative. Practitioners sometimes conflate the two. The flag preserves this tension for Pass B treatment. The v1 entry does not distinguish the two lineages; the v2 entry does.

The review_flag contested_construct also captures the academic debate between Three Horizons as articulated in foresight practice and the multi-level-perspective (MLP) transitions theory in academic sustainability-transitions research (Geels 2002 onward)^[4]. Both frameworks address overlapping-transition dynamics; both have adherents; they use different vocabulary and emphasize different mechanisms. The flag preserves this productive tension.

Origin-domain: v1 had only futurism_strategic_foresight. V2 adds organizational_management_science as alternate, reflecting the McKinsey-lineage origin and its substantial use in corporate-strategy practice. The primary origin remains futurism_strategic_foresight because the Sharpe-Hodgson lineage that is most expressive of the transition-dynamics framing comes from the foresight tradition.

References

[1] Baghai, Mehrdad, Stephen Coley, and David White. The Alchemy of Growth: Practical Insights for Building the Enduring Enterprise. Cambridge, MA: Perseus Publishing, 2000 (originally published 1999). Foundational McKinsey Three Horizons of Growth framework, articulating H1 (extend and defend the core), H2 (build emerging businesses), and H3 (create viable options) as a portfolio-allocation discipline for sustained corporate growth. ↩

[2] Sharpe, Bill. Three Horizons: The Patterning of Hope. Axminster, UK: Triarchy Press, 2013. Foundational Sharpe-Hodgson Three Horizons framework. ↩

[3] International Futures Forum (IFF), founded 2001, based in St Andrews and Aberdour, Scotland. Institutional home of the Sharpe-Hodgson Three Horizons methodology. Publications include Our Future Scotland (with Scottish Government, 2014); Scotland 2030: A Transformative Vision (2018); and Three Horizons applied work with NHS Scotland and the Health Foundation during 2012–2018. See https://www.internationalfuturesforum.com/ and IFF/H3Uni publication archive. ↩

[4] Geels, Frank W. "Technological Transitions as Evolutionary Reconfiguration Processes: A Multi-Level Perspective and a Case-Study." Research Policy 31, no. 8–9 (December 2002): 1257–1274. DOI 10.1016/S0048-7333(02)00062-8. Canonical multi-level-perspective (MLP) articulation: niche-level innovations are incubated alongside the regime, gradually accumulating technical and institutional support needed to displace incumbent configurations under landscape pressure. ↩

[5] Kuhn, Thomas S. The Structure of Scientific Revolutions. Chicago: University of Chicago Press, 1962. ↩

[6] Christensen, Clayton M. The Innovator's Dilemma: When New Technologies Cause Great Firms to Fail. Boston: Harvard Business School Press, 1997. Extended in Christensen, Clayton M., and Michael E. Raynor. The Innovator's Solution: Creating and Sustaining Successful Growth. Boston: Harvard Business School Press, 2003. The theory has been contested post-2010 — see Lepore, Jill, "The Disruption Machine," The New Yorker, 23 June 2014. ↩

[7] O'Reilly, Charles A., III, and Michael L. Tushman. "The Ambidextrous Organization." Harvard Business Review 82, no. 4 (April 2004): 74–81. Earlier framing in Tushman, Michael L., and Charles A. O'Reilly III, "Ambidextrous Organizations: Managing Evolutionary and Revolutionary Change," California Management Review 38, no. 4 (Summer 1996): 8–30, DOI 10.2307/41165852. ↩

[8] Foster, Richard N. Innovation: The Attacker's Advantage. New York: Summit Books, 1986. Develops the technology S-curve as the canonical pattern of incumbent technology approaching its physical or economic limits while a successor technology climbs its own curve, mapping directly onto H1-to-H2 transition dynamics in product strategy. ↩

[9] March, J. G. (1991). "Exploration and exploitation in organizational learning." Organization Science, 2(1), 71–87. ↩

[10] Govindarajan, Vijay, and Chris Trimble. The Other Side of Innovation: Solving the Execution Challenge. Boston: Harvard Business Review Press, 2010. Argues that breakthrough innovation requires a dedicated organizational and budgetary track separated from the performance engine of the core business; provides operational discipline for explicit H1/H2/H3 portfolio allocation. ↩

[11] Sharpe, Bill, and Anthony Hodgson. Towards a New Reality: Strategy and Foresight in a Complex World. International Futures Forum / H3Uni working paper, 1999. Original articulation of the three-horizons-of-system-transition framework that became the Sharpe-Hodgson lineage, foregrounding the overlapping pattern of dominant present, contested transition, and emerging future system. ↩

[12] Sharpe, Bill. Three Horizons: The Patterning of Hope. Axminster, UK: Triarchy Press, 2013. Characterizes H1 as the managerial horizon — the dominant present system whose fitness for the current operating context begins to erode as that context shifts — and treats stress signals in H1 as a diagnostic input to multi-horizon strategy. ↩

[13] Curry, Andrew, and Anthony Hodgson. "Seeing in Multiple Horizons: Connecting Futures to Strategy." Journal of Futures Studies 13, no. 1 (August 2008): 1–20. Develops the methodological discipline of holding the dominant present, the contested transition, and an aspirational future system in simultaneous view, with explicit attention to how H3 envisioning informs H2 investment selection. ↩

[14] Loorbach, Derk. "Transition Management for Sustainable Development: A Prescriptive, Complexity-Based Governance Framework." Governance 23, no. 1 (January 2010): 161–183. DOI 10.1111/j.1468-0491.2009.01471.x. Treats incumbent-versus-emerging dynamics in transition management: regime structures optimized for stability actively impede the experimentation needed to develop their successor, requiring deliberate niche-protection and arena-design. ↩

[15] Sharma, Monica. Radical Transformational Leadership: Strategic Action for Change Agents. Berkeley, CA: North Atlantic Books, 2017 (work originally developed in UN-system practice from 2007 onward). Articulates values-grounded, system-level transformation in which the work is as much about reorienting purpose and identity as restructuring operations; maps to H3 as explicitly normative envisioning. ↩

[16] Schein, E. H. (1985). Organizational Culture and Leadership. Jossey-Bass. Foundational text on organizational culture: develops culture as the shared assumptions, values, and norms that determine which members and practices are compatible with the organization, and provides the canonical framework for analyzing cultural compatibility in mergers, hires, and cross-organizational collaboration. ↩

[17] Bell, Wendell. Foundations of Futures Studies: Human Science for a New Era. New Brunswick, NJ: Transaction Publishers, 1997. Two-volume canonical text placing "images of the future" at the methodological core of futures studies; treats H2-style experimental probes in the present as a way of learning what the emerging system might require. ↩

[18] Miller, Riel, ed. Transforming the Future: Anticipation in the 21^st Century. Paris and London: UNESCO and Routledge, 2018. Develops futures literacy as the capability to surface the assumptions about the future that shape current decisions, and to deliberately use alternative assumptions to expose alternative present-day choices; foundational for normative H3 work. ↩

[19] International Futures Forum and H3Uni. The Three Horizons Kit. St Andrews and Aberdour, Scotland: International Futures Forum, 2017. Practitioner toolkit operationalizing the Sharpe-Hodgson framework with facilitation moves for holding managerial-system rigor (H1) and visionary-system experimentation (H3) in the same conversation while supporting H2 transition activity. ↩

[20] Tushman, M. L., & O'Reilly, C. A. (1996). "Ambidextrous organizations: Managing evolutionary and revolutionary change." California Management Review, 38(4), 8–30.

[21] Gibson, C. B., & Birkinshaw, J. (2004). "The antecedents, consequences, and mediating role of organizational ambidexterity." Academy of Management Journal, 47(2), 209–226.

[22] Raisch, S., & Birkinshaw, J. (2008). "Organizational ambidexterity: Antecedents, outcomes, and moderators." Journal of Management, 34(3), 375–409.

[23] Benner, M. J., & Tushman, M. L. (2003). "Exploitation, exploration, and process management: The productivity dilemma revisited." Academy of Management Review, 28(2), 238–256.

[24] He, Z.-L., & Wong, P.-K. (2004). "Exploration vs. exploitation: An empirical test of the ambidexterity hypothesis." Organization Science, 15(4), 481–494.

[25] Leonard-Barton, D. (1992). "Core capabilities and core rigidities: A paradox in managing new product development." Strategic Management Journal, 13(S2), 111–125.

[26] Christensen, C. M. (1997). The Innovator's Dilemma: When New Technologies Cause Great Firms to Fail. Harvard Business School Press.

[27] O'Reilly, C. A., & Tushman, M. L. (1997). "Winning through innovation." In Competing on the Edge: Strategy as Structured Chaos. Harvard Business School Press.