The Extended Phenotype
Source: https://global.oup.com/academic/product/the-extended-phenotype-9780192880512 ↗
Dawkins considered this his most important book, yet it is far less read than The Selfish Gene.
The central argument: an organism's phenotype does not end at its skin.
The beaver's dam, the caddisfly's case, the snail's shell modified by a parasite -- all are expressions of genes reaching outward into the environment.
This insight connects directly to niche construction theory, which Laland, Odling-Smee, and Feldman would formalise two decades later.
For anyone thinking about how organisms reshape the conditions of their own selection, Extended Phenotype is where the thread begins.
It is also a harder, more philosophical book than its predecessor, and rewards the effort.
Central argument
Dawkins argues that the gene's sphere of influence — its phenotypic expression — does not stop at the boundary of the organism's body. Genes extend their effects outward into the environment: the beaver's dam, the caddisfly's case, even a parasite reshaping its host's shell are all phenotypic expressions of genetic information acting at a distance. This reframes the unit of selection debate: natural selection operates not just on bodies but on the entire causal chain a gene sets in motion, including the environments organisms construct and modify.
Critique
The extended phenotype framework risks becoming unfalsifiable by expansion: if any artifact or environmental modification can be recast as phenotypic expression, the concept loses predictive precision and becomes a powerful metaphor more than a testable mechanism. Critics from developmental systems theory argue Dawkins retains an overly gene-centric causality — treating genes as privileged initiating agents — while downplaying how developmental context, epigenetic factors, and reciprocal organism-environment feedback jointly constitute the phenotype. The framework's elegance may obscure the degree to which causality in complex systems is genuinely distributed and non-linear.
Why it matters for product
Product leaders tend to draw the system boundary at the product itself — its interface, its features, its codebase — but the extended phenotype concept surfaces a sharper question: what conditions is your product constructing in the environment it inhabits, and how do those conditions feed back to shape the selection pressures on the product itself? A platform that changes user behavior, recruits third-party developers, or restructures a market is expressing an extended phenotype; ignoring that causal reach means optimizing a local artifact while misunderstanding the system you are actually steering. This reframes strategy from 'what should the product do' to 'what environment is the product building, and does that environment select for the outcomes we want.'