Use Small and Slow Solutions

Transfers

Principle 9 of David Holmgren’s twelve permaculture design principles, “Use Small and Slow Solutions,” encodes a preference for interventions that are scaled small enough to observe and timed slow enough to self-correct. The principle emerges from the agricultural observation that a small, intensively managed garden outperforms a large, extensively managed field per unit of input — and that perennial systems that take years to establish eventually outperform annuals that produce quickly but deplete their substrate.

The principle operates as a cognitive heuristic in three ways:

• Scale to the span of oversight — a farmer can observe every plant in a small garden bed: noticing the first aphid outbreak, the first nutrient deficiency, the first drainage problem. In a hundred-acre monoculture, these signals are invisible until they reach crisis scale. The principle transfers to any domain where the operator’s ability to perceive feedback is the binding constraint. Small software releases, small organizational changes, and small policy pilots all preserve the operator’s capacity to see what is happening and adjust. The principle predicts that the optimal intervention size is determined not by the ambition of the goal but by the resolution of the feedback loop.
• Compound returns over long time horizons — a food forest planted today will produce little in its first year. In its fifth year it begins to yield. In its twentieth year it produces abundantly with minimal input, having built its own soil, its own microclimate, and its own pest-predator balance. The annual crop produces immediately but requires full replanting, full fertilization, and full pest management every year. The principle imports this lifecycle economics into decision-making: slow solutions that build self-sustaining infrastructure (knowledge bases, team culture, automated systems) eventually outperform fast solutions that require continuous reinvestment.
• Perturbation minimization — in complex adaptive systems, large interventions perturb many variables simultaneously, making it impossible to attribute outcomes to causes. A small intervention changes one thing, and the system’s response is interpretable. This is the agricultural version of the scientific principle of controlled experimentation, and it transfers to software deployment (canary releases, feature flags), organizational change (pilot programs before company-wide rollouts), and policy design (limited trials before national implementation).

Limits

• Urgency defeats patience — the principle has no structural accommodation for time pressure. Permaculture design assumes the designer has seasons and years to observe, iterate, and adjust. Many real-world situations demand action faster than slow solutions can deliver. A security vulnerability cannot be patched “small and slow.” A public health crisis cannot be addressed by pilot programs. The principle is worst as a guide precisely when the stakes are highest and the timeline is shortest.
• Some problems are structurally large — the principle implies that problems can always be decomposed into small pieces that are addressed sequentially. But some systems exhibit threshold effects: a bridge needs a minimum number of supports, a market needs a minimum number of participants, a vaccine campaign needs a minimum coverage percentage. Below the threshold, small interventions produce no effect at all. The permaculture assumption that “small accumulates into sufficient” does not hold for systems with discontinuous returns.
• Slow can mean too late — in agriculture, a garden that takes twenty years to mature is worthwhile because the land will still be there in twenty years. In competitive markets, technology, and politics, the landscape may be unrecognizably different in twenty years. The principle imports an assumption of environmental stability that is characteristic of permaculture’s land-based perspective but false for fast-moving domains. A company that builds its competitive advantage “small and slow” while a competitor scales rapidly may find that the slow solution, however elegant, arrives after the market has been captured.
• The principle can rationalize underinvestment — just as “do as much nothing as possible” can become an excuse for neglect, “use small and slow solutions” can become an excuse for inadequate resourcing. A leader who funds a pilot program at minimal scale, declares it a “small and slow solution,” and then under-resources subsequent phases is using the principle to justify chronic underinvestment rather than patient, adequate investment.

Expressions

• “Use small and slow solutions” — Holmgren’s original formulation from Permaculture: Principles and Pathways Beyond Sustainability (2002)
• “Start small, start now” — the activist compression of the principle, emphasizing that small scale enables immediate action
• “The bigger they are, the harder they fall” — folk proverb expressing the same preference for small scale, framed as risk avoidance
• “Ship small, ship often” — software development heuristic expressing the same principle as deployment strategy
• “Minimum viable product” — the lean startup concept that operationalizes the “small” half of the principle, though often without the “slow” patience the agricultural version implies
• “Slow is smooth, smooth is fast” — military and craft aphorism expressing the paradox that deliberate slowness produces better overall speed through fewer corrections

Origin Story

Holmgren articulated this principle in Permaculture: Principles and Pathways Beyond Sustainability (2002), drawing on E.F. Schumacher’s Small Is Beautiful (1973) and the appropriate technology movement’s critique of industrial-scale solutions. The agricultural grounding is in the contrast between industrial monoculture (large, fast, input-dependent, brittle) and permaculture polyculture (small, slow, self-sustaining, resilient).

The principle resonated beyond agriculture because it arrived at the same time as agile software development (the Agile Manifesto was published in 2001), lean startup methodology (Ries, 2008-2011), and iterative design thinking. These movements independently arrived at similar conclusions — small batches, fast feedback, iterative refinement — from different starting points. Holmgren’s contribution was grounding the insight in ecological first principles rather than business pragmatism: small and slow solutions work not because they are more efficient but because they align with how complex living systems actually develop.

References

• Holmgren, David. Permaculture: Principles and Pathways Beyond Sustainability. Holmgren Design Services, 2002
• Schumacher, E.F. Small Is Beautiful: Economics as if People Mattered. Blond & Briggs, 1973
• Meadows, Donella. Thinking in Systems: A Primer. Chelsea Green, 2008 — systems-theoretic parallel on intervention scale