Sociocracy And Holacracy — Flat Governance Models

At first pass, governance seems like an organizational management topic, not a community and connection topic. But governance is the architecture of collective decision-making — it determines who has voice, whose objections get heard, who exercises authority over shared resources and shared life, and what happens when people disagree.

Bad governance is a community-destroyer. Autocratic leaders produce resentment, passive resistance, and eventual collapse. Majority voting produces persistent minorities who feel unheard and eventually disengage. Fake consensus — where the group nominally agrees but individuals privately dissent — produces the surface of unity over a substrate of alienation.

Good governance creates the conditions for genuine community: everyone has legitimate voice, decisions represent actual buy-in, conflict can be surfaced and worked through rather than suppressed, and authority is connected to real accountability. Sociocracy and holacracy are attempts to formalize good governance — to move beyond "whoever has the loudest voice wins" and "we vote and the minority loses" into something more nuanced and more genuinely inclusive.

This is why these systems matter at the community scale: they're attempting to solve the core problem of collective self-determination, which is how you make decisions together without systematically silencing some people or burning out the people who care most.

Gerard Endenburg was an engineer who studied cybernetics — the science of feedback and self-regulation in systems. Norbert Wiener's cybernetics and the later work of Stafford Beer on organizational cybernetics provided the conceptual framework: a well-functioning organization is a self-regulating system where information flows freely, feedback loops are intact, and authority is distributed to the level where the relevant information exists.

Endenburg applied this framework to his family's electrical engineering company in the Netherlands in the 1970s. He was dissatisfied with both conventional hierarchy (which concentrated decision-making authority where information was weakest — at the top) and with the cooperative-style full consensus model (which was slow, vulnerable to blocking, and tended to suppress genuine disagreement through social pressure to agree).

His solution was the Sociocratic Circle Method (SCM), which he implemented in his company and formalized through the 1970s-1990s. The system spread slowly through cooperative and intentional community networks, becoming better known in the Anglophone world through the work of John Buck and Sharon Villines, who published the influential We the People: Consenting to a Deeper Democracy in 2007.

1. Circles. The organization is structured as a set of circles, each with a defined domain of authority. Circles may be nested — a top-level circle might contain several sub-circles, each governing a specific domain. The critical feature is that circles have real authority within their domain. They don't make recommendations — they make decisions. A finance circle decides on budget allocations within parameters set by the larger circle; it doesn't petition a CEO.

2. Double-linking. Between circles, there are double links: a "lead link" appointed by the larger circle to represent that circle's needs within the sub-circle, and an "elected rep" chosen by the sub-circle to participate in and represent the sub-circle within the larger circle. This means information and influence flow in both directions. The sub-circle's perspective is present in the larger circle's deliberations; the larger circle's direction is present in the sub-circle's. This is structurally different from hierarchical organizations where communication flows primarily down, and feedback flows up only if a brave individual speaks up.

3. Consent-based decision making. Decisions in sociocracy are made by consent, not consensus. The question is not "does everyone agree?" but "does anyone have a paramount objection?" A paramount objection is one that would actively impede the organization's ability to achieve its purpose. Minor disagreements, preferences for a different approach, reservations that don't rise to the level of genuine harm — these don't block. The person with the objection is asked to articulate it specifically, and the group works to amend the proposal to address the objection without abandoning the proposal's core intent.

This is more nuanced than it sounds. The consent model: - Lowers the activation energy for making decisions (you don't need everyone to love it) - Maintains protection for genuine minority concerns (you can't override a specific harm claim by majority) - Encourages people to articulate objections specifically rather than sitting on vague discomfort - Creates a culture where saying "I have an objection" is normal and valued, not threatening

4. Elections by consent. When filling roles, sociocracy uses a specific election process: each person nominates someone and states their reasons publicly. After all nominations, the facilitator can propose a candidate based on the reasoning that emerged. Anyone can object to the proposal with a specific reason. The process produces elected role-holders with genuine community buy-in, and it uses the same information-surfacing function as the nominations process — hearing why people made different nominations reveals community values and perceptions.

Brian Robertson worked in software development and was frustrated by the gap between agile software practices (which distributed authority and adapted rapidly) and organizational governance (which remained stubbornly hierarchical). He developed holacracy as a complete governance operating system — a detailed constitutional document that specifies how decisions are made, how roles are defined, how meetings work, and how conflicts are resolved.

Holacracy's key innovations over sociocracy:

Roles over persons. In holacracy, the organization is described as a set of roles, not people. Each role has defined accountabilities, domains, and purposes. People fill roles — a single person might fill multiple roles across different circles. This distinction matters because it separates the person from the role's function: you're not criticizing Tom when you say the role of Finance Manager needs to be more responsive. You're describing a role accountabilities issue. This depersonalizes organizational friction in useful ways.

Defined meeting formats. Holacracy specifies two meeting types with exact formats: the Tactical Meeting (for operational coordination and rapid processing of tensions) and the Governance Meeting (for changing the structure of roles, circles, and policies). The rigidity of the formats is controversial — many practitioners find them cumbersome — but the intent is to create predictable structures that process organizational tensions efficiently without consuming endless meeting time.

The Constitution. Holacracy's constitution is a legal document that, when adopted, distributes authority from traditional leadership to the governance process. A CEO who adopts holacracy literally signs away their authority to override the governance system. This is why holacracy is both powerful and contentious: it's genuinely non-hierarchical in design, which requires genuine willingness from existing power holders to relinquish traditional authority.

In 2014, Zappos CEO Tony Hsieh announced that the company would adopt holacracy — an unusual move for a company of 1,500+ employees. The implementation was turbulent. Zappos offered buyouts to employees who didn't want to work in the new structure; 18% took them. Management layers were eliminated. Job titles disappeared. The transition was described by many employees as chaotic, anxiety-producing, and in some cases personally damaging.

By the late 2010s, Zappos had modified its implementation significantly, retaining some holacracy elements while adding back structure that the company found it needed.

What went wrong? Analysts point to several factors:

Scale mismatch. Sociocracy and holacracy are well-documented to work at the scale of 5-150 people. A 1,500-person company is substantially more complex, and the systems hadn't been tested at that scale.

Culture mismatch. Zappos had a specific culture — high energy, customer-service-focused, personality-driven — that didn't map well onto the impersonal role-based structure of holacracy. People who had succeeded at Zappos by being themselves found the role/person distinction alienating.

Top-down implementation of a bottom-up system. Holacracy is supposed to distribute authority. Zappos imposed it via the authority of the CEO. The irony is significant: using hierarchical power to install an anti-hierarchical system tends to produce resistance and confusion.

Insufficient training and transition support. Holacracy's governance processes are not intuitive. Without extensive facilitation support and time to develop facility with the new processes, people defaulted to confusion.

The Zappos case is widely cited as evidence that holacracy doesn't work. This is too simple. It's evidence that imposing any complex governance change on a large organization without adequate preparation, cultural alignment, and transition support produces problems. The co-housing communities, cooperatives, and medium-sized organizations that have implemented sociocracy and holacracy successfully don't look like the Zappos case.

The evidence base for sociocracy and holacracy is clearest in:

Cooperatives. Worker cooperatives, housing cooperatives, and consumer cooperatives have a structural need for governance that distributes authority among members who have genuine stake in outcomes. Sociocracy fits this structure naturally. Hundreds of cooperatives use sociocratic governance effectively.

Intentional communities. Co-housing communities, ecovillages, and other intentional communities use sociocracy extensively. The Sociocracy for All (SoFA) network has documented sociocratic implementation across hundreds of communities. Communities report faster, clearer decision-making compared to the consensus processes they previously used, with less burnout among the people who participate most actively.

Non-profits and social enterprises. Organizations with mission-driven cultures, where participants have genuine stake in outcomes and genuinely want voice in direction, tend to be good fits. The governance structure aligns with the organizational culture.

Schools and educational communities. Democratic schools and educational cooperatives have used sociocracy to involve students, parents, and teachers in genuine governance. The double-link structure allows information from students to flow into faculty decisions and vice versa in ways that don't happen in conventional school governance.

Small-to-medium businesses where the founding team wants distributed leadership. Companies of 20-100 people where the founders want to distribute authority rather than concentrate it have implemented sociocracy with documented success.

Sociocracy and holacracy are interesting not primarily as organizational management techniques but as attempts to answer a question about community: how do you make decisions together in a way that everyone can genuinely live with?

The answer both systems give is: you need structures that surface real objections (rather than suppressing them), distribute authority to where the relevant information and accountability actually live, and create feedback loops that keep decisions responsive to real conditions.

These are not just organizational principles. They're community principles. The village that makes decisions well is the village that can hold together through difficulty, adapt to change, and distribute both the power and the responsibility of self-governance across its members.

The failure mode of most communities isn't conflict — it's the suppression of conflict, the accumulation of unvoiced grievances, the concentration of decision-making in a few people who burn out, and the passive disengagement of everyone else. Sociocracy and holacracy, at their best, are attempts to design against these failure modes.

They're not the only answer. But they're serious, tested attempts to formalize what good community governance looks like — and they're worth understanding even for communities that won't adopt them wholesale, because the principles (voice, consent, distributed authority, feedback loops) are sound regardless of the specific system you use to enact them.

Community that can govern itself is community that can sustain itself. That's the whole game.