# Sociocracy 3.0: Decision-Making Patterns for Self-Organising Teams

Author: Marin Niehues, Niehues Consulting · Published: 2024-03-28 · Organisation Design
Source: https://www.niehuesconsulting.de/en/blog/sociocracy-3-0-patterns/

Sociocracy 3.0 (S3) is a freely available collection of patterns with which teams and organisations shape decisions and accountability themselves. Seven principles set the direction, and the patterns are building blocks that a team picks up one at a time where a concrete need exists. The centrepiece is consent decision-making: a proposal stands when nobody holds a reasoned objection, a threshold lower than consensus and more dependable than a vote.

This article explains S3 from its primary source, describes the most important patterns and how they run, helps with choosing the right form of decision and shows how a team introduces S3 in five steps without redesigning the organisation.

**S3 answers the question of how a team can reach decisions that are fast and still find the agreement of the people who carry them out. It offers patterns, and each pattern solves a named problem.**

## What is Sociocracy 3.0 and where does it come from?

Sociocracy 3.0 is a framework of patterns for collaboration and self-organisation, developed from 2015 onwards by James Priest and Bernhard Bockelbrink. It is published under an open licence and is developed further by a community. The name points back to sociocracy, which the Dutch entrepreneur Gerard Endenburg formulated from the 1970s as the "Sociocratic Circle-Organisation Method" for his electrical engineering firm. It works with four fixed rules: a circle structure, double linking of circles, decision-making by consent and the election of people to roles by consent.

S3 takes the core ideas from there and releases them from the fixed rulebook. Its authors describe S3 as a collection that a team uses piece by piece. A team can begin with a single pattern, such as consent decision-making, and add others later when a problem calls for them. This sets S3 apart from Holacracy, which Brian Robertson developed and described in a book of the same name in 2015. Holacracy follows a constitution with fixed rules and meeting formats and is adopted as a whole. S3 can also be combined with Scrum or Kanban.

## Which seven principles underlie S3?

S3 rests on seven principles that serve as a test for every decision. The principle of effectiveness requires spending time only on what contributes to the goal. The principle of consent requires decisions against which there are no reasoned objections. Empiricism means testing assumptions against experience, and continuous improvement means reviewing agreements regularly. Equivalence gives everyone affected a voice in decisions that touch them. Transparency makes information accessible to all who need it, and accountability obliges everyone to take responsibility and to give feedback.

For executives the order of the principles is worth reading: effectiveness comes first and consent second. The principle of effectiveness asks about the speed and yield of every decision, the principle of consent asks about the agreement of those affected, and consent decision-making joins both aims.

## How does consent decision-making work?

Consent decision-making is a sequence in which a proposal is adopted as soon as nobody holds a reasoned objection. Consent differs from consensus: consensus requires the active agreement of everyone, whereas consent only requires the absence of a serious objection. An objection counts as reasoned when it names why the proposal endangers a goal of the team or causes harm. A mere preference counts as a remark and can improve the proposal without blocking it.

The sequence has fixed steps, led by a facilitator:

1. Present the proposal: the proposer presents the proposal and its trigger without defending it.
2. Clarifying questions: the group asks questions of understanding. Evaluations stay out.
3. Quick reactions: each person briefly voices an impression, in a fixed order.
4. Objection round: each person states whether they hold a reasoned objection and names it.
5. Resolve objections: the proposal is changed so that the objection falls away. A new objection round follows.

In this sequence an objection is a gift, because it surfaces knowledge the proposer lacked. The rounds become shorter once everyone grasps the difference between a preference and an objection. Consent also lowers the threshold for a first trial: a proposal does not have to be perfect, it has to be safe enough to try and to evaluate after a set period.

## Which patterns form the core of S3?

Five patterns form the core, and a team uses them to solve the most frequent decision problems.

Driver mapping describes the trigger for a decision. A driver consists of an observation and its effect, together with the need that follows. The pattern stops a team from arguing over solutions before it agrees on the problem. Proposal forming develops a proposal jointly, so that knowledge and early objections feed in. Role and domain define who is responsible for what and what a role holder may decide alone. A domain is the area in which a role has decision authority. Circles bundle roles and teams that pursue a goal together and connect to the wider circle through delegates. Evaluating and evolving agreements adds an expiry date or a review date to every decision.

**An example: driver mapping for a travel policy (illustrative)**
- Observation: travel costs in sales run a quarter above plan in the third quarter
- Effect: the department budget is exhausted in October and customer meetings are cancelled
- Need: the team needs a rule that protects customer visits and controls cost
- Next step: proposal forming with sales and finance, review after three months

## Which form of decision fits which situation?

The right form of decision follows the weight and reversibility of the decision. Decisions can be placed along a spectrum from autocratic decisions through delegated decisions and consent to consensus. The table summarises a practical assignment.

**Form of decision by situation**
Criterion | Autocratic | Consent | Consensus or vote | With Niehues Consulting
Typical situation | Urgent, clearly bounded, low weight | Several people affected, medium weight, change can be reversed | High weight, hard to reverse, equal voices required | The assignment is agreed with the accountable people for each type of decision
Speed | Very high | High | Low | Decision paths matched to delivery
Acceptance | Low if those affected are bypassed | High, because objections are worked in | Very high with consensus, variable with a vote | Measurable in implementation after 90 days
Risk | Knowledge is missing | Objections stall proposals when criteria are missing | Delay | Clear rules on who decides

A rule of thumb for daily work: decisions that can be reviewed and reversed within a set period belong in consent. Decisions that a team can undo only at high cost, such as choosing a platform for several years, deserve the effort of consensus or a decision by the responsible body.

## How does a team introduce S3 in five steps?

A team introduces S3 best step by step, starting with one pattern and one real trigger. Five steps lead there.

1. Choose a trigger: the team names a recurring decision problem, such as long approval loops or unclear responsibilities.
2. Practise consent: the team decides three to five small, reversible questions by consent and reviews afterwards what went well.
3. Clarify roles: the team describes roles with purpose and domain and reviews them at a fixed date.
4. Form circles: several teams connect through delegates so that decisions are not lost between levels. The article on [Flight Levels](/en/blog/flight-levels-coordinating-work/) describes how work can be coordinated across three levels.
5. Measure results: after 90 days the accountable people read metrics such as decision lead time, number of reversals and participant satisfaction.

[unFIX](/en/blog/unfix-model-organisation-building-blocks/) and [Team Topologies](/en/blog/team-topologies-organising-teams-for-flow/) arrange the structure of an organisation. S3 adds patterns by which decisions are made within that structure.

## When does S3 fit, and when does another route?

S3 fits organisations in which teams with specialist knowledge make many decisions and in which managers are willing to hand over decision authority. Typical settings are product organisations and knowledge work with a high coordination load. S3 offers little where regulations or standards fix decisions completely, for example in safety-critical processes with a fixed chain of release.

Three prerequisites should be met. First, leadership names which decisions it hands over and which limits apply. Second, a practised facilitator is available, internal or external. Third, the team has time to rehearse the patterns before applying them to critical questions. For larger programmes the article on [agile scaling without a framework](/en/blog/agile-scaling-without-framework/) shows how companies develop their own rules without adopting a complete package.

## Self-organisation with Niehues Consulting

[Niehues Consulting](/en/) is a consultancy for AI management and organisational design from a delivery perspective, based in Düsseldorf. Founder Marin Niehues builds organisations that deliver, in projects ranging from VC-funded scale-ups to DAX 40 corporations and in more than 20 countries on six continents. In the service area of organisational design he clarifies with the executive team which decisions teams take, which roles they need and how decision paths work in delivery.

The approach follows the Niehues Delivery Model with its three phases. For decision patterns three test questions matter most: Who decides, who delivers, who uses? Which roles and decision paths does operations need? Which metric shows after 90 days that the solution has landed? The entry point is a free initial consultation of 30 minutes, which you can arrange via the [contact page](/en/#kontakt).

**Conclusion**
Sociocracy 3.0 gives teams patterns for fast decisions that people accept. Consent replaces the search for everyone's agreement with the question of reasoned objections, driver mapping clarifies the trigger, and roles with domains fix responsibility. A team begins with one pattern, one real trigger and a review after 90 days.

**Sources**
- Priest, Bockelbrink: Sociocracy 3.0, open documentation and pattern collection (sociocracy30.org), from 2015
- Endenburg: Sociocracy: The Organization of Decision-Making, book, 1998
- Robertson: Holacracy, book, 2015

## Frequently asked questions

### What is Sociocracy 3.0 in one sentence?

Sociocracy 3.0 is a freely available collection of patterns for decisions and self-organisation in teams and organisations. Seven principles set the direction, and the patterns can be introduced one at a time.

### What is the difference between consent and consensus?

Consensus requires the active agreement of everyone, whereas consent is reached when nobody holds a reasoned objection. Decisions therefore come faster while the knowledge of those affected still flows in. A preference counts as a remark, and an objection must name a goal of the team or a harm.

### How do S3 and Holacracy differ?

S3 is a collection of patterns that a team uses piece by piece, while Holacracy is a fixed rulebook with a constitution. Holacracy is adopted as a whole, whereas S3 combines with existing structures and frameworks. Both approaches trace back to sociocracy.

### Which teams is Sociocracy 3.0 suited to?

S3 suits teams that make decisions themselves using specialist knowledge and whose leadership hands over authority. Product organisations and knowledge work are particularly suitable. In processes with a fully prescribed release chain, S3 adds little.

### How long does it take to introduce S3?

First effects are visible after a few weeks, once a team practises a pattern on real decisions. A dependable evaluation is possible after 90 days using metrics such as decision duration and the number of reversals. Extension to further teams follows in steps.

### Who decides in a self-organised company when there is disagreement?

The role in whose domain the question falls decides, or the circle that holds the domain. If responsibility is unclear, the circle first clarifies the domain by consent. Leadership defines in advance which decisions stay with it.

### Does S3 require certification or a licence fee?

No, the patterns are freely available and may be used. Anyone who passes them on follows the terms of the open licence. A practised facilitator is enough for the rollout, and no certificate is required.