El árbol del conocimiento
Source: https://archive.org/details/elrboldelconocim0000matu ↗
Autopoiesis — the idea that living systems produce and maintain themselves — explained for the general reader by the two biologists who coined the term.
Maturana and Varela argue that cognition is not computation but the living system's way of maintaining its own organisation, a claim that reframes what it means for a team to "learn" or an organisation to "adapt." It is not information processing; it is structural change.
This is the intellectual foundation of the enactivist tradition that connects to Clark, Thompson, and contemporary 4E cognition.
For product people the implication is radical: you cannot inject knowledge into a team the way you load data into a database — learning changes the learner, and the change is irreversible.
A short, visual, surprisingly accessible book that quietly undermines the computational metaphor most of the industry still runs on.
Central argument
Maturana and Varela argue that cognition is not the processing of external information but the activity by which a living system maintains its own organisation — what they call autopoiesis. Knowing is not representing the world accurately; it is a form of structural coupling between organism and environment that keeps the organism viable. This means that learning is not the accumulation of data but an irreversible structural change in the learner itself, which collapses the standard input-output model of mind and knowledge transfer.
Critique
The central tension is that autopoiesis, developed to explain cellular and biological self-organisation, is extended to cognition and social systems through analogy rather than strict derivation — a leap the authors make with elegance but not always with rigour. Critics, including Searle and various philosophers of mind, have pointed out that 'structural coupling' can explain adaptive behaviour without fully accounting for intentionality or the semantic content of thought. For product practitioners specifically, the framework's resistance to representationalism makes it difficult to operationalise: if you cannot speak of a team 'processing information,' the theory risks becoming explanatorily rich but practically inert.
Why it matters for product
If learning is irreversible structural change rather than information transfer, then onboarding, documentation, and knowledge-management systems built on the transmission metaphor — wikis, handbooks, training decks — are solving the wrong problem; what actually matters is the quality of the structural experiences you design for the team. For a CPO, this reframes organisational design: adding a new capability to a team is not a matter of hiring for a skill or running a workshop, but of engineering repeated, coupled interactions with real problems until the team's structure genuinely changes. It also has sharp implications for discovery — you cannot 'share insights' with stakeholders and expect alignment; the insight must be lived, not delivered.