Holacracy is a system of organizational governance that replaces a traditional top‑down management hierarchy with a set of distributed, autonomous teams (called circles) and formally defined roles. Instead of fixed job descriptions tied to a single reporting line, people hold multiple roles with specific accountabilities and domains of authority. Decision‑making authority is pushed to the role level: role leads can act freely to fulfill their accountabilities “as long as there’s no rule against it” — a principle often called holacracy’s “golden rule.” (HolacracyOne; Holacracy Constitution v.5.0)
Key takeaways
– Structure: Organizations are organized as nested circles (autonomous teams) rather than a pyramid. (HolacracyOne)
– Roles: Individuals can hold multiple roles; each role has purpose, accountabilities and domains. (Holacracy Constitution)
– Governance: Circles hold regular governance meetings to create, amend or remove roles and rules. Tactical meetings handle day‑to‑day operations. (HolacracyOne)
– Authority: Authority is distributed to roles, not to people via a single manager, which speeds local decision making. (Holacracy.com; Zappos)
– Adoption: Some high‑profile tech and service organizations have experimented with holacracy (e.g., Zappos), but critics warn it can be hype and may not suit every culture. (Zappos; Harvard Business Review; Medium)
How holacracy works — core components
– Circles and nesting: Work is grouped into circles that are semi‑autonomous. Circles can contain sub‑circles, forming a nested structure that mirrors the organization’s domains of work. (HolacracyOne)
– Roles: Each role has a clear purpose, accountabilities (what the role must deliver) and domains (areas the role controls). One person can fill several roles across circles. (Holacracy Constitution)
– Governance meetings: Circles meet periodically in structured governance sessions to propose, test, and adopt role changes and rules. Conflicts about roles or domains are resolved in these meetings using defined processes. (HolacracyOne)
– Tactical meetings: Separate, structured tactical meetings focus on operations: project updates, blocking issues, prioritization and short‑term planning. (HolacracyOne)
– Tensions: A “tension” is any gap between current reality and a potential improvement. Holacracy treats tensions as inputs for governance — people raise and process them in meetings. (HolacracyOne)
– Constitution: Holacracy implementations often adopt a written “Holacracy Constitution” that defines the process rules, meeting formats and authority allocation. (Holacracy Constitution v.5.0)
Origin and evolution
– The word holarchy comes from Arthur Koestler’s concept of holons — units that are whole and part of a larger whole. (Koestler, The Ghost in the Machine)
– Brian Robertson developed the operational system now called Holacracy while running Ternary Software in the early 2000s. He co‑founded HolacracyOne with Tom Thomison in 2007 and published the Holacracy Constitution a few years later. (Holacracy.com; HolacracyOne)
Fast fact
– The largest company to publicly adopt holacracy at scale is Zappos, an online retailer that reported more than 1,500 employees when it moved toward holacracy. (Zappos)
– HolacracyOne lists roughly 185 organizations that have publicly adopted holacracy principles; adoption outcomes are mixed and several organizations later changed course. (HolacracyOne; Harvard Business Review)
Examples of holacracy adoption (and lessons)
– Zappos: Adopted holacracy publicly and used it to accelerate local decision making and surface customer feedback. The transition was highly disruptive: about one in five employees accepted severance rather than continue after the change, and many cited holacracy as a reason. (Zappos; Zappos Insights)
– Liip, Springest, Mercedes‑benz.io: Smaller firms and digital agencies that have implemented holacracy or elements of it. (HolacracyOne)
– Cases of rollback: Medium adopted holacracy in 2013 and moved away from it around 2016, explaining that the system had begun to “get in the way of work.” This underlines that holacracy can create friction if the process outpaces the organization’s readiness. (Medium; Harvard Business Review)
Special considerations and critiques
– Cultural fit: Holacracy requires a culture comfortable with high transparency, disciplined meeting processes and role fluidity. Firms with rigid hierarchies or low psychological safety may struggle. (Harvard Business Review)
– Implementation difficulty: The formal processes and meeting discipline can feel bureaucratic and time‑consuming. Critics call it a buzzword that can be overhyped if not thoughtfully adopted. (Harvard Business Review)
– Talent and HR systems: Conventional HR practices (job grades, promotion ladders, performance reviews and compensation) may need redesign to align with role‑based authority. Legal and compliance frameworks also must be reviewed. (HolacracyOne; Zappos)
– Employee attrition: Expect turnover during transition; some employees will prefer conventional structure. (Zappos)
– Not a one‑size‑fits‑all: Many organizations combine holacratic practices with traditional management elements rather than adopting Holacracy “by the book.” (Harvard Business Review)
Practical steps to adopt holacracy (step‑by‑step)
Prepare and assess
1. Assess readiness and goals
• Clarify why you want holacracy (speed of decision making, innovation, empowerment).
• Evaluate company culture — openness, learning orientation, conflict resolution skills and tolerance for ambiguity.
• Identify legal, HR and compliance constraints.
2. Educate leadership and employees
• Run workshops explaining the holacracy philosophy, roles, circles, governance and tactical meeting formats.
• Share the Holacracy Constitution and basic mechanics so people know what to expect. (Holacracy Constitution v.5.0)
Pilot and design
3. Start with a pilot circle or department
• Pick a unit where autonomy would yield clear benefits and risks are manageable.
• Appoint a facilitator or coach experienced in holacratic practice. External coaches can accelerate learning. (HolacracyOne practitioner stories)
4. Map work and create initial role definitions
• Define circles, sub‑circles and initial roles (purpose, accountabilities, domains).
• Allow role descriptions to be concise and mutable — they will evolve through governance meetings.
Implement process
5. Adopt governance and tactical meeting rhythms
• Schedule regular governance meetings to evolve roles and policies.
• Schedule shorter, frequent tactical meetings to handle daily operations, metrics and blockers.
• Use explicit meeting templates and tension‑processing protocols to keep meetings productive. (HolacracyOne)
6. Train everyone on meeting protocols and tension processing
• Teach specific facilitation roles (facilitator, secretary, lead link) and meeting scripts.
• Model how to surface tensions and propose safe experiments.
Integrate with people systems
7. Align HR and compensation systems
• Redesign job architecture: roles are defined by accountabilities rather than job titles.
• Decide how pay and rewards will reflect role responsibilities, multi‑role contributions and career development.
• Define hiring and onboarding processes that explain role fluidity and expectations.
8. Legal and compliance review
• Ensure contracts, reporting lines, statutory responsibilities and employment law obligations are honored. Some jurisdictions require a clearly accountable legal officer or manager. (Consult legal counsel)
Scale and iterate
9. Evaluate, collect feedback and iterate
• Track metrics: decision speed, cycle time for governance changes, employee engagement, turnover, customer outcomes.
• Use retrospectives and surveys to find friction points (meeting overload, unclear domains, misaligned incentives).
10. Expand or adapt the model
• Based on results, scale holacracy practices to other circles, adjust the degree of formality, or hybridize with traditional structures where necessary. Be explicit about trade‑offs. (Harvard Business Review; Medium)
Practical checklist for the first 90 days
– Week 1–2: Leadership alignment workshop; choose pilot area.
– Week 3–4: Train pilot team in roles, circles and meeting formats. Adopt or draft a simple governance constitution.
– Month 2: Begin weekly tactical meetings and biweekly governance sessions. Coach facilitation.
– Month 3: Review tensions processed, role changes made, and employee feedback. Adjust cadence and expand next circle.
Measuring success
– Operational metrics: Decision lead time, number of governance proposals processed, project throughput.
– People metrics: Engagement scores, voluntary turnover, internal mobility across roles.
– Customer metrics: Speed of responding to customer feedback, NPS, retention.
– Qualitative feedback: Ease of getting decisions made, clarity of accountabilities, meeting effectiveness.
When holacracy may not be right
– Highly regulated industries where clear, legal reporting lines are mandatory may find holacracy hard to reconcile with compliance needs.
– Organizations needing rapid, centralized crisis decisions may prefer a temporary command structure.
– Companies with low tolerance for ambiguity or weak internal facilitation skills may find holacracy’s process overhead onerous.
Further reading and primary sources
– HolacracyOne — Holacracy Constitution (v.5.0) and practitioner resources. (HolacracyOne; Holacracy Constitution)
– Holacracy.com — History and how the system works. (Holacracy.com)
– Zappos — How We Work / Zappos Insights (Zappos; Zappos Insights)
– Harvard Business Review — “Beyond the Holacracy Hype” (discussion of benefits and limits). (Harvard Business Review)
– Medium — “Management and Organization at Medium” (postmortem of a holacracy experiment). (Medium)
Bottom line
Holacracy is a formalized approach to distributing authority and clarifying responsibilities through roles and nested circles. It can speed decisions, increase employee autonomy and surface operational tensions quickly — but it demands disciplined processes, cultural readiness and careful integration with HR, legal and performance systems. Pilot deliberately, measure results, and be prepared to adapt the degree of formalization to your organization’s needs.