Intentional communities are built on a wager that Hardin treated as naïve: that people who choose to share land, kitchens, tools, and labour can escape the logic that ruins open-access resources. Sometimes they can. Often they cannot. The difference is rarely ideology. It is whether the community treats shared resources as an unmanaged commons or as a planned system with visible work, bounded capacity, and feedback.
What the tragedy of the commons actually claims
The tragedy of the commons is not a claim that people are wicked. It is a claim about incentives. When a resource is shared, each person captures most of the private gain from taking a little more and pays only a fraction of the cost. Add one extra cow, skip one kitchen shift, leave the irrigation valve open, harvest the ripe tomatoes before the work day starts. Individually rational acts compound into collective depletion.
William Forster Lloyd described the mechanism in 1833 with common English pasture: cattle on the commons were “puny and stunted” because a herder who added animals to common land took most of the benefit and socialised the damage. Garrett Hardin named the pattern in 1968 and applied it to population, pollution, and any “freedom of the commons.” His famous line was not poetry. It was a systems claim: “Each man is locked into a system that compels him to increase his herd without limit—in a world that is limited.”
Two corrections matter before the idea is imported into community life.
First, Hardin described an unmanaged open-access system: anonymous users, no communication, no property rules, no monitoring. He later said he should have called it the tragedy of the unmanaged commons. Most historical commons were not free-for-alls.
Second, Elinor Ostrom showed that users often govern shared resources without privatising them or handing them to the state. Long-lived commons tend to have clear boundaries, rules that fit local conditions, participation in rule-making, monitoring, graduated sanctions, cheap conflict resolution, and external recognition of the right to self-organise.
The tragedy is therefore not destiny. It is what happens when a shared resource has rivalry (one person’s use reduces what others can use) and weak institutions. Intentional communities are full of such resources.
How the tragedy appears inside communities that “share everything”
A commune, eco-village, cohousing cluster, or land trust is a nest of common-pool resources: land, water, buildings, tools, vehicles, food stores, labour time, attention, and trust. The last of these is the scarcest.
The pattern is familiar to anyone who has lived in a shared house. Dishes migrate to the sink. The person who cares most becomes the unpaid janitor. Food labelled “community” disappears first. Tools leave the shed and do not return. Garden beds nearest the path get harvested; distant beds get weeds. Meetings expand because talking is visible and weeding is not. The conscientious burn out. The rest feel policed. Resentment replaces solidarity. Researchers have called the household version of this the “tragedy of the commune”: each roommate prefers that someone else clean, so the house decays even though everyone would prefer a clean house.
Scale makes it worse. Hardin himself used Hutterite colonies — religious communities organised on a “from each according to ability, to each according to need” principle — to show a scale effect. Below roughly 150 people, shame and face-to-face knowledge can keep contribution and consumption in line. Above that, under-contribution and over-demanding grow. Even a devout group cannot rely on virtue once numbers dissolve accountability.
Food-growing land is an especially sharp case. Soil fertility, irrigation water, compost, seed, and harvest are rival goods. If planting, weeding, and watering are “everyone’s job,” they become no one’s job. If harvest is open to all regardless of hours worked, the community recreates Lloyd’s pasture: the private plate fills first; the common bed is mined. Over a season the visible result is patchy beds, bolted crops, and a quiet split between those who treat the garden as a commons and those who treat it as a pantry.
Labour is the other commons. Time is finite. A community that does not budget labour will discover that charismatic projects (festivals, new buildings, “vision work”) consume the hours that should have gone to drains, accounts, and winter cover crops. This is not a failure of love. It is a failure to treat work as a scarce resource.
The critical point is uncomfortable for movements that treat structure as a capitalist residue. Unstructured sharing does not abolish self-interest. It hides it until the resource, or the relationship, is already damaged.
What large organisations actually do instead of hoping
Private-sector planning is not morally superior. Firms waste resources too. What they cannot afford, at least for long, is an invisible workload and an unowned asset. The methods that matter for communities are not stock options or hierarchy for its own sake. They are visibility, capacity limits, short feedback loops, and named ownership.
Agile and Scrum are one family of those methods. They were built for software teams, but their useful core is simple:
- Work is made explicit in a backlog, not left as a vibe.
- Only as much work is pulled into a short cycle (a sprint) as the group can actually finish.
- Someone is accountable for priorities (a product owner analogue) and someone protects the process (a scrum master analogue).
- The team inspects progress in the open and adapts.
- “Done” is defined in advance, so half-finished beds and “I’ll get to the compost later” do not count as completion.
Farms have already borrowed this. Growers use user stories (“as a kitchen cook I need a predictable weekly harvest”), a board with backlog / doing / done, and short cycles so the season is not one giant unmanageable project. Colour-coded assignment shows who owns which task in the current window.
Cohousing and co-living groups use the same visual logic without calling it Scrum: Kanban or “community mastery” boards that list recurring duties, who is home this week, and what is committed before the next meeting. The point is not the brand. The point is that work stops being a rumour.
Twin Oaks, a long-running income-sharing community in Virginia, built a more industrial version decades before Agile vocabulary arrived. Members owe a weekly labour quota (about 38.5 hours). One hour of approved work equals one credit. Area managers hold labour budgets. Members file preferences; assigners fill shifts; sheets are turned in. Kitchen cleaning is a required shift; most other work is chosen within the budget. Credits are not cash, but they are accounted for. The clerical burden is real. So is the reason it exists: equality and flexibility depend on tracking, not on assuming that goodwill will allocate weeding, milking, and bookkeeping by magic.
That is private-sector resource planning in communal clothing: capacity, budgets, assignment, and audit.
Shared duties: treat chores as a backlog, not a moral test
A community kitchen, laundry, tool library, or common house is a classic common-pool system. The efficient response is not a sermon about helping out. It is a work system with four properties.
1. Name the work and its size.
“Keep the place nice” is not a task. “Clean the common kitchen to the posted standard by 10 p.m., 45 minutes, two people” is a task. Cohousing software such as Gather does this explicitly: jobs are entered with hours, members sign up, quotas can be computed from total hours needed, and accommodations can be granted without pretending everyone has identical capacity. Touchstone Cohousing has used such a system with high participation and hundreds of shared hours per month.
2. Pull work against capacity, in short cycles.
A weekly sprint for domestic life looks prosaic and works. Sunday planning: what must be done this week (meals, cleaning zones, childcare cover, vehicle maintenance, accounts)? Who is actually present? What is each person’s available hours after paid work, illness, and care duties? Nothing extra enters the week unless something leaves. This is Scrum’s sprint planning minus the jargon.
3. Make ownership visible.
A board — whiteboard, magnets, or a shared digital column — with To do / Doing / Done ends the cleaners’ dilemma in which everyone waits to see whether someone else will move first. Wolf Creek Lodge’s team model (landscape, meals, maintenance, clean teams assigned to zones) is the same idea at a coarser grain: membership in a team replaces the fiction that “the community” will do it.
4. Inspect and adjust, with graduated consequences.
A 15-minute weekly standup (“what I finished, what I own next, what is blocked”) plus a monthly retrospective (“which duties are chronically uncovered?”) is cheaper than a grievance circle after six months of silent scorekeeping. Ostrom’s monitoring and graduated sanctions belong here. First reminder, then a make-up shift, then loss of some privilege of the commons (priority harvest, guest meals, vehicle use), then — if the person will not meet the membership bargain — exit. Communities that refuse all sanctions do not become kinder. They become places where the reliable subsidise the unreliable until the reliable leave.
The private-sector analogue is not cruelty. It is WIP limits and definition of done. A team that allows unlimited unfinished work will ship nothing. A community that allows unlimited unfinished care work will live in a mess and call it freedom.
Allocating land for food: plan the field the way a firm plans a portfolio
Shared growing land fails in two opposite ways. Open-access harvest recreates overgrazing. Total privatisation of plots can destroy the economies of shared irrigation, fencing, compost, and crop rotation. The workable middle is bounded plots plus shared infrastructure, planned on a seasonal cadence.
A practical design, using organisational methods rather than slogans:
Define the resource and the users.
Which acres are food land? Who has rights this season? Visitors do not get the same draw on harvest as members who met quota. That is Ostrom’s first principle, not exclusion for its own sake.
Separate the portfolio.
- Community staple beds: potatoes, beans, storage crops, managed as a single product with a named “product owner” (garden manager) and a labour budget.
- Household or small-group plots: clearly marked, sized to the labour the holders will actually supply.
- Experimental beds: small, time-boxed, killed at season’s end if they fail.
- Commons infrastructure: water lines, compost, tool shed, greenhouse schedule — booked like a shared conference room.
Build a seasonal backlog, then sprint.
Winter planning is portfolio planning: crop mix, succession dates, labour hours by month, water budget. The growing season is a sequence of two-week sprints: bed prep, transplant, trellis, weed, harvest, preserve. Each sprint has a board. “Plant the east bed” is not done until it meets the definition of done (mulched, labelled, irrigation checked, hours logged). Farms using Scrum already work this way because weather does not care about consensus process.
Match benefits to contribution.
A member who put in the weeding hours should not lose the ripe fruit to someone who treated the garden as a supermarket. That can mean: community crops go to the common kitchen in proportion to labour credits; plot holders keep their own plot harvest; a small open-glean window after the working members have taken their share. Twin Oaks-style credits make this bookkeeping possible without turning every carrot into a cash transaction.
Monitor the land, not just the people.
Soil tests, moisture readings, yield logs, and a walk-through at the end of each sprint are the community’s equivalent of a burn-down chart. If beans fail in bed 4, the retrospective asks whether the rule (spacing, water turns, who owns that bed) was wrong — not only who is to blame.
This is how a large organisation allocates scarce plant, people, and calendar time: portfolio, capacity, owners, cadence, review. A five-acre food commons that refuses those tools is not more spiritual. It is under-managed.
The critique: Scrum will not save a community that will not name the bargain
Importing Agile into an intentional community can fail in predictable ways.
It can become cargo-cult process: standups without decisions, boards that no one updates, retrospectives that produce more values statements. Software teams know this disease well.
It can clash with the community’s self-image. People join eco-villages to escape timesheets. A labour quota feels like the world they left. If the method is imposed rather than chosen (Ostrom’s collective-choice principle), it will be sabotaged with a smile.
It can ignore care work and unequal capacity. A raw hours quota treats a parent, an elder, and a healthy childless adult as identical production units. Twin Oaks at least builds in pension credits and childcare credits; a crude Scrum board will not.
It can substitute velocity for judgment. Not everything that matters is a ticket. Grief, political conflict, and the slow work of teaching a new member how to irrigate without wasting water do not fit a two-week increment. Treating them as “blockers” is a category error.
And Hardin’s original essay carried a harsher politics — “mutual coercion mutually agreed upon,” especially around population — that communities should not swallow whole. The useful residue is narrower: unmanaged rivalry plus weak feedback ruins shared goods. The remedy is institutions, not a single methodology brand.
Ostrom still describes the skeleton. Agile and Scrum are a modern skin: they make monitoring cheap, rules revisable, and work visible. Private firms use them because hidden work and unbounded demand bankrupt projects. Communities that share land and duties face the same arithmetic. They can reject the vocabulary. They cannot reject the constraint.
The tragedy of the commons is what you get when sharing is an ethic without an operating system. Intentional communities that last treat food land, kitchens, and labour the way a competent organisation treats plant and payroll: bounded, planned in public, adjusted in short cycles, and tied to a membership deal people can see. That is not the death of common life. It is how common life survives contact with harvest season.