Subject

Tech Village Development

Tech village development is the work of establishing a settlement where a group of households support themselves with technology they own and can maintain, and it's a human project far more than a technical one.

Almost every attempt that fails does so on people, money or governance, and almost none of them fail on engineering.

The engineering is not what kills these

Intentional communities and self-sufficient settlements have been attempted continuously for centuries, and there's a large body of evidence about what happens to them. The consistent finding is uncomfortable for anyone approaching it as a technical problem: they very rarely fail because the water system didn't work.

They fail because the founding group never agreed what they were actually doing. Because decisions had no settled process and the disagreements accumulated. Because the money ran out at a predictable point nobody had planned for. Because the work fell unevenly and resentment followed. Because someone left and their share of an undocumented arrangement went with them.

Which means the preparation that matters is the part that feels least like progress: writing down what everyone expects, deciding how decisions get made, and being explicit about money before there is any. The people who skip that because they're keen to start building are the ones who most reliably don't finish.

There's a real prize on the other side. A group at this scale can do what no household can, and the historical village is proof of concept rather than nostalgia. But the route to it runs through the boring part.

The people question, which comes before everything

Who's involved and what they actually agree on determines the outcome more than any other factor.

Get the purpose written down and specific. A group can agree enthusiastically on self-sufficiency and discover, three years in, that some meant an income-sharing commune, some meant neighbours with a shared workshop, and some meant somewhere quiet with a garden. Those are different projects. Writing it down is what surfaces the difference while it's still cheap.

Be explicit about the range of commitment. Full-time residents, part-time, weekenders and investors all want different things and contribute differently, and a structure that pretends they're the same generates the resentment that ends projects.

Skills matter and complementarity matters more. A group where everyone is a builder has one capability and several gaps, and the gaps that most often go unfilled are the administrative and financial ones because they're the least appealing.

And plan for people leaving, at the very start. Circumstances change and someone will go. How their contribution is valued, how they exit, and what happens to their share are questions that are straightforward to settle in advance and destructive to settle in a dispute.

Money, and the gap that catches everyone

The financial pattern is consistent enough to predict, which means it can be planned for.

Capital goes out first and heavily: land, access, water, power, buildings, equipment. Income arrives late, is modest at first, and takes longer to build than anyone expects. The gap between those two is where projects fail, and it's entirely foreseeable.

So the plan needs an answer for how people live during it. Outside income, savings, staged development that keeps costs low while things establish, or phasing so that something earns early. A project that assumes it will be self-supporting quickly is a project that will meet the gap without a plan.

Be clear about who pays for what and what that buys. Contributions of money and contributions of labour both need valuing, and the mismatch between someone who put in capital and someone who put in years is one of the most common sources of serious dispute.

Build in reserves. Something will cost more, take longer or fail, and a project with no margin turns an ordinary setback into an exit.

And distinguish the settlement's finances from the households' finances. Blurring them makes both harder to manage and makes leaving nearly impossible to arrange fairly.

How decisions get made

Governance is what a group has instead of an owner, and having none is itself a choice with predictable results.

Decide the decision method explicitly and in advance. Consensus preserves relationships and can be paralysed by one determined objector. Majority voting is decisive and leaves minorities carrying decisions they opposed. Delegated authority is efficient and needs trust and accountability. Most durable arrangements use different methods for different weights of decision, with the big irreversible ones needing more agreement than the daily ones.

Write down who can decide what without asking. Ambiguity about authority produces both paralysis and unilateral action, frequently in the same group.

Have a process for disagreement before you have a disagreement. Every long-lived community has one, and the ones that fail typically had no route between informal grumbling and someone leaving.

Review deliberately. Rules written by a founding group in its first year rarely suit the same place a decade later, and a settled way to change the rules is what stops people working around them instead.

The order of the work

Sequence decides how far a project gets before the money or the patience runs out.

Water first, then access, then somewhere to live, then the productive infrastructure, then the shared facilities. That order is about what everything else depends on, and it's routinely inverted by groups who start with the most exciting thing.

Start smaller than planned. A phase that's finished and working sustains momentum, teaches you what you actually need, and produces something to build the next phase from. A grand plan half-built is demoralising and frequently unrecoverable.

Plan the temporary properly. People will live in something interim for longer than intended, and making that decent, not merely endurable protects the goodwill the whole project runs on.

Leave room for what you haven't thought of. Layouts, structures and agreements that assume today's arrangement fight every future change, and every one of these projects changes.

Why these usually fail, plainly

This is the section worth reading before committing anything, because the failure modes are consistent and mostly avoidable.

Unclear purpose, where people discover years in that they joined different projects.

No agreed decision process, so that disagreement has nowhere to go and accumulates until it ends the thing.

Money, and specifically the capital-first income-later gap that nobody budgeted for.

Uneven contribution and no mechanism to address it, which produces resentment that is very hard to reverse once established.

Founder dependency, where one person holds the vision, the knowledge and the authority, and the project cannot survive their departure or their exhaustion.

And isolation, both from the surrounding community, which makes practical life harder than it needs to be, and socially, which is a real cost people consistently underestimate.

None of that is an argument against doing it. It's an argument for spending the first year on the agreements in place of the earthworks.

Or tell us what you need

This form isn't accepting submissions yet.

Questions

What is the most common reason these projects fail?
People and process, not engineering. Most commonly an unclear founding purpose that people discover they disagreed about years later, no settled way of making decisions so disagreement accumulates with nowhere to go, and the gap between capital going out early and income arriving late. Water systems and buildings are rarely what ends them.
How should the land be owned?
That depends on your country and on what you're trying to protect, and the choice is between individual ownership with shared use rights, a company or cooperative, a trust, or a partnership. The useful test for any of them is what happens in the awkward cases: someone leaves, someone dies, someone stops contributing, or a majority wants to sell. Get it drafted professionally, because this is cheap advice relative to the cost of getting it wrong.
How many people does it take?
Enough to justify shared infrastructure and cover the range of skills, and few enough to make decisions without formal machinery. Historically the effective unit is a few dozen households instead of a handful or a hundred. Too small and the shared equipment can't be justified; too large and informal agreement stops working and has to be replaced with something more structured.
Should we buy land first?
Usually not. Establish the group, the purpose, the legal structure and the decision process first, and find out what planning rules would allow before committing capital. Buying land with an unformed group is how projects end up with an asset they cannot agree what to do with, and planning constraints have made otherwise sound plans impossible on land already bought.
More questions, and every other subject, in the FAQ.

The library is how this gets written

The Ark is a library of practical knowledge that was ordinary once and isn't any more, being recovered from the sources that recorded it while it was still in use. Membership is what pays for that work, and it's what decides how fast subjects like this one get written.

See what membership includes

The Ark of Forgotten Knowledge Podcast

0:000:00