Holacracy¶

A branded organizational-governance method distributing authority through nested circles, explicit roles and rule-governed governance meetings.

Version: v2 · 2026-09-19 · History
Domain-specific #: 4896
Domain group: Professional & Organizational Practice
Origin domain: Organizational & Management Science
Subdomain: Organization Design → Organizational & Management Science

Core Idea¶

Holacracy is one specific constitution-based system rather than decentralization generally; version, adoption depth and distinction between role and person matter. Work is decomposed into roles with domains and accountabilities, circles govern those roles through integrative decision rules and tensions trigger iterative changes to structure. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

The load-bearing residual is not the broad topic of organization design. It is the domain-specific identity fixed by the organization and constitution version, circles and links, roles domains and accountabilities, authority allocation, governance and tactical meeting processes, tension processing, adoption scope and evidence of practice are explicit.

How would you explain it like I'm…

Role Hats Rulebook

Imagine a club where every job, like 'snack helper' or 'game picker,' is written down with exactly what it's in charge of. People take the jobs, but the job and the person are not the same thing. When something isn't working, the group meets and changes the jobs using a special rulebook. That way of running things is called Holacracy.

Roles, Circles, and Tensions

Holacracy is one particular system for running an organization, written down in a document called a constitution. Work is split into roles, and each role has clear things it's in charge of and things it must do. A person and a role aren't the same thing: one person can fill many roles. Groups called circles have special meetings to change the roles, using set rules for deciding. When someone feels a 'tension', a gap between how things are and how they could be, they bring it to the circle so the structure can be adjusted.

Constitution-Based Role Governance

Holacracy is a specific, constitution-based system for organizing a company, not just any decentralized or flat setup. Work is broken into roles, each with domains it controls and accountabilities it must carry out. A single person can fill several roles, and the role is kept separate from the person. Roles are organized into circles linked to each other, and circles change their roles through governance meetings with a structured decision process. Day-to-day coordination happens in tactical meetings. 'Tensions,' gaps between how things are and how they could be, trigger step-by-step changes to the structure. Whether an organization truly uses Holacracy depends on which constitution version it uses and how fully it practices it.

Holacracy is a particular codified system of self-management defined by a written constitution, and should not be equated with decentralization or flat organization in general. Its unit of structure is the role, specified by a purpose, domains (exclusive control) and accountabilities (ongoing expectations), and explicitly distinguished from the person or people energizing it. Roles are organized into nested circles connected by link roles, and authority is allocated through the constitution rather than through managerial hierarchy. Governance meetings use an integrative decision-making process to create, modify, or remove roles and policies, while tactical meetings handle operations. Tensions raised by role-holders drive iterative structural change. Identifying a real case requires specifying the constitution version, circles and links, role definitions, authority allocation, meeting processes, tension processing, scope of adoption, and evidence that the practice is actually followed.

Scope of Application¶

Holacracy belongs to organization design and is useful where the analyst can specify the typed organization design carrier, including objects, relations, parameters, conventions, evidence, and comparison cases, then evaluate the organization and constitution version, circles and links, roles domains and accountabilities, authority allocation, governance and tactical meeting processes, tension processing, adoption scope and evidence of practice are explicit. The scope is broad within that domain but bounded by the need for the organization and constitution version, circles and links, roles domains and accountabilities, authority allocation, governance and tactical meeting processes, tension processing, adoption scope and evidence of practice are explicit. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.

Clarity¶

The abstraction clarifies a crowded vocabulary by making the organization and constitution version, circles and links, roles domains and accountabilities, authority allocation, governance and tactical meeting processes, tension processing, adoption scope and evidence of practice are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test.

Manages Complexity¶

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Holacracy. Holacracy compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: the typed organization design carrier, including objects, relations, parameters, conventions, evidence, and comparison cases. Reject examples whose alleged carrier belongs to a different problem.
Lock the constitutive rule. Express the organization and constitution version, circles and links, roles domains and accountabilities, authority allocation, governance and tactical meeting processes, tension processing, adoption scope and evidence of practice are explicit independently of one notation or implementation.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of organization design because they reuse the typed organization design carrier, including objects, relations, parameters, conventions, evidence, and comparison cases, Work is decomposed into roles with domains and accountabilities, circles govern those roles through integrative decision rules and tensions trigger iterative changes to structure., and type the carrier, state every parameter and convention in the definition, test that the organization and constitution version, circles and links, roles domains and accountabilities, authority allocation, governance and tactical meeting processes, tension processing, adoption scope and evidence of practice are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions¶

Current abstraction Holacracy Domain-specific

Parents (1) — outgoing typed relations

Holacracy is a kind of Governance Prime

It remains its own entry because its identity is fixed by the organization and constitution version, circles and links, roles domains and accountabilities, authority allocation, governance and tactical meeting processes, tension processing, adoption scope and evidence of practice.

Hierarchy paths (2) — routes to 1 parentless root

Holacracy → is a kind of Governance → includes Accountability → presupposes Authority

Show alternative path (1)

Neighborhood in Abstraction Space¶

Holacracy sits in a crowded region of the domain-specific corpus (18^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Organizational Governance & Process Methods (46 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25