Sociocracy 3.0 (S3)

Details

Author: James Priest, Bernhard Bockelbrink, and Liliana David
Category: Frameworks
Published: 2015
Source: Sociocracy 3.0
Source URL: https://patterns.sociocracy30.org
Access: public

Description

A pattern library of more than 70 modular practices for governance, collaboration, and structuring, designed to be adopted piecemeal rather than as a whole system. Released as Creative Commons in 2015.

Annotation

Sociocracy 3.0, written S3, is a pattern library released as a Creative Commons body of work in March 2015 by James Priest, Bernhard Bockelbrink, and Liliana David. It synthesizes ideas from classical sociocracy (Gerard Endenburg, 1970s Netherlands), Agile, and Lean into more than 70 named patterns: consent decision-making, circles, double-linking, drivers, navigating tensions, governance backlogs, peer feedback, and many others. Each pattern is documented with a name, intent, problem, and solution, and is designed to be selected, adapted, and combined with whatever the group already does. This is the operational difference between S3 and the systems it draws from: where Endenburg's classical sociocracy is a coherent system you adopt whole, S3 lets a group pick the patterns it needs and keep the rest of its life intact.

The pattern-library structure is what has spread S3 quickly through cohousing, ecovillage, cooperative, and self-managing-organization networks since 2015. Vidàlia in Catalonia, Spain, is the cleanest archive example: their `governance_model` field reads "Vidàlia operates through Sociocracy 3.0. Governance is structured in circles and tiered membership levels." Tamera in Portugal added sociocracy alongside Forum in 2021 after a community consolidation process facilitated by Miki Kashtan, and the two now run together as a relational layer (Forum) and a procedural layer (sociocracy). ZEGG in Germany has run sociocracy alongside Forum for years. Findhorn in Scotland is currently exploring it.

The conceptual move that distinguishes S3 from consensus is the consent threshold: a decision proceeds when no one raises an objection grounded in the work of the circle. The often-cited operating phrase is "good enough for now, safe enough to try." This is a lower bar than consensus (which asks for active agreement) and a different bar from majority voting (which asks who has the most votes). The lower bar is what allows S3 groups to move faster than consensus groups, at the cost of less buy-in per decision and a higher reliance on the trust that circle members can object meaningfully when something is unsafe to try.

Critique to flag: the pattern library is large, and groups sometimes spend years configuring before they actually decide anything. S3 also tends toward thin proceduralism when imported into communities without an underlying relational practice (Forum, Way of Council, Nonviolent Communication, or similar). The communities that get the most from S3 pair the procedural layer with a relational one. The communities that get the least from S3 try to use it as the whole stack.

Full text

# Sociocracy 3.0 (S3)

## Description (one-sentence card text)

## Long annotation (italic block under the hero)

## Full content

## What it is, and what it is for

Sociocracy 3.0, written S3, is an open pattern library for governance, collaboration, and organizational structuring. It was released in March 2015 as a Creative Commons body of work and continues under continuous development by its three co-developers: James Priest, Bernhard Bockelbrink, and Liliana David. The library currently documents more than 70 named patterns. Each pattern is recorded with a name, an intent, the problem it addresses, and the solution it proposes. Adoption is piecemeal by design: a group selects the patterns it needs, leaves the rest, and combines them with whatever practices the group already runs.

The canonical short definition, in the words of the patterns library itself, is that S3 is "a practical guide for evolving agile and resilient organizations of any size, from small startups to large international networks and government agencies." What S3 produces is a shared procedural vocabulary for groups that want to make decisions, distribute roles, navigate tensions, and govern themselves without hierarchy. It is operational rather than spiritual: S3 does not ask anything of a group's underlying values or philosophy beyond a willingness to work with consent rather than command.

The practice is built for groups making operational decisions together at any scale: residential communities, cooperatives, distributed teams, federations, larger organizations. Likely fit: groups that have existed long enough to have accumulated procedural questions but not so long that the existing way of deciding has hardened. Less likely fit: groups that have not yet built the trust required for consent-based decision-making to work, or groups that already run something that works and would be disrupted by introducing pattern-by-pattern.

S3 is a *procedural* layer. It is not, on its own, a relational layer. Communities that adopt S3 without an accompanying relational practice (Forum, Way of Council, Nonviolent Communication, Circle Way) often discover that consent decision-making degrades into thin proceduralism after the first year. The communities that hold S3 well treat it as the operational complement to a relational practice rather than as a complete governance stack.

> **From the field.** S3 sits in the ToGather archive at the layer of explicit governance structure. [Vidàlia](/community/vidalia) in Catalonia is the archive's clearest S3 example, with the framework named directly in the community's `governance_model` field. Tamera, ZEGG, and Findhorn (each with separate Library entries on their relational practices) all also use sociocracy at the procedural layer, paired with their respective relational practices. None of them treats sociocracy as the whole stack.

<figure>
<svg viewBox="0 0 700 440" xmlns="http://www.w3.org/2000/svg" style="max-width:660px; display:block; margin:24px auto; background:#fcfaf5;">
<text x="350" y="26" text-anchor="middle" font-family="Georgia, serif" font-size="13" fill="#857e72" font-style="italic">A pattern library of 70+ patterns. Adopt piecemeal. Pair with a relational practice.</text>
<circle cx="350" cy="105" r="42" fill="#f7f1e3" stroke="#5d4f3a" stroke-width="1.5"/>
<text x="350" y="103" text-anchor="middle" font-family="Georgia, serif" font-size="11" fill="#5d4f3a" font-weight="600">General</text>
<text x="350" y="118" text-anchor="middle" font-family="Georgia, serif" font-size="11" fill="#5d4f3a" font-weight="600">Circle</text>
<circle cx="180" cy="210" r="32" fill="#ffffff" stroke="#5d4f3a" stroke-width="1.5"/>
<text x="180" y="207" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#5d4f3a" font-weight="600">Land</text>
<text x="180" y="220" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#5d4f3a" font-weight="600">Circle</text>
<circle cx="520" cy="210" r="32" fill="#ffffff" stroke="#5d4f3a" stroke-width="1.5"/>
<text x="520" y="207" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#5d4f3a" font-weight="600">Finance</text>
<text x="520" y="220" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#5d4f3a" font-weight="600">Circle</text>
<line x1="200" y1="184" x2="316" y2="120" stroke="#c97e4f" stroke-width="1.5"/>
<line x1="216" y1="194" x2="324" y2="135" stroke="#5d4f3a" stroke-width="1.5" stroke-dasharray="2,2"/>
<text x="232" y="170" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">lead + delegate</text>
<line x1="500" y1="184" x2="384" y2="120" stroke="#c97e4f" stroke-width="1.5"/>
<line x1="484" y1="194" x2="376" y2="135" stroke="#5d4f3a" stroke-width="1.5" stroke-dasharray="2,2"/>
<text x="468" y="170" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">lead + delegate</text>
<text x="350" y="265" text-anchor="middle" font-family="Georgia, serif" font-size="11" fill="#857e72" font-style="italic">Double-linking: information flows up, decisions flow back down</text>
<line x1="60" y1="282" x2="640" y2="282" stroke="#e6dfd0" stroke-width="1"/>
<text x="350" y="304" text-anchor="middle" font-family="Georgia, serif" font-size="13" fill="#857e72" font-style="italic">The four core patterns</text>
<rect x="32" y="320" width="150" height="100" rx="6" fill="#ffffff" stroke="#5d4f3a" stroke-width="1.5"/>
<text x="107" y="344" text-anchor="middle" font-family="Georgia, serif" font-size="12" fill="#c97e4f" font-weight="600">CONSENT</text>
<text x="107" y="368" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">No objections grounded</text>
<text x="107" y="382" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">in the work?</text>
<text x="107" y="402" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">"Good enough for now"</text>
<rect x="194" y="320" width="150" height="100" rx="6" fill="#ffffff" stroke="#5d4f3a" stroke-width="1.5"/>
<text x="269" y="344" text-anchor="middle" font-family="Georgia, serif" font-size="12" fill="#c97e4f" font-weight="600">CIRCLES</text>
<text x="269" y="368" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">Domain, accountabilities,</text>
<text x="269" y="382" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">roles</text>
<text x="269" y="402" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">semi-autonomous</text>
<rect x="356" y="320" width="150" height="100" rx="6" fill="#ffffff" stroke="#5d4f3a" stroke-width="1.5"/>
<text x="431" y="344" text-anchor="middle" font-family="Georgia, serif" font-size="12" fill="#c97e4f" font-weight="600">DOUBLE-LINKING</text>
<text x="431" y="368" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">Two members sit</text>
<text x="431" y="382" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">in the parent circle</text>
<text x="431" y="402" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">feedback in both directions</text>
<rect x="518" y="320" width="150" height="100" rx="6" fill="#ffffff" stroke="#5d4f3a" stroke-width="1.5"/>
<text x="593" y="344" text-anchor="middle" font-family="Georgia, serif" font-size="12" fill="#c97e4f" font-weight="600">DRIVERS</text>
<text x="593" y="368" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">Tensions, opportunities,</text>
<text x="593" y="382" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">needs that call for action</text>
<text x="593" y="402" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">named, trial, review</text>
</svg>
<figcaption style="text-align:center; font-style:italic; color:#857e72; font-size:13px; margin-top:8px;">Double-linking between parent and working circles (top), and the four core patterns most groups adopt first (bottom).</figcaption>
</figure>

## Where it came from

S3 has two lineages converging in 2014. The first is classical sociocracy, developed by Gerard Endenburg in the Netherlands through the 1970s and 80s. Endenburg drew on cybernetic feedback principles from his earlier work in radar and electrotechnics, plus the educational ideas of Kees Boeke and Beatrice Cadbury (whose Werkplaats Kindergemeenschap school used a circle-based decision practice from the 1920s). Endenburg ran the full sociocratic system inside his own engineering firm in Rotterdam from the early 1970s and codified the four basic rules: consent governs decisions, the circle is the working unit, double-linking creates feedback between levels, and roles are elected by consent after open discussion. Classical sociocracy is sometimes called Sociocratic Circle Method (SCM) or Sociocracy 1.0 in retrospect.

The second lineage is the Agile and Lean software development community of the 2000s, which had developed its own pattern-based vocabularies for iterative work, emergent design, and self-organizing teams. By the early 2010s, a number of consultants and trainers were working at the intersection: applying classical sociocracy in Agile organizations, and applying Agile patterns in sociocratic ones.

In 2014, James Priest and Bernhard Bockelbrink came together to co-create a body of Creative Commons learning resources synthesizing the two lineages. The first version of Sociocracy 3.0 was launched in March 2015. Liliana David joined the team soon after. The three co-developers have since released several updates per year, treating the pattern library as a working draft that grows and changes with what practitioners report from the field.

The diagnosis underneath S3 was specific: classical sociocracy worked well for whole-system adoption, but most groups in 2015 either could not afford a full systemic conversion or did not want to disrupt existing practices that already worked. The pattern-library structure was the response: groups could select what they needed, build incrementally, and leave the rest of their life intact. The Creative Commons licensing was the second response: the patterns library could be translated, adapted, and forked freely, which is why S3 has spread quickly through volunteer networks that could not have afforded a paid certification system.

A note on lineage divergence: S3 is sometimes confused with Holacracy, another contemporary derivative of classical sociocracy, but the two are distinct. Holacracy was codified by Brian Robertson in 2010 as a tightly-defined constitutional system requiring whole-system adoption. S3 is intentionally modular and license-free. The two share an intellectual ancestor (Endenburg) but diverge sharply on whether governance is best held as a single coherent system or as a library of patterns.

## How it actually runs

The procedural detail below describes what S3 looks like when a group is using it well. The patterns library is the canonical reference; this section describes the most-adopted patterns and the operational shape they take in practice.

### The four core patterns

Most groups that adopt S3 begin with these four:

**Consent decision-making.** A proposal proceeds when no one raises an objection that is grounded in the work of the circle. An objection has to point to a specific harm or risk; preference and discomfort are not objections. The often-cited operating phrase is "good enough for now, safe enough to try." If no one objects, the proposal is adopted. If someone objects, the objection is integrated and the proposal is reshaped. The decision threshold is lower than consensus (which asks for active agreement) and different from majority voting (which counts preferences).

**Circles.** A circle is a semi-autonomous group with a domain (the area of work it is responsible for), accountabilities (the things it has to do), and roles (named functions filled by named people). Circles are formed when there is work that needs holding by a defined group, dissolved when the work is done, and modified when the work shifts. A community might have a Land Circle, a Finance Circle, an Entry Circle, a Conflict Circle, and a General Circle that holds the others.

**Double-linking.** Two members of each circle (typically the lead and a delegate) sit in the parent circle. This creates feedback in both directions: information flows up from working circles to the general circle, and decisions flow back down with context. Double-linking is what prevents the parent circle from becoming a board of directors that rules the working circles from above.

**Driver-based work.** Every circle's work is organized around drivers: the tensions, opportunities, or needs that call for action. A driver is named explicitly ("the membership process is taking too long"), the circle proposes a response, the response runs as a trial, and the driver is revisited at the next review. This pattern keeps work tied to real needs rather than to inherited committee structures.

### How a typical S3 meeting runs

A typical sociocracy meeting in a community context runs 60 to 120 minutes. The shape, drawn from the patterns library:

| Time | What happens |
|---|---|
| Opening | Brief grounding, agenda confirmation, time-keeping role assigned |
| Round 1 | Each member speaks once on the agenda items, no responses yet |
| Discussion | Open exchange on the items raised, structured by the facilitator |
| Proposals | Specific proposals named and refined |
| Consent rounds | For each proposal, the facilitator asks "any objections?" Each member responds in turn |
| Integration | Objections integrated, proposals modified until consent is reached |
| Closing | Decisions logged, follow-ups assigned, brief reflection round |

The role of the facilitator (sometimes called the leader or convener) is to hold the structure, not to drive the content. The content comes from the circle.

### Pattern adoption strategies

Per the patterns library, S3 can be adopted in three broad ways:

- **Pick a pattern.** Start with one pattern that addresses a specific tension. Run it. Add more later if it works.
- **Run a governance backlog.** Treat governance as work that is itself organized into a backlog of items to address, prioritized and sequenced like any other work.
- **Navigate via tensions.** Let the work of governance emerge from the tensions the group is actually experiencing. Each tension becomes a driver, each driver becomes a circle's responsibility, each response runs as a trial.

The three styles can mix: most groups use some combination of all three over time.

### A real moment

Vidàlia's `frameworkSignals` field in the ToGather archive lists the operational signals of their S3 practice: "Sociocracy 3.0," "Tiered membership structure," "Defined circles and shared decision-making." The tiered membership structure is itself an S3 pattern: not all members participate in all decisions, and the level of participation maps to the level of commitment to the community. New members enter with consultative voice; full members hold consent rights; circle leads carry decision authority within their circle's domain. This kind of layered participation is one of the things S3 makes legible that is hard to do well in pure consensus.

## What it is and what it is not

Some clarifications that come up often when groups consider S3:

- **S3 is not classical sociocracy.** Classical sociocracy (Endenburg's 1970s system) is a coherent whole-system adoption. S3 is a pattern library that lets you select what you need. Both share the consent decision-making move, but S3 treats it as one pattern among many rather than the foundation of a whole system.

- **S3 is not Holacracy.** Holacracy (Brian Robertson, 2010) is a tightly-defined constitutional system that requires whole-system adoption and a paid certification process. S3 is Creative Commons, modular, and self-taught. Both share the cybernetic ancestor but diverge sharply on adoption philosophy.

- **S3 consent is not consensus.** Consent asks: is there a reason this is unsafe enough to try, given what we know now? Consensus asks: do you actively agree? The lower bar of consent is what allows sociocratic groups to move faster than consensus groups, at the cost of some buy-in per decision.

- **S3 is not a relational layer.** S3 produces decisions and structures roles. It does not, on its own, address conflict, repair, or the deeper relational substrate of group life. Most communities that adopt S3 well pair it with a relational practice: Tamera Forum, Way of Council, Nonviolent Communication, or similar.

- **S3 pairs well with other practices.** Per the patterns library, S3 combines productively with Agile and Lean development practices, with Cynefin sense-making, with Restorative Circles, with NVC, with Bohm Dialogue, and with most relational practices in the broader Living Library.

- **S3 is not a finished system.** The pattern library is updated continuously by the three co-developers. The current version (mid-2026) is roughly the 14th major release since 2015.

## Communities practicing it

### [Vidàlia](/community/vidalia) (Catalonia, Spain, founded 2017, ~32 residents)

The clearest S3 example in the ToGather archive. A housing cooperative based in the historic Cal Vidal textile mill town one hour from Barcelona. The community's `governance_model` field reads, in full: "Vidàlia operates through Sociocracy 3.0. Governance is structured in circles and tiered membership levels." S3 is named explicitly as the governance framework, and Vidàlia uses S3 patterns including circles, tiered membership, defined responsibilities per membership level, and a structured pathway over two years for new members to move from applicant to full membership. Vidàlia's tags in the archive include "sociocracy" and "housing cooperative." Vidàlia is documented in the archive but no member interviews have yet been published.

### [Tamera](/community/tamera) (Alentejo, Portugal, founded 1995, ~170 residents)

Tamera adopted sociocracy alongside its long-running Forum practice in 2021, after a community consolidation process facilitated by Miki Kashtan. The two layers now run together: Forum as the relational layer, sociocracy as the procedural layer. The shift is described in [Joshua Gottenko's interview](/interview/69679e0dbb287c49bb10b855): Kashtan said directly to the community that "Tamera is a low-trust environment. You need to face that," and the community's response over the following years included introducing sociocratic decision-making structures. The combination is a useful counter-example to the assumption that mature communities can hold themselves together with relational practice alone. See the separate [Tamera Forum](/library/tamera-forum) entry for more on the relational layer.

### [ZEGG](/community/zegg) (Bad Belzig, Germany, founded 1991, ~100 residents)

Sister practice to Tamera. ZEGG runs sociocracy alongside ZEGG Forum (a variant of the same Bauhütte-rooted Forum tradition). ZEGG's archive entry includes a [ZEGG: Seven Values, Forum, and Sociocracy](/library/zegg-constitutional-practice) Library entry, documenting the layered governance approach. ZEGG is in the ToGather archive as documented but not yet interviewed.

### [Findhorn Ecovillage](/community/findhorn-ecovillage) (Scotland, founded 1962, ~200 residents)

Findhorn has historically run consensus with attunement (the silent-listening practice that opens every meeting). Following the founding of the Ecovillage Findhorn CBS in 2024 and the broader institutional restructuring, the community is currently exploring sociocracy as an additional layer alongside attunement and consensus. As of mid-2026, Findhorn is in the early adoption phase. The exploration is itself a useful case for what it looks like when a long-running community considers adding S3 to existing practice without displacing it.

### Sociocracy For All (network, founded 2015)

Not a residential community, but a network organization that trains, coaches, and supports communities adopting sociocracy. Sociocracy For All offers the "Sociocracy For Communities" curriculum that several archive communities have trained in (the Sociocracy For Communities course is itself a Library entry in the Courses category). The network is the most active source of S3-adjacent training in the cohousing and ecovillage sector.

> **From the field.** A pattern across the four communities. S3 enters communities that already have something working (Forum at Tamera and ZEGG, attunement and consensus at Findhorn, a tiered membership process at Vidàlia) rather than communities trying to build from scratch. This is consistent with the patterns library's own framing: S3 is for "evolving" organizations, not for founding ones. The communities that get the most from S3 are the ones that introduce it to address specific tensions in an existing way of working, not the ones that try to use it as the whole governance stack.

## How to begin practicing this in your own group

The honest answer is that S3 is genuinely modular and self-teachable, which is unusual for governance frameworks. The patterns library is free, the basic patterns are documented at length, and the consent decision-making pattern can be adopted in a single meeting. What follows is what good practitioners say about adoption sequencing.

**1. Start with a single pattern.** Don't adopt S3 wholesale on your first attempt. Pick one pattern that addresses a specific tension your group has right now: consent decision-making, drivers, governance backlog, or circles. Run that pattern for two to three months. See what happens. Add more later if the first one works.

**2. Read the patterns library.** [`patterns.sociocracy30.org`](https://patterns.sociocracy30.org). Free, Creative Commons. The Practical Guide is published as a single web book and as a PDF. Read the introduction, the patterns you plan to use, and the section on adoption strategies. Skim the rest. Come back to specific patterns as needed.

**3. Take the Practitioner Course.** [`academy.sociocracy30.org/sociocracy-3-0-practitioner-course`](https://academy.sociocracy30.org/sociocracy-3-0-practitioner-course). The official multi-week course offered by the three co-developers. Pricier than self-study but the most direct way to develop facilitation skill. For groups that want the SoFA-flavored variant, [Sociocracy For All Academy](https://www.sociocracyforall.org/sofa-academy/) offers parallel training oriented toward residential communities.

**4. Pair S3 with a relational practice.** S3 produces decisions and roles. It does not, on its own, build trust or process conflict. Communities that get the most from S3 run it alongside Forum, Way of Council, NVC, or another relational practice. Decide which relational practice you will use *before* you adopt S3, not after. See the companion Library entries for [Tamera Forum](/library/tamera-forum), Way of Council (forthcoming), and Nonviolent Communication (forthcoming).

**5. Run your first sociocracy meeting with a coach.** The patterns are documented, but the facilitation skill is not transferable from text. Sociocracy For All, the S3 academy, and many independent practitioners offer coached first meetings or short residencies. The cost is modest. The first three meetings done well shape years of subsequent practice.

**6. Plan for the year-three reckoning.** A pattern from communities that have adopted S3: enthusiasm in year one, productivity in year two, drift toward thin proceduralism in year three. The drift happens when circle work loses its connection to the actual relational life of the community. Year three is when most communities decide whether to invest in deepening the relational layer underneath S3 or accept that S3 has become something procedural rather than alive. Plan the reckoning, do not be surprised by it.

## Living examples and entry points for community builders

S3 is one of the most-adopted contemporary governance frameworks in the cohousing, ecovillage, cooperative, and self-managing-organization sectors. The pattern library has been translated into more than a dozen languages, used by thousands of organizations worldwide, and continues to grow through volunteer contributions. The examples below are not meant to be exhaustive; they are meant to show the range of contexts in which S3 has landed.

**Living examples beyond the archive.**

[Buurtzorg](https://www.buurtzorg.com), the 9,000-person Dutch nursing organization, runs without managers using a combination of self-managing teams, peer advice protocols, and sociocratic-adjacent decision practices. Buurtzorg is widely cited as proof that self-management can scale past 30 people; the patterns S3 documents are the formal vocabulary for what Buurtzorg has been doing in practice since 2006. Frédéric Laloux's *Reinventing Organizations* draws extensively on Buurtzorg for the Teal-organization framing.

[GLS Bank](https://www.gls.de) in Bochum, Germany, the country's first ethical bank (founded 1974), uses sociocratic decision-making at its branch and team level. GLS is one of the largest financial institutions running sociocratic governance.

The German federal cohousing association, BGW (Berliner Genossenschaftsverband Wohnen), supports member cooperatives in adopting sociocracy. Several German Mietsshäuser Syndikat housing collectives use S3 patterns at the level of individual house projects.

In the United States, [Sociocracy For All](https://www.sociocracyforall.org) is the central network. SoFA has trained hundreds of cohousing communities and ecovillages in S3 since 2015 and runs an academy, a community of practice, and an annual conference.

Smaller-scale: many tech worker cooperatives (CoLab.coop, Hypha Worker Co-op, Sociocracy.io itself) run on S3. The cooperative tech sector has been one of the strongest adopters since 2017.

**Adjacent applications.**

The Holacracy community ([holacracy.org](https://www.holacracy.org)) is the closest sister framework. Holacracy and S3 share a cybernetic ancestor but diverge on whether governance is best held as a coherent system or as a pattern library. Reading the [Holacracy Constitution v5.0](https://www.holacracy.org/constitution/5-0/) alongside the S3 patterns library is the cleanest way to see the trade-off.

[Loomio](https://www.loomio.com), the open-source decision software, ships with templates for several S3 patterns including consent decision-making and the advice process. Communities running Loomio for asynchronous decision-making often informally use S3 vocabulary.

The Cynefin framework (Dave Snowden) is frequently paired with S3 for sense-making in complex situations: Cynefin diagnoses what kind of problem the group is facing, S3 provides the procedural patterns for working with each type.

**Entry points for community builders.**
1. **Read the [Practical Guide to Sociocracy 3.0](https://patterns.sociocracy30.org)** in a single sitting. Free, Creative Commons, ~200 pages. Skim the patterns, read the adoption strategies in detail, return to specific patterns as needed.
2. **Watch a real S3 meeting.** Sociocracy For All publishes recorded meetings on their YouTube channel and runs occasional public-facing demonstrations. Twenty minutes of watching how a consent round actually runs teaches more than two hours of reading.
3. **Try one consent decision in your next meeting.** Pick a small decision your group is making anyway. Frame it as a proposal. Ask: "Any objections grounded in the work of this group?" See what happens. The first time you do this is the most useful single experiment in S3 adoption.
4. **Connect with a local cohort or coach.** [Sociocracy For All's directory](https://www.sociocracyforall.org/find-a-trainer/) lists trainers and coaches by region. The S3 academy maintains a separate practitioner directory. A 90-minute coached session is often enough to surface what your group will struggle with most.
5. **Pair S3 with a relational practice you actually run.** Decide before you adopt S3 what your relational layer will be. If you do not yet have one, build it first; the procedural layer alone does not hold a community.

**One caution.** S3 is procedural. It does not build trust, process conflict, or hold the relational substrate of community life. Communities that adopt S3 without a relational practice tend to discover by year three that consent decision-making has become thin: people stop objecting because objecting takes too much energy, or because the work of integrating objections has become tedious. The communities that hold S3 well treat it as one of two layers, not the whole stack. Do not import S3 as a substitute for the deeper work of building trust, processing conflict, and developing the relational skills that any long-running community needs.

## Where it gets hard

Five tensions inside S3 worth naming directly:

**The pattern library is large, and configuration can become its own work.** S3 documents more than 70 patterns. A group that takes "select what you need" seriously can spend years configuring before it actually decides anything. The same modularity that makes S3 adoptable can become a procrastination structure if the group is reluctant to commit to anything specific. The remedy, per experienced practitioners, is to start with a single pattern and add only when an existing pattern is producing tension.

**Procedural drift toward thin proceduralism.** Communities that adopt S3 without an underlying relational practice tend to discover by year two or three that consent decision-making has become formalistic. The forms are followed but the substance is gone. Objections are not raised because raising objections has become exhausting. Decisions are passed because the work of refining them has become tedious. The procedural layer floats free of the actual relational life of the group.

**Cultural assumption embedded in S3 about meeting culture.** S3 was developed by practitioners working in northern European and North American organizational contexts. The implicit cultural assumption is a meeting culture that values structured turn-taking, explicit naming of objections, and direct expression of disagreement in a public group setting. In groups with members from cultures where dignity is held through restraint, where direct disagreement is uncomfortable, or where decision-making traditionally happens elsewhere (informal conversation, family consultation, elder mediation), S3 can land as alienating even when it is offered as voluntary.

**Power within circles can ossify into role-based fiefdoms.** S3 distributes authority across circles with named roles. The same structure that prevents central command can produce small concentrations of authority within circles, especially when role-holders stay in roles for years. The patterns library addresses this with patterns like role review and role rotation, but groups frequently adopt the circle structure without the rotation patterns. The result is a more distributed but still entrenched authority pattern.

**S3 does not address founder authority or generational transfer.** A pattern most-quoted by communities that have adopted S3 over a decade or more: the framework is good at distributing authority among adults who all chose to be there, but it does not do well with the question of how founder authority is renegotiated as founders age, or how second-generation members (born into the community) come into authority. These are deeper relational and cultural questions that S3 does not, on its own, resolve.

## More resources

### Canonical primary sources

- [A Practical Guide to Sociocracy 3.0](https://patterns.sociocracy30.org). The patterns library itself. Free, Creative Commons, continuously updated. Start here.
- [Sociocracy 3.0 Authors page](https://patterns.sociocracy30.org/authors.html). Background on James Priest, Bernhard Bockelbrink, and Liliana David, the three co-developers.
- [Influences and History of Sociocracy 3.0](https://patterns.sociocracy30.org/history.html). The pattern library's own account of its lineage from classical sociocracy, Agile, and Lean.
- [The Patterns](https://patterns.sociocracy30.org/patterns.html). The full pattern catalog with names, intents, and structured solutions.
- [GitHub repository for the Practical Guide](https://github.com/S3-working-group/s3-practical-guide). The source repository for the open-licensed text.

### Trainings and residencies

- [Sociocracy 3.0 Practitioner Course (S3 Academy)](https://academy.sociocracy30.org/sociocracy-3-0-practitioner-course). The official multi-week course from the co-developers.
- [Sociocracy For All Academy](https://www.sociocracyforall.org/sofa-academy/). Parallel training oriented toward residential communities and cohousing.
- [Sociocracy For All Trainer Directory](https://www.sociocracyforall.org/find-a-trainer/). Local trainers and coaches by region.
- [Thrive in Collaboration](https://www.thriveincollaboration.com). James Priest and Liliana David's consultancy and training portal.

### Theoretical lineage

- *Sociocracy: The Organization of Decision-Making* by Gerard Endenburg (1998). The classical reference for Sociocracy 1.0, the lineage S3 builds on.
- *We the People: Consenting to a Deeper Democracy* by John Buck and Sharon Villines (2017). A standard text on classical sociocracy in residential community settings.
- *Reinventing Organizations* by Frédéric Laloux (2014). The contemporary theoretical companion: where Laloux describes the Teal-organization landscape, S3 provides the operational vocabulary. Reads as a sister text.
- *The Cynefin Framework* by Dave Snowden. The sense-making framework that pairs naturally with S3 for diagnosing what kind of problem a group is facing.

### Companion frameworks

- [Tamera Forum](/library/tamera-forum). The relational layer Tamera pairs with sociocracy after 2021. The two together rather than either alone.
- **Way of Council** (separate Library entry, forthcoming). Another relational layer that pairs well with S3.
- **Nonviolent Communication** (separate Library entry, forthcoming). The communication layer most-cited by S3 practitioners.
- **Holacracy** (separate Library entry, forthcoming). The sister framework with a different adoption philosophy.
- **Consent Decision-Making (Sociocratic)** (separate Library entry, forthcoming). The single most-adopted S3 pattern, often introduced before the rest of the framework.
- **Classical Sociocracy / Sociocracy 1.0** (separate Library entry, forthcoming). The lineage S3 builds on.

### From the ToGather archive

- [Vidàlia community card](/community/vidalia). The clearest archive example of an S3-grounded community. No interviews yet published.
- The [Tamera Forum entry](/library/tamera-forum) discusses Tamera's 2021 adoption of sociocracy alongside Forum, including [Joshua Gottenko's interview](/interview/69679e0dbb287c49bb10b855) describing the Miki Kashtan-facilitated community consolidation that prompted it.

## Short summary (preview text)

An open Creative Commons pattern library of 70+ modular practices for governance, decision-making, and self-organization. Released in March 2015 by James Priest, Bernhard Bockelbrink, and Liliana David, synthesizing classical sociocracy (Endenburg, 1970s Netherlands) with Agile and Lean. Designed for piecemeal adoption rather than whole-system replacement. The clearest archive example is Vidàlia in Catalonia.