Community Governance Models

The reason this concept belongs in the Law 3 encyclopedia is not because governance is a civic virtue to be admired from a distance. It's because the specific mechanics of how a community makes decisions determines whether that community is capable of doing what communities are supposed to do — hold people through hard things, make collective resources work, survive conflict, and improve over time.

Every failed intentional community, collapsed housing cooperative, or imploded neighborhood organization I've ever studied had one thing in common: the governance was never built. The founders started with shared values, abundant enthusiasm, and no working answer to the question "who decides, and how?" When the first real conflict arrived — the one that required a decision that couldn't make everyone happy — there was no structure to hold the weight of it. The community fractured because it had no skeleton.

Understanding the spectrum

Community governance exists on two axes. The first is centralization — how concentrated decision-making authority is. The second is formalization — how explicit and structured the process is.

Most communities start low on both axes: informal and decentralized, which is to say "figuring it out as we go with whoever is present." This works for small groups in the honeymoon phase. It reliably fails when the group grows, when resources become significant, when real conflict emerges, or when the founding members need to hand off responsibility to others. The transition from informal to formal governance is one of the most fraught moments in a community's life, and most communities handle it badly — either too late, under crisis conditions, or in ways that entrench the power of whoever was already running things informally.

The major models in depth

Representative democracy is what most communities default to when they try to formalize. You elect a board, a council, a committee. That body has authority over defined domains. Members participate periodically through elections and sometimes referendums. The advantages are familiarity, scalability, and clear accountability — you can vote people out. The disadvantages are structural.

First: elections favor certain types of people — those with time, those who are comfortable with self-promotion, those who already have networks within the community. The result is governance bodies that are demographically narrower than the community and systematically underrepresent the people with the least institutional power. This is not an accident. It's the mechanism.

Second: as governance becomes more formalized, the governing class professionalized. They develop their own perspective, their own relationships with each other, and eventually a mild interest in maintaining their own governance role. The community becomes something they manage rather than something they belong to. Members start feeling like constituents rather than participants.

Third: elections every year or two create natural power concentrations. The person who serves on the board for eight years accumulates relationships, institutional memory, and informal authority that the electoral process can't dissolve even when it formally ends their tenure.

Direct democracy solves the representation problem by eliminating representation — everyone votes on everything. This preserves the sense that everyone's voice matters and prevents the emergence of a governing class. Its failures are also structural.

At scale, it's simply impractical. A housing cooperative with 200 members cannot make every facilities decision through an all-member vote. Decision fatigue is real. The volume of decisions that communities face is enormous, and asking everyone to be informed and engaged on all of them produces either rubber-stamping (decisions pass because people stop paying attention) or gridlock (the people who do pay attention block everything).

There's also a problem with minority protection. Pure direct democracy gives majorities the ability to consistently override minority interests with no structural check. In communities with significant demographic diversity, this becomes a serious justice problem.

Consensus governance — in its careful, skilled implementations — addresses both the representation problem and the minority protection problem simultaneously. The requirement that no one actively blocks a decision means that every person has effective veto power over things that would seriously harm them. Decisions that survive consensus process are genuinely supported by the community rather than just tolerated by the majority.

The drawbacks are real. Consensus is slow. It requires skilled facilitation. It requires community members to develop sophisticated communication skills — particularly the ability to distinguish between "I disagree with this" and "this decision is so harmful to me that I need to block it." Communities where everyone treats mild disagreement as block-level opposition cannot use consensus effectively.

There's also a failure mode where consensus becomes a tool of obstruction — where one or two people block everything they don't personally prefer, holding the community hostage. Functional consensus processes have mechanisms for this: a distinction between blocking (I can't live with this) and standing aside (I don't support this but I won't block it); processes for appeals when someone is deemed to be blocking in bad faith; and fallback voting provisions when consensus genuinely can't be reached after sustained good-faith effort.

Sociocracy (also called dynamic governance) is the most systematically developed alternative. It was designed explicitly to solve the scaling problem of consensus while preserving the inclusion benefits. The key innovations:

Double-linking between circles — each circle has a leader selected from above and a representative selected from within to carry information in both directions. This prevents the information asymmetries that plague hierarchical governance.

Consent-based decision making — not consensus (everyone enthusiastically agrees) but consent (no one has a paramount objection). This speeds the process while still protecting against serious harm.

Role and policy distinctions — people have defined roles with defined authority, and decisions are made in the appropriate domain rather than everything going to the top. This allows distributed authority without chaos.

Regular structured review — decisions, roles, and processes are systematically reviewed on a regular cycle. Nothing is permanent. The organization can update itself.

The learning curve is real. Communities that try to implement sociocracy without training, without committed facilitation, and without patience usually abandon it after a few frustrating meetings. Communities that stick with it report that it genuinely works better at scale than any other model they've tried.

The question of legitimacy

Any governance model is only as good as its legitimacy — the shared belief among community members that the process is fair and that decisions made through it are binding. Legitimacy is earned through transparency (people can see how decisions are made), participation (people have meaningful ability to engage in the process), and track record (the process has produced outcomes that most people can live with over time).

Legitimacy can be lost. A governance process that makes good decisions in ways that people don't understand loses legitimacy. A governance process where participation is technically open but practically controlled by insiders loses legitimacy. A governance process that consistently produces outcomes favoring certain members at the expense of others loses legitimacy.

When legitimacy collapses, you get exit, voice, or sabotage. The healthiest communities have governance structures that make it relatively easy to raise concerns through voice before people give up and leave, and that take those concerns seriously enough to keep people from having to choose between silently complying and leaving.

Transitions and crises

The most common governance crisis is the transition from the founding period to maturity. Founding communities run on founder authority — the people who started the thing have authority that comes from having built it. This is often appropriate in the early phase. It becomes a problem when the community grows, when founders burn out, or when their vision and the community's evolved needs diverge.

Communities that successfully navigate this transition usually do so by consciously designing the transition — deciding what governance structure will work at scale before they need it, piloting it while the founders are still around to troubleshoot, and building institutional memory into the structure rather than leaving it all in individual heads.

Communities that fail this transition either fragment (factions form around different visions with no legitimate process to resolve them) or calcify (the founders' authority becomes entrenched and the community stops being able to adapt).

What good governance actually looks like

Good community governance has these properties:

It's explicit. Everyone knows how decisions are made. Not just the inner circle — everyone.

It matches the community's scale and purpose. A ten-person cooperative and a thousand-person housing development need different governance.

It distributes power widely enough that the community's wellbeing isn't contingent on any single person or clique.

It has a legitimate process for changing itself. The governance structure can be updated without requiring a power struggle.

It includes mechanisms for conflict resolution that don't require the conflict to go nuclear before there's a path for handling it.

It preserves institutional memory — the structure encodes knowledge about how the community works, rather than leaving all of that knowledge in the heads of whoever has been there longest.

It creates accountability — people who hold authority can be held accountable when they misuse it, through processes that don't require the community to destroy itself.

None of this is easy. Governance design is hard work. But the communities that invest in doing it well are the communities that survive and actually do what communities are supposed to do. The communities that avoid it are the ones sending sad emails about how they "grew apart" or "had irreconcilable differences" — usually about something that a well-designed governance process would have resolved before it became existential.

Build the governance before you need it. That's the lesson.

---

Related concepts: sociocracy, consensus decision making, institutional memory, conflict resolution, community design, cooperative governance, power distribution