Three Horizon Transition Mapping¶
Map current-system maintenance, emerging transition, and future-system development so change portfolios are timed coherently.
The Diagnostic Story¶
Symptom: Every initiative gets called strategic, so no one can tell which work sustains what must keep running, which bridges toward something new, and which builds the future. Future work gets celebrated in presentations but funded as a side project. Legacy teams read future work as a threat; future teams see present obligations as obstruction. Roadmaps show dates but not the coexistence and conflict among old, transitional, and emerging systems.
Pivot: Separate the work into three horizon roles — sustaining the current system, managing the transition, and developing future patterns — and classify every initiative by its actual role. Define signals and metrics appropriate to each horizon, and rebalance resources and timing as transition evidence accumulates.
Resolution: Maintain, migrate, experiment, scale, and retire decisions become legible across the portfolio. Transition experiments are protected from legacy metrics while remaining accountable to learning. Present obligations are not abandoned because future work is exciting, and future patterns can shape action without being mistaken for certainties.
Reach for this when you hear…¶
[energy grid operator] “We are running the coal plant, building storage, and piloting hydrogen all at once, and every budget meeting treats them as competing for the same pot instead of serving three different time horizons.”
[health system strategist] “The digital front door team keeps getting pulled into stabilizing the legacy EHR because leadership has no frame for why those two efforts need different metrics and different protection.”
[university administrator] “We are judging the online pilot by the same retention benchmarks as the residential program, and it is going to get killed before we learn whether the model works.”
When This Archetype Applies¶
Complete catalog groundingAt least one sufficient condition set is fully represented by existing primes or domain-specific abstractions.
Diagnostic problem
A system must keep current operations viable while preparing for a different future, but its activities are mixed together without a clear temporal role, causing legacy lock-in, unsupported experiments, or premature future bets.
What this problem means
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.
Show the applicability expression
Applicability expression4 distinct conditions
groundedpartly groundedopen
4 conditions, all required.
4Required in every casenumbered 1–4
These hold no matter which pattern applies.
Necessary but brittle incumbent · grounded
The current system is still necessary but shows signs of brittleness, legitimacy loss, cost pressure, or strategic exhaustion.
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. The narrower requirement in this condition set is: The current system is still necessary but shows signs of brittleness, legitimacy loss, cost pressure, or strategic exhaustion.
Visible immature future · grounded
Future possibilities are visible enough to influence strategy but not mature enough to replace current operations immediately.
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. The narrower requirement in this condition set is: Future possibilities are visible enough to influence strategy but not mature enough to replace current operations immediately.
Misjudged transition experiments · grounded
Transitional experiments exist but are judged by the wrong metrics, starved of support, or captured by legacy incentives.
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 narrower requirement in this condition set is: Transitional experiments exist but are judged by the wrong metrics, starved of support, or captured by legacy incentives.
Cross-horizon resource allocation · grounded
Decision makers need to allocate resources across maintain, migrate, experiment, scale, and retire choices.
Without a horizon structure, decision makers tend to collapse these roles. The narrower requirement in this condition set is: Decision makers need to allocate resources across maintain, migrate, experiment, scale, and retire choices.
Other requirements and context (1)
Why these sit outside the expression
Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.
Supporting contextStakeholders disagree because some prioritize reliability, some demand transformation, and some are already investing in future patterns.
The present system must remain functional long enough for transition to be safe, but too much present-system optimization delays the future pattern; too much future enthusiasm destabilizes the present before alternatives are ready. In this archetype, the relevant contextual consideration is: Stakeholders disagree because some prioritize reliability, some demand transformation, and some are already investing in future patterns. It helps interpret the situation or strengthens the practical case for examining the archetype.
Coverage
4 of 4 conditions grounded.
Mechanisms / Implementations¶
- Core / Emerging / Future Investment Buckets: Groups initiatives into present core, emerging transition, and future bets, then tallies the split so the portfolio can be reviewed as three comparable groups.
- Experiment Incubation Pipeline: Gives Horizon Two experiments a protected lane with explicit learning goals and scale-or-stop gates, shielding them from legacy metrics until they have earned a verdict.
- Horizon Budget Allocation: Sets and defends how much funding, people, attention, and risk tolerance each horizon receives, including protected floors for transition work and a ring-fenced line for legacy support.
- Horizon-Specific Metric Dashboard: Gives each horizon its own metric panel — efficiency for the core, validated learning for the transition, viability for the future — so no horizon is judged by another's yardstick.
- 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: A recurring review that plots each asset on its own maturity-to-decline curve and decides renew, retire, replace, or preserve by lifecycle stage.
- Strategic Transition Map: A planning artifact that wires horizon roles into a dependency-ordered sequence of dated, owned commitments — migrate this before retiring that.
- Strategic Transition Workshop: A facilitated live session where stakeholders classify initiatives, surface and argue horizon tensions, articulate the future pattern, and leave with aligned expectations.
- Three Horizons Map: Visualizes current-system, transition, and future-pattern initiatives on an H1/H2/H3 structure so portfolio tensions become visible at a glance.
- Transition Signal Dashboard: Tracks leading signals that the current system is weakening, the transition is maturing, or the future is becoming viable, and flags when to maintain, scale, adapt, or retire.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (3)
- Ambidexterity (Exploit vs. Explore): Balance exploit vs explore.
- Creative Destruction: Replacement through innovation.
- Three Horizons Analysis: Short, medium, long-term transitions.
Also references 15 related abstractions
- Adaptation: Systems adjust to conditions.
- Balance: Even distribution of elements.
- Continuity vs. Rupture: Gradual vs abrupt change.
- Emergence: Complex patterns from simple rules.
- Feedback: Outputs influence inputs.
- Inertia: Resistance to change.
- Metasystem Transition: Systems form higher-level system.
- Resilience: Absorb shocks and adapt.
- Resource Management: Allocation of finite assets.
- State and State Transition: Captures system condition and evolution.
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.
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.
Technology Transition Horizons · domain variant · recognized
Maps legacy technology, migration architecture, and future-state technology patterns so technical transition is neither frozen nor reckless.
Capability Migration Horizons · implementation variant · candidate
Uses the three horizons to migrate capabilities, roles, and routines rather than products, technologies, or policies.
Editorial Notes¶
Problem Classification¶
Classification: Timing, Transition & Path-Dependence Failure → Continuity, Regime, Legacy & Liminal Transition
Problem kernel: current operations experiments and future system roles are conflated
Rationale: Earliest causal condition: A system must keep current operations viable while preparing for a different future, but its activities are mixed together without a clear temporal role, causing legacy lock-in, unsupported experiments, or premature future bets.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A system must keep current operations viable while preparing for a different future, but its activities are mixed together without a clear temporal role, causing legacy lock-in, unsupported experiments, or premature future bets. That is a continuity regime legacy and liminal transition problem because Movement between old and new regimes creates rupture, service loss, stranded legacy, or ambiguous liminal status because the crossing is treated as a switch.
Review outcome: Independent reviewer agreement; high confidence.