# Chapter 17: To Infinity and Beyond

## Core Focus

Practical strategy execution at Canonical, transforming Ubuntu into the dominant cloud guest OS. Demonstrates business horizons, Porter's forces through evolution, legacy management, and strategic timing.

## Three Horizons Model (and its limitations)

From "Alchemy of Growth" (1999):
- **Horizon 1**: core profitable business (defend/extend)
- **Horizon 2**: emerging medium-term growth
- **Horizon 3**: long-term ventures for survival

Critique: inadequate without mapping. Horizons are context-specific and don't cleanly map to evolution stages or pioneer/settler/town planner roles.

## Legacy and Inertia

Legacy isn't tied to specific organizational roles. It emerges from "failure to evolve" anywhere in the system:
- Activities trapped behind inertia barriers
- Co-evolved practices resisting change
- Invisible lower-order systems

Any team can become legacy through failure to evolve.

## Porter's Five Forces Through Peace-War-Wonder

- **Wonder**: uncertain, consumer-driven, no established competitors
- **Peace**: product competition, occasional substitution threats
- **War**: industrialization threatens incumbents; new entrants dominate

## Strategic Timing

Identical hype cycle positions require radically different strategies depending on evolutionary stage:
- Cloud computing (2008): "all in" (operational value/industrialization)
- 3D printing (2008): "wait and see" (still custom/product)

## The Benefit Curve

Two waves of value:
- **Differential value**: advantage from being different (peaks early)
- **Operational value**: efficiency advantage (peaks later, during industrialization)

The gap between expected and actual benefit resembles the Gartner hype cycle.

## Case Study: Canonical's Cloud Strategy

**Challenge**: 300-person company vs. RedHat and Microsoft. Internal resistance viewed cloud as distraction from support-license revenue.

**Play**:
- Recognize cloud as industrialization (Horizon 2)
- Aggressively pursue guest OS market share ("land grab")
- Support co-evolved practices (DevOps, containerization)
- Provide transitional offerings for customers facing inertia

**Outcome**: Within 18 months, Ubuntu dominated cloud guest OS. A CIO observed: "the future was all RedHat and then suddenly it was all Ubuntu."

## Key Takeaways

1. Context determines strategy - same technology needs opposite approaches at different evolutionary positions
2. Legacy is predictable - understanding inertia lets you anticipate competitor paralysis
3. Timing requires mapping - hype cycles gain precision calibrated against evolutionary certainty
4. Organizational structure doesn't determine legacy
5. Co-evolution matters - ignoring practice evolution creates hidden inertia
6. Competitors' inertia is exploitable