What is Dealing with Darwin about?

Dealing with Darwin is Geoffrey Moore's 2005 argument that established companies face a form of Darwinian selection pressure that startup logic cannot address, and that surviving it requires a clear understanding of where a company sits in its technology lifecycle and what kind of innovation is appropriate at each stage. Moore is best known for Crossing the Chasm, and this book extends that framework: where Chasm dealt with getting disruptive innovations to mainstream markets, Dealing with Darwin deals with the question of what an established company does after it has made it across.

The central framework is the innovation spectrum. At one end is disruptive innovation — the kind that creates new markets and redefines categories. At the other end is process innovation — optimizing and extracting value from existing offerings. Most companies need both, but the mistake Moore identifies is applying disruptive-innovation thinking to businesses that have reached maturity, or applying process optimization to categories that are still in flux. The two require different organizational cultures, different resource allocation, and different success metrics.

Moore introduces what he calls the innovation zone — the place where a company's differentiation actually lives and where innovation must be concentrated — and the context zone, where work needs to be done competently but doesn't differentiate the company. His prescription for most established companies is to migrate as much context work as possible to partners, outsourcing, and shared services, while concentrating internal investment on the zone where they can actually win. This is straightforward in theory and hard to execute against institutional resistance.

The book is practical rather than theoretical, and Moore's consulting background shows in both the clarity of the frameworks and the prevalence of enterprise tech examples. Readers outside the tech industry will need to do more translation work. But the core insight — that different stages of the technology lifecycle require fundamentally different innovation strategies, and that confusing them is the primary cause of large-company stagnation — is well argued and applicable beyond the specific examples Moore uses.