Obtain a Yield

Transfers

“Obtain a yield” is Principle 3 of David Holmgren’s twelve permaculture design principles, published in Permaculture: Principles and Pathways Beyond Sustainability (2002). In its agricultural context, the principle is a corrective to permaculture’s own idealism: it is not enough to design a beautiful, self-sustaining ecosystem if that ecosystem does not feed anyone. A food forest that produces biodiversity but no edible harvest is an ecological success and a practical failure. The principle insists that every designed system must produce tangible, usable output — food, fiber, fuel, income — or it will not survive, because the people maintaining it will eventually redirect their labor to systems that do.

Key structural parallels:

• Yield as structural necessity, not reward. The deepest transfer is the distinction between yield as a bonus and yield as a precondition. In conventional thinking, output is the purpose of a system: you plant corn to harvest corn. In Holmgren’s framing, yield is not the purpose but the survival mechanism. A permaculture system has many purposes (building soil, cycling water, supporting biodiversity), but it cannot pursue any of them for long without producing something that sustains the humans who maintain it. This reframing transfers to organizations: a nonprofit that pursues its mission without generating enough revenue to retain staff will eventually collapse. An open-source project that does not yield enough contributor satisfaction (recognition, learning, career advancement) to sustain participation will be abandoned. The yield is not the point; the yield is what makes the point sustainable.

• Output vs. yield: the harvest problem. A garden that produces tomatoes no one picks has output but no yield. A fruit tree that ripens all its crop in one week when the household is on vacation has output but no yield. Holmgren’s principle distinguishes between what a system produces and what the operator can actually capture. This transfers to knowledge work: a team that produces excellent analyses that no one reads has output but no yield. A research program that generates insights that never reach practitioners has output but no yield. The cognitive move is to shift design attention from “what does this system produce?” to “what can the operator actually use, and when?”

• Stacking functions for cascading yield. Permaculture design arranges elements so that each produces multiple yields and each yield becomes an input for another element. A chicken produces eggs (food yield), manure (fertility yield), pest control (garden yield), and heat (greenhouse yield). The principle of stacking functions transfers to organizational design: a well-designed onboarding process yields a productive employee (labor), documentation improvements (knowledge capture), mentorship experience for the trainer (skill development), and cultural transmission (organizational resilience). Designing for multiple yields from a single investment is a fundamentally different optimization than maximizing a single output.

Limits

• The yield trap: premature extraction. The principle can be misused to demand returns before a system has matured. In agriculture, a food forest needs three to seven years of establishment before it produces meaningful harvests. Demanding yield in year one means pulling up the trees and planting annual crops, which produces immediate output at the cost of the long-term system. This is precisely the pattern the principle is meant to prevent, but its imperative phrasing (“obtain a yield”) lends itself to impatient application. In organizations, the equivalent is demanding quarterly results from a research team, immediate ROI from a training program, or visible output from a culture-change initiative. The principle provides no guidance on how long to invest before expecting returns.

• Not all valuable outputs are measurable yields. Holmgren’s examples are deliberately tangible: food, fuel, fiber, income. But in knowledge work, education, and community organizing, the most important system outputs — trust, shared understanding, cultural resilience, institutional knowledge — resist quantification. When “obtain a yield” is applied to these domains, it creates pressure to identify measurable proxy metrics (test scores for learning, engagement metrics for community, lines of code for development), and the proxy becomes the target, displacing the actual value. Goodhart’s Law is the shadow of “obtain a yield” in domains where the real yield cannot be weighed.

• It assumes a single operator perspective. The question “does this system yield?” depends entirely on who is asking. A wetland yields flood protection to the downstream community, habitat to wildlife, and water filtration to the watershed — but yields nothing marketable to the landowner. The principle’s imperative to obtain a yield can be used to justify draining the wetland (which yields no private return) and planting corn (which does), destroying the larger system yields in pursuit of the narrower private one. The principle does not specify whose yield counts.

Expressions

• “Obtain a yield” — Holmgren’s canonical formulation, Principle 3 of the twelve permaculture design principles
• “You can’t work on an empty stomach” — the folk version, emphasizing that idealism without sustenance is unsustainable
• “Ensure that you are getting truly useful rewards as part of the work that you are doing” — Holmgren’s explanatory gloss
• “Stack functions” — the permaculture design imperative to make each element serve multiple purposes, directly related to maximizing yield per unit of investment
• “If it doesn’t produce, it doesn’t stay” — harsher practitioner variant used in permaculture garden design

Origin Story

David Holmgren, co-originator of the permaculture concept with Bill Mollison, published his twelve design principles in 2002 as a systematic framework for ecological design. “Obtain a yield” is positioned as Principle 3 — after “observe and interact” and “catch and store energy” — because Holmgren recognized that permaculture’s idealistic reputation was a practical vulnerability. Critics dismissed permaculture as impractical utopianism, and some practitioners built elaborate systems that produced biodiversity and soil health but not enough food to justify the labor. Principle 3 is Holmgren’s answer: a system that does not feed its maintainers will not be maintained, no matter how ecologically elegant it is.

The principle’s deeper agricultural root is the peasant farmer’s pragmatism. Subsistence agriculture, which permaculture draws on extensively, has always understood that yield is not optional. The innovation in Holmgren’s formulation is applying this ancient constraint to modern design: sustainability without productivity is a luxury that only well-funded demonstration projects can afford.

References

• Holmgren, D. Permaculture: Principles and Pathways Beyond Sustainability (Holmgren Design Services, 2002) — source of the twelve design principles
• Mollison, B. Permaculture: A Designer’s Manual (Tagari, 1988) — foundational permaculture text
• Hemenway, T. Gaia’s Garden: A Guide to Home-Scale Permaculture (2009) — accessible introduction to permaculture design principles including yield optimization