Three Horizons Framework
Strategic Design Foundation
Three Horizons Framework provides the strategic architecture for Phased Internal Build by defining what the organization must accomplish at each horizon. Competitive analysis (Porter's) revealed we must defend core operations, build proprietary advantages, and create strategic options. Organizational constraints (7S) required a progressive, voluntary, bounded-risk approach. Three Horizons framework structures these requirements into three strategic objectives: H1 (Defend/Extend Core), H2 (Build Emerging Capabilities), H3 (Create Transformative Options). From these horizon objectives, we designed six phases to achieve the required transformation with exit optionality at every horizon boundary.
What Each Horizon Must Accomplish
Three Horizons Framework (McKinsey) provides the strategic architecture by defining three clear objectives: defend core operations, build emerging competitive advantages, and create transformative strategic options. Each horizon's objectives are derived directly from competitive analysis (Porter's), organizational constraints (7S), and stakeholder requirements.
Horizon 1: Defend and Extend the Core
Strategic Imperative: Core business under threat from lean competitors (Porter's), organization in crisis requiring immediate value delivery (7S, stakeholders), must defend by improving existing operations efficiency.
| What H1 Must Deliver | Success Criteria |
|---|---|
| Defend Core Business: Protect competitive position under threat | Core operations measurably more efficient |
| Extend Core Efficiency: Improve operations without disruption | Competitive vulnerability reduced |
| Preserve Client Value: No workflow changes, better service | Staff self-initiating adoption (proof of value) |
| Generate Resources: ROI funds next horizon | Positive ROI funding H2 consideration |
| Build Credibility: Success creates trust for H2 investment | Decision point: Can stop with defended/extended core |
Horizon 2: Build Emerging Competitive Advantages
Strategic Imperative: Only defensible competitive advantage is proprietary capabilities on unique institutional knowledge (Porter's), must build with existing staff as AI talent is inaccessible (7S), stakeholders require non-commoditizable capabilities.
| What H2 Must Deliver | Success Criteria |
|---|---|
| Genuinely New Capabilities: Not faster existing work, but work we couldn't do before | New capabilities operational (not just efficiency gains) |
| Proprietary Advantage: Capabilities competitors cannot purchase or replicate | Staff can do work previously impossible |
| Defensible Differentiation: Based on unique institutional knowledge | Competitive differentiation achieved |
| Advanced Staff Capabilities: Internal expertise, not external dependency | Proprietary advantage built on institutional knowledge |
| Competitive Moat: Sustainable advantage that strengthens over time | Decision point: Can stop with defended core + competitive advantages |
Horizon 3: Create Transformative Strategic Options
Strategic Imperative: Rapidly changing AI environment requires strategic flexibility and ongoing innovation capacity (Porter's, 7S), stakeholders require strategic optionality beyond one-time transformation.
| What H3 Must Deliver | Success Criteria |
|---|---|
| Transformative Capabilities: Fundamentally different ways of operating | Breakthrough capabilities operational |
| Strategic Optionality: Options for future innovation and adaptation | Strategic options created (not just current improvements) |
| Organizational-Scale Intelligence: Enterprise-wide AI capabilities | Innovation capacity built (ongoing capability development) |
| Innovation Capacity: Internal expertise to continue evolving | Organizational transformation complete |
| Future-Ready Organization: Sustainable competitive advantage | Sustainable advantage: Capability strengthens over time |
From Horizons to Phase Design
Design Principle
Start with horizon objectives → Design phases to achieve them
Each horizon's strategic requirements drove the design of specific phases. Phases are not arbitrary divisions—they are purpose-built to accomplish horizon objectives while respecting organizational constraints.
Horizon 1: Phases 0, 1, 2 (Defend/Extend Core)
H1 Objective: Defend and extend core operations through existing capabilities augmentation
| Phase | Purpose & Design Rationale | Why H1? | Deliverable | Value |
|---|---|---|---|---|
| Phase 0: Registry Foundation (Month 0) | Put registries in place to track experiments, data, and models | Must establish tracking infrastructure before any AI work begins | Experiment registry, data registry, model registry | Enables systematic AI development and governance |
| Phase 1: Knowledge Access (Months 1-3) | Make trapped knowledge accessible to defend competitive position | Works with existing knowledge, just makes it accessible | Natural language query, 4 languages, universal access | Core operations immediately more efficient |
| Phase 2: Task Automation (Months 4-9) | Automate repetitive work in existing workflows | Works with existing tasks and processes, just automates them | 50% repetitive work automated | Extended core efficiency, resources generated for H2 |
Why H1 Required Three Phases: To defend and extend core operations, we needed to establish tracking infrastructure (Phase 0), make existing knowledge accessible (Phase 1), and automate existing workflows (Phase 2). All three phases work with what already exists rather than creating new capabilities. Additionally, stakeholder requirements for quarterly ROI (S1) and exit optionality (S2) drove the decision to break H1 into three phases rather than one—each phase delivers independent value with decision points, enabling progressive investment with bounded risk.
H1 Investment: $106,000 ($0 Phase 0 + $62.4K Phase 1 + $43.6K Phase 2) | H1 Timeline: Months 0-9 | H1 Decision Point: Can stop with defended/extended core operations
Horizon 2: Phase 3 (Build Emerging)
H2 Objective: Build genuinely new competitive capabilities
| Phase | Purpose & Design Rationale | Why H2? | Deliverable | Value |
|---|---|---|---|---|
| Phase 3: Division Intelligence (Months 7-12) | Create sophisticated analytical capabilities on unique institutional knowledge | Creates genuinely new capabilities that competitors cannot purchase or replicate | Advanced analysis, division-specific intelligence, sophisticated queries | Staff can do work previously impossible (not just faster) |
Why H2 Required This Phase: To build genuinely new competitive advantages, we needed capabilities that don't exist today. Phase 3 was designed to create division-level intelligence—sophisticated analytical capabilities that enable work previously impossible, not just faster existing work.
H2 Investment: $31,200 (Phase 3) | H2 Timeline: Months 7-12 (overlap with H1 Months 7-9) | H2 Decision Point: Can stop with defended core + competitive advantages
Horizon 3: Phases 4 & 5 (Create Transformative Options)
H3 Objective: Create transformative strategic options
| Phase | Purpose & Design Rationale | Why H3? | Deliverable | Value |
|---|---|---|---|---|
| Phase 4: Agentic Discovery (Months 10-15) | Enable cross-division experimentation in sandboxed environments to discover patterns and generate training data. H3 requires breakthrough capabilities—Phase 4 creates experimental foundation through siloed discovery | Siloed experimentation generates training corpus for orchestration | Experimentation patterns, cross-division insights, training data corpus | Discovery of emergent organizational patterns |
| Phase 5: Orchestrated System (Months 13-18) | Train orchestrator on Phase 4 experimental data to enable organizational-scale intelligence. Phase 5 transforms siloed discoveries into unified orchestration | Transforms how the organization operates (not incremental improvement) | Trained orchestrator, integrated multi-agent system, organizational-scale intelligence | Strategic options for future innovation and adaptation |
Why H3 Required Two Phases: To create transformative strategic options, we needed breakthrough capabilities beyond incremental improvements. Phase 4 generates training data through siloed experimentation across divisions—discovering patterns in sandboxed environments. Phase 5 uses this training data to build the orchestrator that unifies these discoveries into organizational-scale intelligence. Phase 4 creates the data that makes Phase 5 possible.
H3 Investment: $25,900 ($15.5K Phase 4 + $10.4K Phase 5) | H3 Timeline: Months 10-18 (overlap with H2 Months 10-12, Phase 4/5 overlap Months 13-15) | H3 Outcome: Full transformation complete, ongoing innovation capacity
Final Phase Design
Six phases designed from three horizon objectives:
| Phase | Timeline | Horizon | Purpose | Deliverable | Investment |
|---|---|---|---|---|---|
| Phase 0: Registry Foundation | Month 0 | H1 | Establish tracking infrastructure for systematic AI development | Experiment, data, model registries | $0 infrastructure |
| Phase 1: Knowledge Access | Months 1-3 | H1 | Make existing knowledge accessible to defend competitive position | Natural language query, 4 languages, universal access | $62,400 |
| Phase 2: Task Automation | Months 4-9 | H1 | Automate repetitive work in existing workflows to extend core efficiency | 50% repetitive work automated | $43,600 |
| Phase 3: Division Intelligence | Months 7-12 | H2 | Create genuinely new analytical capabilities on institutional knowledge | Advanced analysis, division-specific intelligence | $31,200 |
| Phase 4: Agentic Discovery | Months 10-15 | H3 | Enable cross-division experimentation to discover patterns and generate training data | Experimentation patterns, training data corpus | $15,500 |
| Phase 5: Orchestrated System | Months 13-18 | H3 | Train orchestrator on Phase 4 data for organizational-scale intelligence | Trained orchestrator, integrated multi-agent system | $10,400 |
Total Investment: $163.1K Direct Investment ($11,100 infrastructure) | Total Timeline: 18 months | Decision Points: After Phase 2 (H1), Phase 3 (H2), Phase 4 (H3), or Phase 5 (H3)
Design Validation
The phase design accomplishes all horizon objectives:
| Horizon Objective | Phase(s) Designed | How Phases Achieve Objective |
|---|---|---|
| H1: Defend Core | Phases 0-2 | Registry foundation + knowledge access + task automation = defended/extended core |
| H2: Build Emerging | Phase 3 | Division intelligence = genuinely new competitive capabilities |
| H3: Create Transformative | Phases 4-5 | Agentic discovery (experimentation/training data) + orchestrated system = transformative strategic options |
Strategic coherence: Every phase exists to accomplish a specific horizon objective. No phase is arbitrary. Phase 4 generates the training data that Phase 5 requires—they are sequential and interdependent within H3.