Holacracy

A self-organizing management system that replaces hierarchical structures with a network of circles and roles with distributed authority.

Category:Agile Methods

Holacracy is a comprehensive management and governance system that replaces traditional hierarchical organizational structures with a decentralized network of self-organizing teams. It was developed in 2007 by Brian Robertson and became known through companies such as Zappos, Medium, and Springest.

Core Principles of Holacracy

Holacracy is based on several core principles that together form a coherent leadership system:

  • Distributed Authority: Decision-making powers are distributed from central leadership positions to all organizational members, so that authority resides where the corresponding knowledge and expertise also exists.
  • Roles Instead of Positions: Instead of fixed job descriptions, Holacracy defines dynamic roles with clear domains, accountabilities, and authorities that can be flexibly assumed by people.
  • Circle Structure: The organization is structured into self-organizing teams (circles) that can be nested and autonomously coordinate specific areas of work.
  • Transparent Rules: A clear set of rules (the Holacracy Constitution) defines how decisions are made and how governance processes operate.
  • Tension Orientation: Organizational improvements are driven by recognizing and processing "tensions" – discrepancies between current reality and potential ideal state.

Core Elements of Holacracy

Roles

In Holacracy, people do not work in jobs but fill one or more clearly defined roles. Each role has:

  • A Purpose: The specific objective of the role
  • Domains: Things over which the role has exclusive control
  • Accountabilities: Ongoing activities for which the role is responsible

A person can hold multiple roles, and a role can be shared by multiple people.

Circles

Circles are self-organizing teams with:

  • A defined purpose and accountabilities
  • Nested structure (circles within circles)
  • Special linking roles between circles:
    • Lead Link: Represents the needs of the parent circle
    • Rep Link: Represents the perspectives of the circle in the parent circle
    • Facilitator: Leads meetings according to Holacracy rules
    • Secretary: Manages records and governance documentation

Meetings

Holacracy uses specific meeting formats with clear structures:

  • Governance Meetings: Roles and policies are defined and adjusted here – they clarify the "who" and "how" of work.
  • Tactical Meetings: Operational meetings for synchronizing the team, sharing metrics, identifying projects, and resolving obstacles.

Both meeting types follow a structured process that ensures all voices are heard and effective decisions are made.

Comparison of Organizational Models

Aspect
Hierarchy
Scrum
Holacracy
Organizational Structure
Pyramid with command-and-control chain
Project-oriented teams with fixed roles
Nested circles with distributed authority
Decision-Making
Top-down
Partially self-organized, but with Product Owner as decision-maker
Fully decentralized according to clear rules
Scope of Application
Entire organization
Primarily for project work and product development
Entire organization, including administration
Adaptability
Often slow due to approval processes
Fast within sprints, limited at product level
Fast at all levels through distributed decision-making authority
Work Roles
Fixed job descriptions
Few defined roles (PO, SM, Team)
Dynamic, evolutionary roles without limit
Meetings
Often unstructured or heavily controlled
Structured cyclical events (Sprint Planning, Review, Retro)
Highly structured governance and tactical meetings
Transparency
Often limited, information flows vertically
High within the team, limited beyond
Full transparency of structure and processes
Iterations
Rare, usually in larger reorganizations
Regular iterations through sprints (1-4 weeks)
Continuous evolution through ongoing governance

The Adoption Process

Introducing Holacracy into an organization is a profound change that typically encompasses the following phases:

  1. Preparation and Training: Fundamental understanding of Holacracy principles and practices
  2. Ratification of the Constitution: Formal transfer of power from management to the process
  3. Initial Structuring: Definition of the initial circle structure and core roles
  4. Implementation of Practices: Gradual introduction of governance and tactical meetings
  5. Continuous Evolution: Ongoing adaptation of the structure through the governance process

Many organizations choose a staged approach, starting with individual teams or departments and then scaling gradually.

Advantages and Challenges

Advantages

  • Increased agility and adaptability
  • Greater autonomy and employee engagement
  • Clearer accountability and transparency
  • Reduced political power struggles
  • Faster decision-making processes
  • Promotion of innovation and entrepreneurial thinking

Challenges

  • Steep learning curve for new practices
  • Cultural resistance to authority distribution
  • Initial productivity losses during the transition
  • Higher demands on self-management
  • Possible over-structuring of simple processes
  • Integration with existing legal and financial structures

Holacracy at Elasticbrains

Elasticbrains implemented Holacracy in 2022 as an evolutionary step in organizational development. As an already fully agile company, we had previously worked exclusively with agile teams and processes such as Scrum and Kanban. However, we found that many internal company processes did not fit optimally into these frameworks. After an intensive search for a suitable organizational model, we decided on Holacracy to make these processes more effective as well.

As part of the implementation, several team members were trained in Holacracy step by step and took on important roles such as Facilitator and Secretary. This methodical evolution enables us today to manage both internal processes and client projects with the highest flexibility and transparency.

Conclusion

Holacracy is not a silver bullet, but a powerful framework for organizations seeking greater agility, transparency, and distributed decision-making. As an evolutionary operating system for organizations, it offers a structured path to transition from traditional, hierarchical structures to a more dynamic, self-organizing system. The willingness to continuously adapt and learn is the key to success.

International Adoption & Variants

Holacracy gained significant traction in North America and Western Europe among tech startups and progressive enterprises (Zappos, Buffer, Medium). However, adoption varies by culture: US companies embrace Holacracy's decision-speed benefits; German/Nordic organizations adapt it to existing works councils and labor laws; Japanese companies struggle with the explicit conflict-processing aspect (contrary to consensus-seeking norms). British and Australian firms often hybrid Holacracy with Agile frameworks. Global organizations frequently use Holacracy core principles selectively – circles and role definition – without full governance ceremonies, due to the implementation complexity across time zones.

Holacracy in Distributed, Multi-Timezone Teams

Governance meetings (quarterly Governance, regular Tactical) are challenging across time zones spanning 12+ hours. Successful implementations record detailed decisions and use asynchronous resolution where possible. Role clarity (Purpose, Accountabilities, Domains) actually reduces real-time coordination needs – team members in different zones operate independently within their role boundaries. For international teams, Holacracy's explicit process documentation is an advantage over ad-hoc hierarchies; however, the front-loaded training investment (3–6 months) is higher in multilingual, multicultural settings.

FAQ for English-speaking Organizations

How does Holacracy compare to flat hierarchies or distributed authority without formal governance?
Holacracy adds explicit rules and processes (Governance meetings, Tactical meetings, clear role evolution). Flat teams are often more creative but slow on decisions and accountability. Holacracy trades some flexibility for decision clarity – useful at scale (30+ people), risky for small teams (<10) where overhead may stifle.
Can we implement Holacracy across multiple offices in different countries with different labor laws?
Yes, but adapt carefully. US offices can go full Holacracy; German offices must respect works councils; UK offices can layer Holacracy on top of standard employment contracts. Core benefits (circles, transparent roles) survive; governance ceremonies may need simplified versions.
Is Holacracy compatible with Agile (Scrum, Kanban)?
Yes – many teams use Agile methods within Holacracy circles. The frameworks operate at different levels: Holacracy handles organizational roles and governance; Scrum/Kanban handle sprint execution. Combined, they're powerful; alone, Holacracy without workflow methodology can feel process-heavy.

More Glossary Terms