Skip to content

Three Horizon Transition Mapping

Map current-system maintenance, emerging transition, and future-system development so change portfolios are timed coherently.

Essence

Three-Horizon Transition Mapping is a way to keep the present, the transition, and the future visible at the same time. It is useful when a system cannot simply abandon what works now, but also cannot keep optimizing the present as if no deeper change is coming.

The archetype separates work into three strategic roles. Horizon One is the current system that still has obligations, value, and dependencies. Horizon Two is the unstable transition space where experiments, hybrids, conflicts, and bridge capabilities appear. Horizon Three is the emerging or desired future pattern that could eventually become dominant. The map matters because these roles require different metrics, funding logic, timing, and governance.

Compression statement

When present operations, transitional innovations, and future possibilities compete, map them across three horizons to balance continuity, experimentation, and transformation.

Canonical formula: H1 current system + H2 transition space + H3 future pattern + signals + portfolio rebalancing => coherent transition strategy

When to Use This Archetype

Use this archetype when present operations, transition experiments, and future-building efforts are competing for attention but are being evaluated as if they are the same kind of work. It is especially helpful when an organization, policy system, infrastructure system, or community must maintain reliability while moving toward a different model.

It is also useful when people are polarized between defenders of the current system and advocates of a future state. The three-horizon map gives both sides a more precise language: some current capacity may need preservation, some legacy patterns may need retirement, some transitional experiments need protection, and some future bets need stronger evidence before large-scale commitment.

Structural Problem

The structural problem is not merely uncertainty about the future. The deeper problem is coexistence. The current system is still active and often still necessary; the future pattern is not yet mature; and the transition space is full of fragile experiments that are easy to kill, capture, or overhype.

Without a horizon structure, decision makers tend to collapse these roles. They judge experiments by current efficiency metrics, treat future aspirations as slogans, overfund the legacy system because it is measurable, or abandon present responsibilities before replacements are ready. The result is either lock-in, chaos, or a portfolio of disconnected initiatives.

Intervention Logic

The intervention starts by naming the strategic domain and the transition question. It then describes Horizon One, Horizon Two, and Horizon Three as roles rather than as simple calendar periods. A Horizon One initiative is not just short-term; it sustains or defends the current system. A Horizon Two initiative is not just medium-term; it tests, bridges, or destabilizes the relationship between the old and future systems. A Horizon Three initiative is not just long-term; it expresses the future pattern the system may need to grow into.

Once the roles are defined, the archetype classifies initiatives, assets, policies, capabilities, and commitments. It then asks what metrics, signals, resources, and governance each horizon needs. This turns the map from a picture into a decision tool: maintain this, protect that experiment, retire this dependency, scale that bridge, monitor this signal, or rebalance the portfolio.

Key Components

Three-Horizon Transition Mapping keeps three strategic roles visible at the same time so an organization can sustain present obligations, protect transitional learning, and grow into a different future without collapsing all three into a single agenda. The first three components describe the roles themselves. Horizon One Current System names the dominant present configuration — what still creates value, what is becoming brittle, what dependencies make continuity necessary — so future strategy does not silently neglect current obligations. Horizon Two Transition Space names the experiments, hybrids, and bridge capabilities that connect the present to the future, marking the most fragile part of the portfolio because it is easy to starve, capture, or overhype. Horizon Three Future Pattern names the emerging configuration the system is trying to make viable, guiding action without pretending to be a confirmed prediction.

Three further components turn the roles into a usable portfolio. Horizon Role Classification assigns every initiative, capability, asset, and policy to a strategic role rather than to a calendar bucket, refusing the temptation to treat short-, medium-, and long-term as synonyms for the horizons. The Portfolio Balance Map shows how funding, talent, attention, and risk are distributed across those roles, surfacing concentration and starvation patterns. The Transition Signal defines what evidence will indicate that the current system is weakening, the transition is maturing, or the future pattern is becoming more viable — preventing the map from being judged only by emotion or status.

The remaining five components govern movement, measurement, and revision so the map keeps shaping decisions over time. The Continuity and Cannibalization Rule makes explicit what should be preserved, migrated, shielded, retired, or deliberately cannibalized, refusing the comfort of leaving these choices implicit. The Timing and Dependency Pathway orders dependencies so the system neither exits the present too early nor waits until the future is too late. The Horizon-Specific Metric Set prevents current-system efficiency metrics from killing transition learning and prevents future-system metrics from destabilizing essential services. The Tension Review Loop revisits conflicts, evidence, and resource balance, keeping the map alive as conditions change. The Stakeholder Expectation Bridge explains why the horizons coexist and what different groups can expect during the transition, protecting the design against legacy capture and future cosplay alike.

ComponentDescription
Horizon One Current System ↗describes the dominant present system, including what still creates value and what is becoming brittle. This prevents future strategy from neglecting current obligations.
Horizon Two Transition Space ↗identifies experiments, hybrids, and conflicts that connect the present to the future. This is where transformation is most vulnerable to capture or starvation.
Horizon Three Future Pattern ↗names the future configuration the system is trying to make viable. It should guide action without pretending to be a guaranteed prediction.
Horizon Role Classification ↗assigns initiatives to strategic roles so the portfolio is not just a list of projects.
Portfolio Balance Map ↗shows how funding, talent, attention, and risk are distributed across horizons.
Transition Signal ↗defines evidence that the current system is weakening, the transition is maturing, or the future pattern is becoming more viable.
Continuity and Cannibalization Rule ↗makes explicit what should be preserved, migrated, shielded, retired, or deliberately cannibalized.
Timing and Dependency Pathway ↗orders dependencies so the system neither exits the present too early nor waits until the future is too late.
Horizon-Specific Metric Set ↗prevents current-system metrics from killing transition learning or future metrics from destabilizing essential services.
Tension Review Loop ↗keeps the map alive by revisiting conflicts, evidence, and resource balance.
Stakeholder Expectation Bridge ↗explains why different horizons coexist and what different groups can expect during the transition.

Common Mechanisms

A Three Horizons Map is the most recognizable mechanism, but the diagram is not the archetype. It implements the archetype only when the H1/H2/H3 distinctions change decisions about resources, timing, metrics, or governance.

An Innovation Portfolio Review implements the archetype by asking whether the portfolio is over-concentrated in present optimization, unsupported transition experiments, or speculative future bets. Core / Emerging / Future Investment Buckets are a lighter classification mechanism, useful only when they do more than relabel projects.

A Strategic Transition Map connects horizon roles to dependencies, owners, and commitments. A Transition Signal Dashboard tracks the evidence that justifies scaling, pausing, retiring, or rebalancing initiatives. An Experiment Incubation Pipeline protects Horizon Two work long enough to learn, while a Horizon-Specific Metric Dashboard prevents each horizon from being judged by the wrong standard.

Workshops, roadmaps, dashboards, and diagrams are implementation mechanisms. They should not be confused with the archetype itself, which is the transferable logic of managing current-transition-future coexistence.

  • Core / Emerging / Future Investment Buckets
  • Experiment Incubation Pipeline
  • Horizon Budget Allocation
  • Horizon-Specific Metric Dashboard
  • Innovation Portfolio Review — A recurring governance review that checks whether resources are over-concentrated in one bet-horizon and rebalances the split across run-the-business, transition, and future-building work.
  • Lifecycle Portfolio Review
  • Strategic Transition Map
  • Strategic Transition Workshop
  • Three Horizons Map
  • Transition Signal Dashboard

Parameter / Tuning Dimensions

Important tuning dimensions include the time span of the horizons, the breadth of the strategic domain, the share of resources allocated to each horizon, the strength of protection for Horizon Two experiments, and the evidence threshold for scaling or retiring work.

Other parameters include how explicit the future pattern should be, how much current-system continuity must be protected, how often the map is reviewed, who gets to classify initiatives, and whether the map is used primarily for strategy, budgeting, communication, or transition governance.

Invariants to Preserve

The central invariant is the distinction among horizon roles. Horizon One, Horizon Two, and Horizon Three should not collapse into short-, medium-, and long-term labels. They must preserve the structural relationship between the current system, the transitional zone, and the future pattern.

The second invariant is accountability to action. A three-horizon map that does not influence metrics, resources, timing, protection, scaling, retirement, or communication is only a diagram. The third invariant is revisability: as signals change, initiatives may need to be reclassified and the portfolio rebalanced.

Target Outcomes

The target outcomes are clearer strategic role assignments, better protection for transition learning, more responsible maintenance of current obligations, and more disciplined investment in future patterns. A strong implementation reduces both legacy lock-in and reckless future-chasing.

It should also improve communication. Stakeholders can understand why some present work is preserved, why some experiments are protected, why some legacy strengths may be cannibalized, and why not every future possibility receives immediate full commitment.

Tradeoffs

The archetype makes uncomfortable choices visible. It can reveal that some valuable current capabilities need eventual retirement, that some celebrated experiments do not actually help the transition, or that some future narratives are not yet viable.

It also creates governance burdens. Horizon Two work needs special metrics and protection, but not unlimited freedom. Horizon One needs continuity support, but not indefinite immunity. Horizon Three needs imagination and commitment, but not insulation from evidence.

Failure Modes

The most common failure mode is diagram theater: producing a polished three-horizons graphic without changing any decision. Another is legacy capture, where transition initiatives are reshaped to preserve the current model while using transformation language.

Other failure modes include premature abandonment of essential current capacity, starvation of transition experiments, future cosplay, false linearity, metric mismatch, and stakeholder whiplash. Most failures come from forgetting that the horizons are strategic roles that coexist and interact, not a simple sequence of dates.

Neighbor Distinctions

Three-Horizon Transition Mapping is distinct from Scenario Portfolio Planning because it does not primarily explore multiple plausible futures; it maps the relationship among current, transition, and future systems. It is distinct from Backcasting Pathway Design because it does not only work backward from a desired endpoint; it manages coexistence among horizons.

It is close to Ambidextrous Portfolio Design, but ambidexterity usually balances exploitation and exploration, while this archetype requires explicit H1/H2/H3 temporal transition roles. It is close to Creative Destruction Management, but the three-horizon map includes preservation and bridge-building, not just replacement. It can use Horizon Scanning System outputs as signals, but scanning alone does not govern the portfolio.

Cross-Domain Examples

In energy transition, the map can preserve grid reliability while supporting storage pilots and future renewable infrastructure. In software architecture, it can keep a legacy system stable while transitional services and a future platform mature. In education, it can protect current learners while competency-based assessment pilots prepare a future model.

In healthcare, the archetype can distinguish today’s fee-for-service operations from integrated-care experiments and a future population-health pattern. In public administration, it can help a city maintain current services while testing digital and proactive service models.

Non-Examples

A quarterly roadmap is not Three-Horizon Transition Mapping if it only orders tasks by date. A futures workshop is not this archetype if it produces interesting ideas but no horizon classification, metrics, signals, or resource implications. A budget split into short-, medium-, and long-term projects is not enough if the split does not reflect current-system, transition, and future-pattern roles.

A prediction that one technology will replace another is also not enough. The archetype is about governing coexistence and transition, not predicting a replacement date.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

Also references 15 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Innovation Portfolio Three Horizons · domain variant · recognized

Uses the three-horizon structure to balance core optimization, transition experiments, and longer-term innovation bets.

  • Distinct from parent: The parent can map any current-transition-future system; this variant centers on innovation portfolios and investment governance.
  • Use when: An organization has an innovation portfolio but keeps judging every initiative by current-business metrics; Exploratory initiatives need protection without losing connection to strategic transition needs; Leadership must decide how much resource to place in core, adjacent, and future-facing work.
  • Typical domains: corporate strategy, R&D management, product portfolio planning
  • Common mechanisms: Innovation Portfolio Review, Core / Emerging / Future Investment Buckets

System Transition Horizons · scale variant · recognized

Applies the horizon map to social, ecological, policy, or infrastructure transitions where old and new systems coexist for long periods.

  • Distinct from parent: The parent is cross-domain; this variant emphasizes multi-actor system transformation and legitimacy during long transitions.
  • Use when: A transition spans institutions, infrastructure, norms, and multiple stakeholders; Current-system reliability must be preserved while future arrangements mature; Actors need to negotiate which legacy elements should be transformed, retired, or protected.
  • Typical domains: energy transition, health systems, public administration, education reform
  • Common mechanisms: Strategic Transition Map, Transition Signal Dashboard

Technology Transition Horizons · domain variant · recognized

Maps legacy technology, migration architecture, and future-state technology patterns so technical transition is neither frozen nor reckless.

  • Distinct from parent: The parent covers broader strategic transitions; this variant translates the horizon logic into technical migration design.
  • Use when: Legacy systems still carry critical operations but limit future capability; Migration requires intermediate architectures, parallel runs, or staged adoption; Technical teams need to decide which legacy investments to sustain, wrap, replace, or retire.
  • Typical domains: software architecture, infrastructure modernization, data platform migration
  • Common mechanisms: Experiment Incubation Pipeline, Horizon-Specific Metric Dashboard

Capability Migration Horizons · implementation variant · candidate

Uses the three horizons to migrate capabilities, roles, and routines rather than products, technologies, or policies.

  • Distinct from parent: The parent can map any transition; this candidate variant is about capability migration and practice change.
  • Use when: A group must continue current work while learning future capabilities; Old roles and incentives prevent new practices from stabilizing; The transition depends more on skill, identity, or operating rhythm than on a single artifact.
  • Typical domains: organizational change, workforce development, clinical practice change
  • Common mechanisms: Strategic Transition Workshop, Experiment Incubation Pipeline

Near names: Three Horizons, Three Horizons Framework, H1/H2/H3 Mapping, Current-Transition-Future Mapping, Transition Portfolio Mapping.