Holacracy¶

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

Version: v1 · 2026-09-08 · History
Domain-specific #: 4896
Origin domain: organization design
Subdomain: organization design

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.

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. 2. 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) — more general patterns this builds on

Holacracy is a kind of Governance Prime

The proposed strict upward parent is prime:governance.

Hierarchy paths (2) — routes to 1 parentless root

Holacracy → Governance → Accountability → Authority

Show alternative path (1)

Neighborhood in Abstraction Space¶

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

Family — Engineering Design & Requirements (47 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08