Holacracy is a management system that replaces traditional top-down hierarchy with self-organizing teams called “circles,” where authority is distributed across clearly defined roles rather than concentrated in managers. Instead of a CEO making decisions that cascade downward, each person holds one or more roles with explicit responsibilities and the authority to make decisions within those roles. The system runs on a formal written constitution that every participant agrees to follow.
How Roles Replace Job Titles
In a traditional company, you have a job description that broadly outlines what you do, and a manager who tells you what to prioritize. Holacracy replaces both of those with something more granular. Each role has three components: a purpose (the goal it exists to achieve), domains (the specific assets or processes it controls), and accountabilities (the ongoing activities expected of whoever fills that role).
One person can hold multiple roles across different circles, and roles can be reassigned as the organization’s needs shift. This is fundamentally different from a job title, which tends to be static and vaguely defined. If you’re a marketing coordinator in a traditional company, you might do everything from event planning to social media to vendor management. In a holacracy, those would likely be three separate roles, each with its own clear purpose, and potentially filled by different people.
Circles Instead of Departments
Circles function like departments, but with a key difference: they’re nested. The broadest circle, called the “Anchor Circle,” holds all the authority and domains the organization controls. Sub-circles exist within it, each responsible for a specific area of work. A Circle Lead assigns roles within that circle and can set a strategy, which is essentially a set of guidelines for how people in the circle should prioritize their work.
There is still structure and hierarchy in holacracy, but it’s organized around these circles and roles rather than around people. A Circle Lead isn’t a traditional boss. They don’t evaluate your performance or approve your vacation time. They manage the structure of work itself: which roles exist, who fills them, and what priorities guide the circle.
The Constitution That Governs Everything
What makes holacracy distinctive from other “flat organization” experiments is that it runs on a formal, written constitution. The current version (5.0) is a detailed document that spells out exactly how authority works, how decisions get made, and what obligations everyone has to each other.
When an organization adopts holacracy, its leaders formally cede their power to govern and run the organization into the rules laid out in the constitution. No implicit expectations or constraints hold any power over anyone, and no directives issued outside the constitution’s authority carry weight. This is a meaningful shift: it means a founder or executive can’t simply override a decision because they feel like it. They have to work within the system like everyone else.
The constitution also defines three duties that every participant owes to others. The duty of transparency requires you to share information about your projects, priorities, and progress when asked. The duty of processing means you must respond promptly to messages and requests from others. The duty of prioritization says you must put incoming requests and official strategies ahead of your own personal preferences for how to spend your time.
How Decisions Get Made
Holacracy uses two distinct types of meetings, each with a specific purpose and a tightly controlled format.
Governance meetings exist to change the organization’s structure: creating, modifying, or removing roles, circles, and policies. These meetings follow a process called Integrative Decision Making. Someone identifies a “tension,” which is a gap between how things are and how they could be. They propose a change to resolve it. The group reacts (this is the one step where people can speak freely). Then the proposer can amend their proposal based on those reactions. The group tests for objections, and if no valid objection exists, the proposal passes. You don’t need consensus or majority approval. You just need the absence of a reason the proposal would cause harm.
Tactical meetings, by contrast, deal with day-to-day operational work: syncing on projects, removing obstacles, and coordinating across roles. Both meeting types begin with a check-in round where each person speaks without discussion, and both build their agenda at the start of the meeting rather than in advance.
This structure means meetings can feel slow, especially at first. Participants have to hold back comments and wait for the right step in the process. But the rigidity is intentional: it prevents conversations from spiraling into open-ended debates and keeps each item focused on a specific tension.
Authority and Its Limits
As a role lead, you have the authority to take any action or make any decision that serves your role’s purpose or accountabilities, as long as you don’t break the rules in the constitution. That’s a broad grant of power, but it comes with clear guardrails.
You can’t violate policies set by circles that contain your role. You can’t impact a domain controlled by another role or circle without permission. And you can’t spend money or assets without authorization from whoever controls those resources. These constraints prevent the system from devolving into chaos while still giving individuals far more decision-making power than they’d have in a traditional hierarchy.
There’s also an escape valve for urgent situations. If acting strictly within your role’s authority would mean losing significant value because you had to wait for permission or a governance change, you can step outside your role’s boundaries. But only if you’re acting in good faith, the action resolves more tension than it creates, and it doesn’t commit the organization to unauthorized spending.
What Happened at Zappos
The most prominent real-world test of holacracy came at Zappos, the online shoe retailer. CEO Tony Hsieh adopted the system company-wide, making it the largest holacracy implementation at the time. The results were mixed. Employees found that meetings dragged on, roles overlapped, and the process felt heavier than what it replaced. The experiment, as Forbes described it, “promised too much, carried too much process and broke under its own weight.”
Zappos’ experience became a cautionary reference point for other organizations considering the system. But it also revealed something useful: the problems weren’t necessarily with the principles of distributed authority. They were with the overhead of implementing a rigid constitutional framework across a large, established company with deeply ingrained habits.
Why Adoption Is Difficult
Even organizations that are enthusiastic about holacracy tend to hit the same friction points during the transition. People who spent their careers in traditional hierarchies often struggle to act with genuine independence, even when they’re told they now have authority. The reflex to check with a boss before making a decision doesn’t disappear overnight.
On the flip side, former executives face the opposite challenge: learning to let go. People who used to fill leadership positions need to step back, take an observer’s role more often, and allow decisions to emerge from the system rather than directing them. Letting go of consensus is also surprisingly hard. The holacracy process doesn’t require buy-in from everyone, but teams accustomed to collaborative decision-making find it uncomfortable to move forward when not everyone agrees.
Role discipline is another ongoing challenge. When people get absorbed in a project, they sometimes lose focus on the specific roles they hold and the purposes those roles are meant to serve. The system depends on everyone staying within their defined accountabilities, and that requires constant attention in a way that traditional job descriptions, however vague, don’t demand.
Who Holacracy Works For
Holacracy tends to fit best in small to mid-sized organizations where adaptability matters more than predictability. Startups, consultancies, and mission-driven organizations have been the most common adopters, partly because they have less institutional inertia to overcome and partly because the system’s emphasis on purpose-driven roles aligns with how these organizations already think about work.
Larger organizations sometimes adopt holacracy principles selectively, taking the role clarity and meeting structures without committing to the full constitutional framework. This hybrid approach sidesteps some of the implementation pain while capturing the parts of the system that employees and leaders find most valuable: clearer accountability, faster decision-making within defined boundaries, and fewer bottlenecks caused by waiting for managerial approval.