Pilot Programs in Holacracy: Testing Before Full Rollout

Pilot programs can be a sensible intermediate step in Holacracy implementation. Instead of transforming the entire organization at once, you test the system with a single circle first. This way you can learn, make mistakes, and adjust before the whole organization is affected.

But pilots also have disadvantages. They can create friction between the pilot circle and the rest of the organization. They can become a permanent state because nobody dares the full rollout. And they can create a false picture of Holacracy because the pilot circle works under unrealistic conditions.

This article helps you decide whether a pilot makes sense for your organization, and how to execute it successfully.

When a Pilot Makes Sense

Large Organizations (>100 employees)

In large organizations, a big-bang rollout is risky. A pilot enables:

• Gradual learning
• Identification of adaptation needs
• Building internal expertise before the broad rollout
• Reducing risk of failure

Research Insight: Change management research on flexible organizational structures shows: Phased rollouts reduce initial risk but extend total transformation time by an average of 40%. The optimal strategy depends on organization size. For organizations over 50 employees, experts typically recommend a pilot-based approach; for smaller organizations, a direct rollout. [1]

Skeptical Leadership

If leadership isn’t fully convinced yet, a pilot can serve as proof:

• Shows whether Holacracy works in your context
• Reduces perceived risk for leadership
• Creates internal success stories and ambassadors

Cultural Uncertainty

If you’re unsure whether the organizational culture is ready:

• Pilot provides insight into cultural barriers
• Enables culture work parallel to the pilot phase
• Shows what support employees need

Complex Dependencies

If your organization has many external dependencies (regulatory requirements, strong customer integration):

• Pilot shows where adaptations are needed
• Enables testing compatibility
• Provides time for stakeholder communication

When a Pilot Doesn’t Make Sense

Small Organizations (<30 employees)

In small organizations, the disadvantages outweigh:

• Friction between pilot and rest is relatively larger
• The pilot is a significant part of the organization
• Big-bang is usually simpler and more effective

When a Pilot Becomes a Hiding Place

Sometimes “let’s do a pilot first” is code for “we don’t want to commit”:

• If leadership hopes the pilot will fail
• If the pilot runs indefinitely
• If nobody has a rollout plan after the pilot

In these cases, address the commitment problem first.

When the Pilot Circle Is Too Isolated

A pilot that has no interaction with the rest of the organization isn’t representative:

• Learnings aren’t transferable
• The pilot works under unrealistic conditions
• Cross-functional problems don’t become visible

Choosing the Right Pilot Circle

Choosing the pilot circle is critical. The wrong circle can doom the pilot even if Holacracy would work in principle.

Ideal Properties

Size: 5-10 people

• Large enough for real governance dynamics
• Small enough for manageability
• Representative of typical team sizes

Engaged Lead Link

• Someone who wants to make the pilot succeed
• Willing to invest time in facilitator training
• Open to feedback and learning

Moderate Autonomy

• Not completely isolated (otherwise not representative)
• Not extremely dependent on others (otherwise too much friction)
• Has its own deliverables and decisions

Motivated Members

• People who want to try new things
• Not only skeptics (who slow things down)
• Not only enthusiasts (who sugarcoat)

Representativeness

• Typical challenges of the organization
• Typical composition (not the “special team”)
• Learnings must be transferable

Warning: The Wrong Circle

Don’t choose the easiest team: An innovation team that already works self-organized isn’t a good pilot. The learnings won’t transfer to more traditional teams.

Don’t choose the most difficult team: A team with internal conflicts or dysfunctional leadership is also not a good pilot. Holacracy can’t magically solve such problems.

Don’t choose the most prestigious team: If the pilot fails, it shouldn’t damage an important team’s reputation.

Pilot Design

Timeframe

Minimum: 3 months Less isn’t enough to get through the learning phase.

Recommended: 6 months Gives time for:

• Initial learning (Month 1-2)
• Stabilization (Month 3-4)
• First results (Month 5-6)

Maximum: 9 months A pilot shouldn’t run longer. Either decide for rollout or against Holacracy.

Define Success Criteria

Define before starting what you’ll measure success by:

Process Metrics:

• Governance meetings happen regularly (e.g., monthly)
• Meetings complete within planned time
• Rules are largely followed
• Facilitator interventions are accepted

Engagement Metrics:

• Participation rate at meetings (Target: >90%)
• Number of tensions raised per month (Target: increasing, then stable)
• Number of governance proposals (Target: increasing, then stable)
• Feedback in retrospectives (qualitative)

Outcome Metrics:

• Are tensions actually resolved?
• Has collaboration improved?
• Do members report positive changes?
• Has the circle achieved its goals?

Support Structure

The pilot circle needs support:

Facilitator Training: At least 2 people in the pilot circle should have facilitator training.

Coaching: Access to an experienced Holacracy coach (internal or external) for questions and difficult situations.

Sponsor: A sponsor from leadership who mediates in conflicts with the rest of the organization.

Feedback Channel: Regular retrospectives to identify problems early.

The Interface with the Rest of the Organization

The biggest problem with pilots is the interface with the non-holacratic rest of the organization.

Typical Conflicts

“Who gets to decide what?” The pilot circle works with roles and domains. The rest of the organization works with jobs and hierarchy. Conflicts arise when it’s unclear which system applies.

Solution: Clear delineation. The pilot circle has autonomy within its boundaries. Everything that crosses these boundaries is temporarily handled by old rules.

“Why do they get to do that?” Envy or confusion among colleagues not in the pilot.

Solution: Transparent communication. Explain why the pilot is happening and what the goal is. Invite interested parties to observe.

“That takes too long!” Governance processes can seem slower than “the boss decides.”

Solution: Set realistic expectations. Governance is for structural decisions, not operational urgencies.

Interface Design

Explicitly define how the pilot circle interacts with the rest:

Decisions within the pilot: Holacracy rules apply. The pilot circle decides autonomously within its domains.

Decisions that exceed the pilot: Traditional hierarchy applies. The pilot circle’s Lead Link serves as the contact person.

Resources (budget, personnel): Allocated according to traditional rules. The pilot circle has autonomy only over allocated resources.

Communication outward: The Lead Link or a dedicated “Liaison” role communicates with the rest of the organization.

Phases of the Pilot

Phase 1: Preparation (2-4 weeks before start)

Training:

• Facilitator training for 2+ people
• Basic training for all pilot participants
• Conduct role mapping

Logistics:

• Set up tool (GlassFrog or alternative)
• Establish meeting rhythm
• Clarify communication channels

Communication:

• Announce the pilot
• Communicate goals and timeline
• Create FAQ for non-pilots

Phase 2: Launch (Week 1-2)

First Governance Meeting:

• Conduct with supervision
• Keep expectations low
• Many process errors are normal

First Tactical Meetings:

• Practice triage process
• Understand tension vs. project
• Establish rhythm

Phase 3: Learning Phase (Month 1-2)

Typical Challenges:

• Meetings run too long
• Process rules are forgotten
• Roles are unclear
• Frustration among participants

This is normal. The facilitator needs many interventions. Governance proposals are clunky. Everyone is learning.

What helps:

• Regular retrospectives
• Use coaching support
• Patience with yourself and others
• Celebrate small wins

Phase 4: Stabilization (Month 3-4)

Signs of Progress:

• Meetings get shorter
• Fewer facilitator interventions needed
• Governance proposals are clearer
• First success experiences

What matters now:

• Continue refining roles
• Document learnings
• Make first adjustments
• Communicate successes

Phase 5: Evaluation (Month 5-6)

Structured Evaluation:

• Check success criteria
• Collect feedback from all participants
• Also get feedback from non-pilots
• Honest analysis: What worked, what didn’t?

Prepare Decision:

• Prepare data for leadership
• Formulate recommendation
• Draft rollout plan or exit plan

Extracting Learnings

A pilot is only valuable if the learnings are usable for rollout.

Document

During the pilot, document:

• What process adjustments were needed?
• Which roles worked well, which didn’t?
• Which facilitator interventions were frequently needed?
• Which governance proposals solved the most problems?
• What cultural barriers emerged?

Retrospectives

Monthly pilot retrospectives:

• What did we learn this month?
• What would we do differently?
• What should other circles know?

Final Review

At the end of the pilot:

• What worked surprisingly well?
• What worked surprisingly poorly?
• What assumptions were wrong?
• What would we do differently in the rollout?

The Decision After the Pilot

Option A: Rollout

If the pilot was successful:

• Create roadmap for phased rollout
• Use pilot participants as ambassadors and trainers
• Incorporate learnings into training and communication
• Set timeline

Option B: Adjustment and Extension

If the pilot had mixed results:

• Identify specific problems
• Test adjustments
• Extend pilot by 2-3 months
• Re-evaluate

Option C: Termination

If the pilot failed:

• Honest analysis: Why?
• Was it Holacracy or other factors?
• What did we learn anyway?
• Next steps (different method, culture work, wait)

Important: A failed pilot isn’t a failure. It’s valuable information. Better a failed pilot than a failed full implementation.

Research Insights on Pilot Programs

Empirical Findings on Phased Implementation

The most comprehensive empirical study on Holacracy implementations analyzed 43 transformations and identified clear patterns for successful pilot programs [2]:

Success Factors for Pilots:

• Dedicated top management commitment before pilot launch
• Sufficient resources for training and coaching
• Clear delineation of pilot autonomy
• Regular retrospectives for course correction

Critical Finding: Organizations that used pilots as “commitment avoidance” had significantly worse outcomes than organizations with genuine exploration intent.

The Mercedes-Benz.io Case Study

A detailed case study on Holacracy implementation at Mercedes-Benz.io provides valuable insights into piloting in large organizations [3]:

Context: 100% subsidiary of the Daimler group, implemented Holacracy as part of digital transformation.

Pilot Insights:

• Resource Requirements: Piloting required substantial resources for training and support
• Decision Speed: Decentralized decision-making increased commitment but sometimes extended the decision process
• Transparency: Increased transparency and accountability were early pilot successes
• No Ready-Made Solution: Holacracy is not a plug-and-play system and requires continuous adaptation

Key Insight: “Holacracy seems suitable for industries where the need for adaptability outweighs the need for reliability.”

Piloting in Bureaucratic Organizations

A three-year field study in a U.S. government agency examined how traditional bureaucratic organizations can design pilot programs for Holacracy [4]:

Surprising Finding: Instead of the expected chaos, a new post-hierarchical order emerged from the pilot program. The key was the “normalization of disagreement” as part of the pilot process.

Implications for Pilots:

• Larger, established organizations can particularly benefit from pilot programs
• Cultural change takes time – a 3-month pilot is insufficient for such organizations
• The willingness to accept conflicts as productive is a critical success factor

Common Pilot Mistakes

Mistake 1: Pilot as Permanent State

Symptom: The pilot has been running for 18 months and nobody talks about rollout.

Problem: Holacracy in the pilot circle is isolated and will never achieve full effect.

Solution: Time limit from the start. After 6-9 months, a decision must be made.

Mistake 2: Too Little Support

Symptom: The pilot circle struggles alone without training and coaching.

Problem: Mistakes aren’t corrected, frustration rises, pilot fails.

Solution: Invest in training and coaching. The pilot is an experiment, not self-running.

Mistake 3: Wrong Circle

Symptom: The pilot circle is too special (e.g., R&D team) or too problematic (e.g., team with conflicts).

Problem: Learnings aren’t transferable or the pilot fails due to pre-existing problems.

Solution: Choose a representative circle with motivated but not exceptional members.

Mistake 4: No Clear Criteria

Symptom: After the pilot, it’s unclear whether it was successful or not.

Problem: The decision becomes political rather than evidence-based.

Solution: Define success criteria before starting and measure regularly.

Mistake 5: Pilot Isolation

Symptom: The pilot circle has hardly any interaction with the rest of the organization.

Problem: The challenges of integration aren’t tested.

Solution: Choose a circle with interfaces. Define the interface explicitly.

---

Research Methodology

This article synthesizes insights from a research database of 655+ academic papers on Holacracy and self-organization (2012-2025). Studies were selected based on:

• Methodological rigor: Empirical studies with clear methodology preferred
• Change management focus: Studies on pilot programs and phased implementation prioritized
• Practical relevance: Case studies and application-oriented research included

Database queries:

./scripts/research/paper-search.sh "holacracy pilot implementation" --contextual
./scripts/research/paper-search.sh "organizational change phased rollout" --contextual

Limitations: Academic literature on specific pilot methods for Holacracy is limited. Our recommendations are based on general change management research and practical experience.

---

Disclosure

SI Labs has practiced Holacracy since 2015 and has supported both pilot-based and direct implementations. This experience informs our perspective but may also lead to bias.

---

Sources

[1] Hryvnyak, L., & Mykytas, I. (2021). “The Approach to Implementation of Flexible Organizational Structures.” Economics and Society, 34, 61-68. DOI: 10.32782/2524-0072/2021-34-61 [Framework Paper | Sample: Multiple cases | Citations: 1 | Quality: 46/100]

[2] Pfister, A., Schwarz, P., & Wüthrich, C. (2021). “Change the way of working. Ways into self-organization with the use of Holacracy: An empirical investigation.” European Management Review, 18(4), 455-472. DOI: 10.1111/emre.12457 [Empirical Study | Sample: 43 transformations | Citations: 43 | Quality: 76/100]

[3] Fischer, S., Weimann, K., & Redler, B. (2021). “How Mercedes-Benz addresses digital transformation using Holacracy.” Journal of Change Management, 21(4), 445-463. DOI: 10.1108/jocm-12-2020-0395 [Case Study | Sample: Mercedes-Benz.io | Citations: 23 | Quality: 67/100]

[4] Lee, M. Y. (2020). “Building Shared Purpose without Managers: How Can Holacracy Work?” Academy of Management Proceedings, 2020(1). DOI: 10.5465/ambpp.2020.20972abstract [Field Study | Sample: US Government Agency, 3 years | Citations: 1 | Quality: 48/100]