If you want to understand integrate rather than segregate permaculture, start with one shift in perspective: good design is not about collecting more parts. It is about arranging relationships so the parts support one another. In permaculture, that means looking at what an element needs, what it produces, when it acts, and where it sits in relation to the rest of the system. David Holmgren frames this principle around the importance of connections and around placing elements so each serves the needs and accepts the products of other elements.
What Integrate Rather Than Segregate Permaculture Means
“Integrate rather than segregate” is one of Holmgren’s twelve permaculture design principles. At the simplest level, it asks you to stop seeing a garden, homestead, or landscape as a pile of separate objects. A fruit tree is not just a fruit tree. A path is not just a path. A chicken coop is not only a coop. Each part has needs, creates outputs, and changes the options around it.
From OMF’s point of view, the practical lesson is simple. Place things where they can do useful work for each other. That might mean a tree that provides shade where heat is a problem, flowers that feed beneficial insects near crops that need pollination, or a path that improves access and observation. The principle is not asking you to cram everything together. It is asking you to design relationships on purpose.
That distinction matters. Simply mixing many elements in one place can create competition, confusion, and extra labor. Integration only works when the relationship is functional. Proximity alone is not enough. The connection has to do something useful.
Why This Principle Matters in Design
Systems work through relationships
Permaculture has many visible parts, but systems behave through relationships. Water moves downhill. Shade changes temperature. Roots change soil structure. Flowering plants can feed insects that later help with pollination or influence pest pressure. A fence changes animal movement. One well-placed element can affect far more than its own footprint.
That is one reason isolated optimization often falls short. You can maximize one bed, one crop, or one structure and still end up with a weaker whole. Designs that hold up over time usually pay attention to flows: fertility, water, labor, access, habitat, shelter, and timing. Official agroecology and agroforestry guidance uses similar logic. One part of the system can become a resource or service for another.
For beginners, this changes the core design question. Instead of asking, “What should I add next?” ask, “What relationship am I trying to create?” That shift moves design away from collection and toward function.
Stacked functions and redundancy
Holmgren ties this principle to two linked rules. Each element should perform many functions, and each important function should be supported by many elements.
Those rules explain why integration matters. A single tree can produce fruit, cast shade, shelter soil, slow wind, host insects, and change conditions around nearby plants. At the same time, if pollination, mulch, wind protection, or fertility depend on only one fragile link, the system becomes brittle. Redundancy gives you backup. Multifunction gives each element more value.
This is where many beginner designs improve quickly. They stop asking each element to do one isolated job. They also stop depending on one element to solve everything. Integration is the middle ground between clutter and over-specialization.
Integration vs. Segregation
Segregation is not always bad. It can simplify management. Straight rows, separate beds, isolated functions, and clearly divided zones are often easier to understand and maintain, especially at the start. That clarity has real value.
Permaculture still leans toward integration because the whole system often benefits when relationships are intentional. Waste can become an input. Shelter can support production. Habitat can support pest management. One placement decision can solve several problems at once.
The tradeoff is complexity. An integrated system usually asks more from the designer and the manager. You need to observe timing, competition, access, and maintenance. You also need to accept that not every relationship will pay off equally in every climate, soil, or landscape. Research on diversified systems supports many benefits, but it also shows that results vary with context.
That is why OMF treats integrate rather than segregate permaculture as a design discipline, not a slogan. Separate parts when separation genuinely makes the system work better. Integrate parts when the relationship improves the performance of the whole.
Practical Examples of Integration in Permaculture
Plants that support other plants
Companion planting is one of the easiest ways to see this principle in action. The useful version is not folklore or random pairing. It is a design choice where one plant helps create conditions another plant can use. University of Minnesota Extension notes that companion planting can make efficient use of space and, in some cases, support soil health or weed management.
A beginner example is pairing plants with different canopy shapes, root depths, or growth timing so they do not compete in the same way for the same resource at the same moment. Another is using living cover around a crop to protect soil and reduce bare ground. The point is not to memorize a magic chart. The point is to ask whether the pairing creates a real function.
Flowers and habitat for beneficial insects
Many beneficial insects need nectar, pollen, or shelter for at least part of their life cycle. If your productive plants offer food only for a short window, nearby flowering habitat can fill the gap. Michigan State University Extension notes that supporting beneficial insects can aid pest suppression and pollination.
This is a clear example of integration because the flowering border is no longer decorative alone. It becomes part of the working system. It feeds useful insects, increases habitat, and can make the growing area more biologically active. That does not guarantee a pest-free garden. It does create a more functional relationship between habitat and production.
Trees, shrubs, and windbreak roles
Trees and shrubs often show stacked function better than almost anything else. USDA defines agroforestry as the intentional integration of trees and shrubs into crop and animal systems, and that definition is useful here because it highlights deliberate placement for multiple outcomes.
A windbreak is a simple case. Properly placed trees or shrubs can reduce wind exposure, protect soil, create shelter, provide habitat, and sometimes produce food, fuel, or craft material depending on the species and context.
The caution matters as much as the promise. Tree-based systems can take time to mature. They can also complicate management if spacing, shade, root competition, or maintenance are poorly planned. Integration is not a free bonus. It is a longer design commitment.
Crop and livestock relationships
FAO describes crop-livestock integration in terms of one system’s products or by-products becoming resources for the other. That is a useful beginner frame because it makes the relationship visible.
Manure can support fertility. Crop residues can become feed or bedding. Managed animal movement can shape vegetation. In permaculture terms, this is the principle at work because the output of one element is not treated as waste by default. It becomes part of a loop.
This kind of integration also makes the tradeoffs obvious. Animal systems add labor, infrastructure, timing demands, and management risk. They only improve the whole when the relationship is well matched to the site and to the people running it.
Where Integration Goes Wrong
The most common mistake is adding complexity without a function map. More beds, more species, more structures, and more animals can look impressive while making the system harder to manage. If the elements do not actually support one another, the result is clutter, not integration.
A second mistake is confusing diversity with performance. Diverse systems often have real ecological advantages, and research shows that diversified farming can increase the abundance and richness of beneficial arthropods in many settings. Still, those outcomes depend on local conditions and landscape context. More diversity does not automatically create a better design.
Another failure mode is ignoring time. A relationship that looks good on paper may not work in year one, or it may work only after trees mature, soil improves, or management routines settle in. Some integrations produce delayed returns. Others create short-term headaches before long-term gains become visible.
Competition is another issue. Two elements can be near each other and still fight for light, water, nutrients, or access. That is why correct placement matters so much in permaculture literature. The goal is not closeness for its own sake. The goal is a useful relationship with tolerable costs.
A Simple Test for Better Integration
When OMF looks at this principle in practical terms, four questions do most of the work:
- What does this element need?
- What does this element produce?
- Which nearby element can use either one?
- Does that relationship reduce waste, labor, or fragility without creating a bigger problem?
That last question matters because every relationship has a cost. One pairing may save water but complicate harvest. In another case, a windbreak may protect crops but increase shade where you do not want it. Elsewhere, a flowering strip may support beneficial insects but take space from another use. The point is to judge the relationship by whole-system function, not by whether it sounds elegant.
Beginners usually do better when they start small. Build one or two clear relationships first. Watch them through a season. Then decide whether the integration actually earned its place.
Frequently Asked Questions
Does integration mean everything should be planted together?
No. Functional integration is not the same as forced proximity. Permaculture sources stress relationship and placement, not crowding. Sometimes the best design move is to keep elements separate so they are easier to manage or so they do not compete too hard.
Is integration always better than separation?
No. Separation can improve clarity, access, sanitation, timing, or maintenance. Integrated systems can offer broader whole-system benefits, but they can also demand more observation and management. The right choice depends on the site, the goal, and the people maintaining the system.
Does this principle guarantee higher yields?
No. A well-integrated system can support multiple functions and may improve resilience or ecological performance, but research shows that outcomes vary by context. It is safer to think in terms of whole-system function than guaranteed output from one crop.
How can beginners apply this principle without making things too complicated?
Start with one simple relationship at a time. Pair a flowering strip with crops that benefit from pollinators. Use a mulch source near beds that need it. Place a frequently used herb near a path or doorway. Choose relationships you can observe easily and manage without adding a new layer of chaos.
Final Takeaway
Integrate rather than segregate permaculture is a reminder to design relationships, not just collect elements. Good integration happens when one part of the system helps another in a clear, useful, manageable way. Bad integration happens when parts are merely close together and the costs are ignored.
Do not ask whether your design looks diverse. Ask whether the relationships actually work.