A self-management system that replaces traditional management hierarchy with a set of distributed authority rules, organizing work into roles within nested circles rather than departments with bosses.
Key Takeaways
Holacracy is a governance system that distributes authority across self-organizing circles rather than concentrating it in a management hierarchy. Created by Brian Robertson in 2007 based on his experience running software company Ternary Software, it's defined by a formal constitution that every adopting organization agrees to follow. Here's what makes holacracy different from simply "going flat": it doesn't remove structure. It replaces one type of structure (management hierarchy) with another (role-based governance with explicit rules). People don't have bosses, but they do have clearly defined roles with explicit accountabilities. Decisions aren't made by managers, but they are made through structured governance meetings with specific protocols. The system's core innovation is separating people from roles. In a traditional organization, a person is hired into a position that bundles multiple responsibilities. In holacracy, responsibilities are broken into discrete roles. One person might fill three or four roles simultaneously, and any role can be held by different people at different times. This creates flexibility, but it also creates complexity. The honest assessment from organizations that have tried holacracy is mixed. Small, knowledge-intensive firms with experienced employees often thrive with it. Larger organizations or those with less experienced workforces tend to struggle. Zappos's experience, the most high-profile implementation, showed both the promise and the pain.
Holacracy replaces familiar management concepts with its own vocabulary and mechanics. Understanding these is essential before evaluating whether the system could work for your organization.
Holacracy organizes work into circles, which are self-governing teams responsible for a specific domain. Circles nest inside each other: a Marketing Circle might contain a Content Circle and a Brand Circle. Each circle has clear authority over its domain and governs itself through its own meetings. The circle doesn't have a manager. It has several structural roles. A Lead Link (appointed by the broader circle) allocates resources and assigns people to roles within the circle. A Rep Link (elected by circle members) represents the circle's interests in the broader circle's governance meetings. A Facilitator runs meetings according to the constitution's protocols. A Secretary handles scheduling and records.
Traditional job descriptions bundle multiple responsibilities into a single position. Holacracy breaks them apart. Instead of "Marketing Manager," you might have separate roles for "Campaign Strategist," "Analytics Reviewer," "Budget Allocator," and "Vendor Relationship Holder." One person might fill all four roles, or they might be distributed across several people. Roles have three components: a purpose (why the role exists), domains (what the role has exclusive authority over), and accountabilities (what ongoing activities the role is expected to perform). Roles are created, modified, and removed through the governance process, not by management decree.
Governance meetings are where the structure itself evolves. Any circle member can propose changes to roles, domains, or policies through a structured process called Integrative Decision Making (IDM). The proposer presents a tension (something that's not working), proposes a solution, and the group processes it through rounds of clarifying questions, reactions, amendments, and an objection round. Objections must be argued as harmful to the circle's purpose, not just personal preferences. Valid objections trigger amendments. Invalid objections are overruled by the Facilitator. This is very different from consensus. You don't need everyone to agree. You need no one to have a valid, reasoned objection.
Separate from governance, tactical meetings handle the day-to-day work. They follow a strict format: check-in round, checklist review, metrics review, project updates, and a triage round where anyone can raise operational tensions and request actions from other roles. The Facilitator keeps the meeting on-protocol and on-time. Tactical meetings typically run 30-60 minutes weekly. The rigid format prevents meetings from devolving into open-ended discussions. Some people find this structure liberating (meetings actually end on time). Others find it stifling (can't have a natural conversation about a complex issue).
The contrasts are stark. Understanding them helps you assess fit for your organization.
| Dimension | Traditional Hierarchy | Holacracy |
|---|---|---|
| Authority source | Manager's position in the hierarchy | The constitution and role definitions |
| Decision-making | Manager decides, team executes | Role filler decides within their role's authority; governance meetings change structure |
| Job definition | Fixed job description, updated infrequently | Multiple roles per person, updated continuously through governance |
| Org structure changes | Top-down reorganization (often every 2-3 years) | Continuous evolution through governance proposals (weekly or biweekly) |
| Conflict resolution | Escalate to manager | Process tensions through governance or tactical meetings using defined protocols |
| Career progression | Climb the management ladder | Expand roles, take on higher-impact work (no formal promotion ladder) |
| Meeting style | Agenda varies, often unstructured | Rigidly structured with specific protocols for each phase |
| Who sets priorities | Manager assigns and prioritizes work | Each role filler prioritizes their own work based on role purpose |
Companies that successfully implement holacracy report specific advantages that traditional structures struggle to match.
In a traditional company, changing roles and responsibilities requires management approval, HR review, potentially new job descriptions and salary banding. In holacracy, a circle can create, modify, or eliminate a role in a single governance meeting. David Allen Company (the Getting Things Done organization) reports that they adapt their structure weekly in response to new information, something that would take months in a traditional hierarchy. For companies in fast-changing environments, this structural agility is significant.
Every role has explicit authority over its domain. A person filling the "Social Media Content" role doesn't need to ask a manager before posting. They have defined authority. This eliminates the bottleneck of managerial approval for routine decisions. When combined with clear accountability (the role holder is responsible for outcomes in their domain), it creates genuine ownership. People make decisions faster and take more responsibility for results because they can't defer to a boss.
Holacracy's governance process gives everyone a formal channel to raise structural problems and propose solutions. In traditional organizations, tensions often go unaddressed because there's no mechanism for a frontline employee to change organizational structure. They can complain, suggest, or escalate, but the structural change requires management action. In holacracy, anyone can propose a governance change, and if no valid objection exists, it happens. This surfaces problems that traditional structures bury.
Holacracy has vocal critics, many of whom are former practitioners. These criticisms are grounded in real experience, not theoretical objections.
Zappos, the online shoe retailer, adopted holacracy in 2014 under CEO Tony Hsieh. It was the largest and most visible implementation: 1,500 employees transitioning to self-management. Within 18 months, 29% of employees had left. Many cited confusion, frustration with the governance process, and a sense that the system created more structure than it removed. By 2020, Zappos had quietly moved away from pure holacracy toward what it called "market-based dynamics," a hybrid system. The lesson wasn't that holacracy can't work. It was that imposing it on 1,500 people with varying levels of self-direction capability and enthusiasm was asking too much.
Holacracy's constitution is prescriptive. You don't get to pick and choose which parts to follow. This "all or nothing" approach frustrates companies that want to adopt some elements while keeping others from their current system. Brian Robertson has argued that the constitution works as a whole and cherry-picking undermines it. Critics argue this makes holacracy more like a religion than a management tool. The practical reality is that many organizations adopt "holacracy-inspired" practices (circles, role-based governance) without following the full constitution.
Removing formal hierarchy doesn't eliminate power dynamics. It just makes them less visible. In holacracy, influence flows to people who are comfortable with the governance process, articulate in meetings, and skilled at navigating the constitutional rules. Introverted employees, non-native language speakers, and those less comfortable with procedural argumentation can get marginalized. Former Medium employees (the blogging platform tried and abandoned holacracy) reported that senior employees and founders retained outsized influence despite the formal equality of the system.
Holacracy's governance process is designed to process tensions about roles and structure. It's not designed to handle interpersonal conflicts, emotional dynamics, or cultural issues. The constitution explicitly scopes governance meetings to structural topics. But organizational problems are often emotional and relational, not structural. A team that doesn't trust each other can't be fixed by redefining roles. Holacracy practitioners acknowledge this gap and recommend supplementing the system with separate practices for interpersonal dynamics, but the constitution itself doesn't address it.
The adoption record reveals where holacracy tends to work and where it tends to fail.
| Company | Size | Industry | Status | Outcome |
|---|---|---|---|---|
| Zappos | ~1,500 | E-commerce/Retail | Adopted 2014, moved away by 2020 | 29% turnover; shifted to hybrid model after Tony Hsieh's passing |
| David Allen Company | ~50 | Consulting/Training | Active since 2013 | Successfully operating for 10+ years; credits holacracy with organizational agility |
| Medium | ~100 | Technology/Media | Adopted 2013, abandoned 2016 | Found it too process-heavy; returned to traditional management |
| Precision Nutrition | ~200 | Health/Education | Active since 2015 | Reports improved clarity and faster decision-making in a distributed team |
| Springest | ~80 | EdTech (Netherlands) | Active since 2014 | Successful implementation in a small, knowledge-work environment |
| HolacracyOne | ~30 | Consulting | Active (creators of the system) | Practices what it preaches; serves as the reference implementation |
Implementation is where most holacracy adoptions succeed or fail. The system requires careful rollout, not a big-bang switch.
Before committing, run a pilot with a single team or department. Have leadership study the constitution, attend a holacracy practitioner training, and honestly assess whether the organization's culture can support self-management. Key readiness indicators: employees are experienced and self-directed, leadership is genuinely willing to give up control (not just saying they are), the organization values process discipline (holacracy's meetings are highly structured), and there's tolerance for a 6-12 month learning curve where productivity will dip.
The organization formally ratifies the holacracy constitution. Existing job descriptions get translated into roles. Departments become circles. This translation isn't trivial: a "Marketing Manager" might become 8 different roles, some of which get distributed to other people. HolacracyOne recommends a certified coach to guide this phase. Most successful implementations use external facilitation for the first 6-12 months until internal facilitators develop sufficient skill.
The first 6-12 months are bumpy. People forget the meeting protocols, governance proposals are clumsy, and the temptation to revert to old habits is strong. This is normal. The governance process feels slow and awkward at first but speeds up as people internalize the protocols. Common mistakes during this phase: trying to process every issue through governance (some things are just conversations), over-defining roles (keep them minimal and evolve as needed), and former managers still acting like managers while holding different role titles.
Data on holacracy adoption, outcomes, and organizational impact.
Holacracy isn't the only self-management system. Several alternatives offer similar benefits with different trade-offs.
Sociocracy predates holacracy and uses similar circle-based structures with consent decision-making. The key difference: sociocracy is more flexible. There's no rigid constitution. Organizations adapt the principles to their context. Many practitioners consider sociocracy a better fit for organizations that want self-management without holacracy's all-or-nothing approach. The Sociocratic Circle Method is used by hundreds of organizations globally, particularly in the Netherlands, where it originated.
Some organizations create self-managing teams without adopting any formal governance system. Morning Star (tomato processing), Buurtzorg (Dutch home healthcare with 15,000 nurses in self-managing teams of 12), and Handelsbanken (Swedish bank with highly autonomous branches) all practice self-management using custom-designed systems rather than an off-the-shelf framework. The advantage is fit: each organization designs governance that matches its specific context. The disadvantage is that there's no manual. You're building the plane while flying it.
Frederic Laloux's book "Reinventing Organizations" (2014) described a new organizational model called Teal, characterized by self-management, wholeness (bringing your full self to work), and evolutionary purpose (the organization has its own sense of direction). Laloux's framework isn't a governance system like holacracy. It's a set of principles that organizations interpret differently. Patagonia, Buurtzorg, and FAVI (a French automotive supplier) are often cited as Teal-inspired organizations. The framework is useful for vision-setting but doesn't provide the operational specifics that holacracy does.