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.”
Mechanisms / Implementations¶
- 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
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.