What is Holacracy?
Holacracy is a self-management operating system that replaces a traditional management hierarchy with a structure of self-organizing circles. Authority is distributed to clearly defined roles instead of job titles, and roles update through a written governance process. Brian Robertson introduced the model in 2007 and codified it in the Holacracy Constitution.
- Authority sits in roles, not people: Holacracy assigns decision rights to written roles inside circles, so power moves with the work rather than with promotions.
- Governance is a written process: Roles, accountabilities, and policies change through structured governance meetings, not informal management decisions.
- Tactical work runs separately: A second meeting cadence handles day-to-day operations so governance does not get hijacked by status updates.
- Real adoption is narrow: Under 1,000 organizations practice formal Holacracy, and high-profile rollouts at Zappos and Medium show the operating cost is real.
Definition: Holacracy is a method of decentralized management and organizational governance in which authority and decision-making are distributed throughout a self-organizing team, rather than being vested at the top of a hierarchy.
Where Holacracy came from
Brian Robertson developed Holacracy at his software company Ternary Software between 2001 and 2007, then spun off HolacracyOne to license the method and publish the Holacracy Constitution. The term comes from the Greek "holon," coined by Arthur Koestler to describe an entity that is both a whole and a part of a larger whole.
Robertson positions Holacracy as a way to build agile, responsive organizations by distributing authority across roles rather than tying it to individuals.
The four building blocks of a Holacracy system
A Holacracy operating system has four moving parts, each with a precise definition in the Constitution. Together they replace the work that managers normally do informally.
- Roles. Energized work is broken into clearly defined roles, each with a purpose, domains it controls, and accountabilities. People fill multiple roles and can be reassigned without a title change.
- Circles. Roles are grouped into circles, each a semi-autonomous team with its own purpose and the authority to govern itself. Circles nest inside broader circles, forming a holarchy.
- Governance meetings. A structured meeting cadence where circle members propose changes to roles, accountabilities, and policies through integrative decision making. Objections must point to actual harm, not personal preference.
- Tactical meetings. A separate cadence focused on operational work: checking metrics, processing tensions about projects, and triaging next actions. Keeping tactical and governance separate is the part most teams skip and most teams later regret.
How governance actually changes a role
In a traditional org, changing a job description is a closed-door manager decision. In Holacracy, anyone in a circle who senses a tension (a gap between what is and what could be) can propose a governance change.
The Lead Link cannot veto on personal preference. The Facilitator runs a fixed-script process where the proposal is tested for objections, integrated, and either adopted or rejected.
The output is captured in writing (GlassFrog is the canonical tool) so the next person who fills the role inherits the same definition. This is the part of Holacracy that gets called "rigid": every change is visible, and personal influence stops mattering as much as written authority.
Holacracy versus other flat structures
Holacracy is often lumped together with "flat" or "self-managed" structures, but the differences matter when picking a model. The table below shows where Holacracy lands against three alternatives a CEO would actually compare it against.
Dimension | Traditional Hierarchy | Flat Organization | Sociocracy | Holacracy |
|---|---|---|---|---|
Authority sits with | Managers | Senior leadership, often informally | Circle members via consent | Written roles within circles |
How rules change | Manager decision | Ad-hoc | Consent decision making | Integrative decision making per Constitution |
Role definition | Job title | Often fluid | Defined per circle | Strictly written, versioned |
Meeting structure | Variable | Variable | Defined consent process | Defined governance and tactical cadence |
Codified rulebook | None | None | Sociocratic principles, multiple variants | Holacracy Constitution v5.0 |
The cleanest one-line difference: Sociocracy gives you principles, Holacracy gives you a rulebook. That is also the trade-off. The rulebook removes ambiguity but adds operating cost.
When Holacracy rollouts typically break
Most failed implementations do not fail because the Constitution is wrong. They fail at predictable seams.
- The Constitution is treated as optional. Teams adopt circles and roles but skip the governance process. Within a quarter, the lead link starts making manager-style decisions and the system collapses back to hierarchy with extra paperwork.
- Tactical creep into governance. Without a strict facilitator, governance meetings drift into project status. Real role changes stop happening, and people lose faith in the system.
- Performance, pay, and firing live outside the model. Holacracy governs work, not employment. Compensation and termination decisions still need a separate process. Companies that forget to design one end up with shadow hierarchy.
- Senior leaders cannot let go of veto power. The model only works if the CEO accepts the Constitution above their own authority. Robertson himself has said this is the most common failure mode, and Zappos' rollout under Tony Hsieh is the canonical case study.
Zappos remains the most cited Holacracy case. After CEO Tony Hsieh offered buyouts to employees who did not want to operate under the new system, 18% of Zappos' 1,500 staff took the offer by January 2016 (Washington Post, 2016). Zappos eventually moved to a hybrid "Market-Based Dynamics" model that kept circles but reintroduced budgets and P&L accountability.
Adoption is narrower than the press suggests
HolacracyOne's published directory lists more than 200 verified Holacracy-powered organizations worldwide (HolacracyOne, 2024), with academic sources citing roughly 1,000 organizations using some form of the model. That is a small adoption base for a framework that has been in the press since 2014.
The pattern that does work: small-to-mid software companies, consultancies, and intentionally self-managed firms where the founder is committed to ceding personal authority. Large enterprises that have tried Holacracy at scale (Zappos, Medium) have either pulled back or hybridized the model.
When to choose Holacracy over a lighter model
Pick Holacracy when three conditions hold at once: leadership is willing to be governed by a written constitution, the team is small enough to absorb the meeting cadence (typically under 200 people, or in a self-contained division), and the work is knowledge work where role boundaries genuinely shift.
If even one condition is missing, lighter approaches like the Spotify model, a teal organization operating principle, or a decentralized authority pattern layered onto a traditional org chart will deliver more of the benefit at a fraction of the operating cost.
Pair any of these with strong organizational alignment practices, OKRs, and servant leadership habits and you capture most of what people actually want from Holacracy: clearer authority, faster decisions, and roles that match the work.
