Embedded Files
Design Is Not Planning (and This Is Where Most Fail)
Design Is Not Planning (and This Is Where Most Fail)
Many permaculture designs fail because they confuse planning with design.
Many permaculture designs fail because they confuse planning with design.
Planning focuses on what you want
Design focuses on what the site will tolerate
Examples of planning (not design):
Examples of planning (not design):
“I want a food forest here.”
“I want to be off-grid.”
“I want to capture all rainfall.”
Examples of design questions:
Examples of design questions:
What is the maintenance load at this scale?
What happens if this system fails mid-season?
Who bears liability if this causes damage?
Design begins when constraints are acknowledged — not when ideas are generated.
What Permaculture Design Actually Is
What Permaculture Design Actually Is
Permaculture design is not a set of layouts, patterns, or aesthetic choices.
Permaculture design is not a set of layouts, patterns, or aesthetic choices.
At its core, permaculture design is the process of aligning human intent with ecological constraints while minimizing irreversible error.
A valid design answers three questions before it answers “what should I build?”:
What is the true scale of impact?
How difficult is this to undo if it fails?
What external systems does this interact with (law, neighbors, insurance, safety)?
If those questions are undefined, the design is incomplete — no matter how elegant it looks on paper.
Permaculture design is often presented as a creative or intuitive process.
Permaculture design is often presented as a creative or intuitive process.
In reality, design validity is not determined by creativity, ethics, or intent alone.
In reality, design validity is not determined by creativity, ethics, or intent alone.
A design is only valid if it survives the structural constraints imposed by the site, the scale of impact, and the permanence of the action. Most failed permaculture projects do not fail because the idea was bad — they fail because these constraints were never evaluated before implementation.
The purpose of this framework is not to restrict design, but to prevent irreversible error. Permaculture does not fail at the idea level — it fails at the decision level. By evaluating designs through deterministic constraints instead of assumptions, this system shifts permaculture from aspirational planning toward verifiable, site-specific accountability.
In permaculture, design ideas are not assumed valid by default. This diagram shows the required decision gates a design must pass—scale, reversibility, and governance—before it can be responsibly implemented.
The Three Design Governors
The Three Design Governors
Every permaculture design is governed by three non-negotiable realities.
Every permaculture design is governed by three non-negotiable realities.
Ignoring any one of them produces failure elsewhere.
1. Scale of Impact
1. Scale of Impact
Scale determines:
energy flows
maintenance burden
failure blast radius
A design that works at garden scale may collapse at homestead or community scale.
Good design reduces scale until stability is proven.
2. Permanence (Reversibility)
2. Permanence (Reversibility)
Every design choice has a reversal cost.
Fully reversible systems allow learning
Partially reversible systems require caution
Permanent systems require certainty
Design does not ask “can this be built?”
It asks “can this be safely undone?”
3. Governance & External Constraints
3. Governance & External Constraints
No design exists in isolation.
Design interacts with:
zoning and land-use law
HOAs and covenants
neighbors and shared infrastructure
insurance and liability
safety and emergency response
A design that ignores governance does not become independent — it becomes vulnerable.
Why “Good Design” Still Fails
Why “Good Design” Still Fails
Permaculture designs fail even when they follow:
Permaculture designs fail even when they follow:
accepted principles
common zone layouts
proven techniques
Common failure modes include:
underestimating maintenance energy
assuming future behavior will match intent
ignoring off-site consequences
treating permanence as neutral
Failure is not a moral issue.
It is a systems mismatch.
Design exists to surface mismatch before implementation.
Design Knowledge You Can Actually Use
Design Knowledge You Can Actually Use
Once constraints are defined, design knowledge becomes actionable.
Once constraints are defined, design knowledge becomes actionable.
Below are design concepts that only work after context is validated:
Zones
Zones
Zones describe frequency of interaction, not success.
They help place elements once scale and access are known.
Sectors
Sectors
Sectors model external forces (sun, wind, water, fire).
They matter most when permanence increases.
Guilds
Guilds
Guilds reduce inputs only when maintenance energy is accounted for.
Poorly designed guilds increase complexity without resilience.
Stacking Functions
Stacking Functions
Stacking works when functions are compatible over time, not just space.
These tools are powerful — but only inside defined boundaries.
Design Without Assumptions (Important)
Design Without Assumptions (Important)
This page intentionally does not tell you what to build.
This page intentionally does not tell you what to build.
That is not an omission.
It is a safeguard.
Design decisions made without verified context produce:
sunk costs
regulatory conflict
ecological damage
long-term maintenance traps
Before committing to a design, your site context must be classified.
Start With Classification
Start With Classification
Before designing, validate your site reality.
Before designing, validate your site reality.
Use the Decision Router to determine whether a project should:
proceed
pause
or be refused in its current form
This step protects both the site and the designer.
Where to Go Next
Where to Go Next
If you’re still learning:
If you’re still learning:
Permaculture Systems – understand interacting components
Permaculture Zones – spatial logic and limits
If you’re preparing to act:
If you’re preparing to act:
Use validated tools only after classification
Do not bypass governance or permanence constraints
Permaculture design is a responsibility, not a recommendation.
This site prioritizes decision validity over outcomes.
Page updated
Google Sites
Report abuse