Scaling Holacracy: From Startup to Enterprise

Holacracy scales differently than traditional hierarchies—and that’s both its strength and its challenge. While classical organizations grow by adding management layers, Holacracy uses circles as the scaling unit. This structure has natural limits and requires specific adaptations as organizations grow from 20 to 200 or 2,000 employees.

Research shows: Holacracy can work in large organizations, but not through simple “more of the same.” Zappos with over 1,500 employees and Mercedes-Benz.io as a corporate subsidiary demonstrate two different scaling strategies—with different results [1, 2].

When Scaling Problems Emerge

The Complexity Thresholds

Organizational science research identifies specific thresholds where coordination problems increase dramatically [3]:

Employee Count	Challenge	Holacracy Response
~50	Informal communication no longer sufficient	First circle formation necessary
~150	Dunbar number reached—personal relationships overwhelmed	Sub-circles and clear accountability
~500	Coordination between areas breaks down	Systematic use of cross-links
~1,500	Governance load explodes	Async governance, facilitator capacity

Research Insight: A study on “conflict-free organizational scaling” shows that non-hierarchical growth is possible but requires “limited hierarchical growth”—the circle structure fulfills exactly this function [4].

The Communication Network Problem

As size increases, communication network complexity grows exponentially. Research on self-organized companies shows: Formal structure must adapt to informal communication, not the other way around [5].

In traditional hierarchies, each management layer filters information. This reduces complexity but also speed and quality.

In Holacracy, information flows through roles and circles. This maintains speed, but without clear structuring, information overload quickly overwhelms.

The Zappos Experience: 1,500+ Employees

What Worked

Zappos implemented Holacracy in 2013 as one of the largest companies ever. The experiences, documented in several academic studies [1, 6], show:

Successes:

• Faster adaptability to market changes
• Higher ownership in operational roles
• Clearer accountabilities (who is responsible for what)
• Reduced bureaucracy in decision-making

What Struggled

Challenges:

• Turnover: 14-18% voluntary departures after implementation—well above industry average [2]
• Governance load: At 1,500+ employees and hundreds of circles, meeting times exploded
• Learning curve: New employees needed 6-12 months to understand the system
• Cultural fit: Not all existing employees could or wanted to adapt

Zappos’ Conclusion

Zappos hasn’t abandoned Holacracy but has significantly adapted it. The key lesson: The constitution is a starting point, not an endpoint. Every company must develop its own adaptations for scaling.

The Mercedes-Benz.io Strategy: Greenfield Approach

A Different Path

Mercedes-Benz.io, the 100% digital subsidiary of the automotive group, chose a fundamentally different approach [2]:

1. Greenfield instead of transformation: Don’t rebuild existing organization, build new
2. Limited size: Deliberately staying smaller than classic corporate units
3. Shielding: Clear boundary between Holacracy organization and traditional corporation
4. Selective integration: Interfaces to parent company through defined roles

Why This Approach Works

Research shows: Mercedes-Benz.io avoided the biggest scaling problems by intentionally keeping the organization smaller and reducing transformation burden. Instead of transforming 30,000 employees, a new unit with Holacracy DNA was built.

Trade-off: This approach doesn’t scale the organization; it scales Holacracy alongside the existing organization.

Structural Adaptations for Scaling

1. Super-Circle Architecture

With increasing size, the super-circle/sub-circle structure becomes critical:

Anchor Circle
├── Business Development Circle
│   ├── Sales Sub-Circle
│   └── Marketing Sub-Circle
├── Product Circle
│   ├── Engineering Sub-Circle
│   └── Design Sub-Circle
└── Operations Circle
    ├── Finance Sub-Circle
    └── People Sub-Circle

Design Principles:

• Each circle should have 5-15 roles (coordination limit)
• Sub-circles emerge when work becomes too complex internally
• Super-circles retain only strategic responsibility

2. Systematic Cross-Link Usage

Cross-links are essential for scaling. They connect circles without adding hierarchical layers:

Use Case	Cross-Link Design
Customer projects touch multiple circles	Customer Success → Engineering, Design
Compliance requirements	Legal Compliance role in all relevant circles
Resource sharing	People Operations link in delivery circles

3. Anchor Circle Design

The Anchor Circle is the scaling bottleneck. In large organizations it should:

• Be minimally staffed: Only strategic roles
• Delegate, not decide: Push authority to sub-circles
• Meet sparingly: Monthly, not weekly

Managing Governance Load

The Meeting Problem

With 100 circles and monthly governance meetings, that’s 100+ meetings. Facilitators serving multiple circles spend most of their time in meetings.

Solution Approaches:

1. Asynchronous governance: Async Holacracy for standard proposals
2. Adjust meeting frequency: Not every circle needs monthly governance
3. Facilitator pool: Shared facilitators across multiple circles

Facilitator Capacity Planning

Rule of thumb for large organizations:

Organization Size	Recommended Facilitator Capacity
50-100 employees	2-3 trained facilitators
100-500 employees	5-10 facilitators, 2-3 senior
500+ employees	Dedicated facilitator role or circle

Research on Scaling

A systematic analysis of enterprise agility shows that successful scaling requires “systematic bundling” of different approaches [3]:

1. Structural adaptation: Adapt circle hierarchy to communication flows
2. Cultural support: Change management parallel to structure
3. Technical support: Governance tools for transparency
4. Leadership development: Lead Links as key roles

Research Insight: Organizations that combine multiple scaling mechanisms have higher success rates than those relying on a single approach [3].

What “Holacracy Doesn’t Scale” Really Means

The statement “Holacracy doesn’t scale” is both right and wrong:

Right: Holacracy in its basic form (constitution + standard meetings) hits limits at 200-500 employees.

Wrong: With structural adaptations—super-circles, cross-links, async governance, facilitator capacity—Holacracy can work with thousands of employees.

The real question: Is the effort for these adaptations justified? That depends on goals:

If your goal is…	Then Holacracy scaling is…
Rapid adaptability	Probably worthwhile
Cost reduction through less management	Unclear—coordination costs differently
Employee empowerment	Possible, but culture-dependent
Simplicity	Not the right approach

SI Labs Perspective

After supporting multiple scaling attempts, we see:

1. Greenfield is easier than transformation: Build new units with Holacracy rather than transform existing ones
2. Not everything needs to scale: Sometimes the answer is keeping Holacracy in parts of the organization, not everywhere
3. Facilitator investment pays off: Underestimated success factor
4. Patience: 18-24 months until stable scaling

---

Sources

[1] Bernstein, Ethan, et al. “Holacracy – the Future of Organizing? The Case of Zappos.” Human Resource Management International Digest 26, no. 4 (2018): 35-38. DOI: 10.1108/hrmid-08-2018-0161 [Case study | N=1,500+ | Citations: 27]

[2] Velinov, Emil, Zoran Todorović, and Janez Damij. “How Mercedes-Benz Addresses Digital Transformation Using Holacracy.” Journal of Organizational Change Management 34, no. 5 (2021): 1125-1150. DOI: 10.1108/jocm-12-2020-0395 [Case study | Qualitative interviews | Citations: 23]

[3] Dikert, Kim, et al. “Scaling Agile on Large Enterprise Level – Systematic Bundling and Application of State of the Art Approaches for Lasting Agile Transitions.” Proceedings of the 2019 Federated Conference on Computer Science and Information Systems (2019): 1009-1016. DOI: 10.15439/2019f150 [Systematic analysis | Enterprise context | Citations: 7]

[4] Davis, Gerald F., and Adam J. Cobb. “Scaling Nonhierarchically: A Theory of Conflict-Free Organizational Growth with Limited Hierarchical Growth.” Strategic Management Journal 44, no. 9 (2023): 2203-2229. DOI: 10.1002/smj.3541 [Theory building | Scaling principles | Citations: 6]

[5] Reitzig, Markus, and Boris Maciejovsky. “Changes in Formal Structure Towards Self-Managing Organization and Their Effects on the Intra-Organizational Communication Network.” Journal of Organization Design 12 (2023): 53-65. DOI: 10.1007/s41469-023-00143-z [Empirical study | Communication networks | Citations: 12]

[6] Groth, Aimee, and Stephen Robbins. “Evaluation of Implementing Holacracy: A Comprehensive Study on Zappos.” International Journal of Business and Management 12, no. 5 (2017): 1-12. [Evaluation study | N=1,500+ | Citations: 8]

---

Research Methodology

This article synthesizes insights from 6 academic studies from our research database of over 655 papers on self-organization. Studies were selected based on relevance for enterprise scaling and methodological rigor.

Limitations: Large-scale Holacracy deployment is rare. The evidence base relies heavily on Zappos and a few other large implementations. Generalizability is limited.

---

Disclosure

SI Labs has not itself transformed an organization with over 500 employees to Holacracy. Our scaling experience comes from smaller implementations and supporting parts of larger organizations. This perspective informs our assessment of practical challenges.