← Back to Blog
31 August 2026

Holacracy vs. The Cone Model: What Distributed Authority Gets Right and What It Leaves Broken

Most organizations are built on a silent assumption: that authority flows downward, from the few to the many, and that hierarchy is simply the natural order of things. Then holacracy arrived and challenged everything.

Developed by Brian Robertson and formalized in the early 2000s, holacracy promised something radical: a governance system where power is distributed across self-organizing circles rather than concentrated at the top. Companies like Zappos made headlines by adopting it, and the business world took notice. But the results were messy, complicated, and deeply instructive.

Enter the Cone Model, a different approach to distributed authority that attempts to solve some of the problems holacracy leaves unresolved. Both models reject traditional top-down management, yet they arrive at very different conclusions about how power, accountability, and decision-making should actually function.

In this post, you will get a clear, honest comparison of both frameworks. We will examine what holacracy genuinely gets right, where it struggles in practice, and how the Cone Model addresses those gaps. Whether you are evaluating organizational structures or simply trying to understand the future of work, this breakdown will sharpen your thinking considerably.

What Holacracy Actually Is (And What Problem It Was Built to Solve)

What Holacracy Actually Is (And What Problem It Was Built to Solve)

Brian Robertson began developing what would become holacracy in 2001 at his software company Ternary Software, formally publishing the first Holacracy Constitution in 2007 and founding HolacracyOne to steward and license the system. The founding problem was specific: traditional positional hierarchy concentrates authority at the top, which means the people furthest from the actual work hold the most decision-making power. The result is predictable — approval chains slow organisations down, frontline insights go unheard, and employees disengage because they cannot act on what they clearly see. Robertson framed his design question not as "how do we improve management?" but as "what gets in the way of sensing something that could be better?" That reframing produced a structurally different answer. You can read the history of holacracy in Robertson's own words to understand how the framework evolved from lived frustration into a codified system.

The core mechanics rest on four pillars. First, authority attaches to written roles inside self-organised circles, not to the people who happen to hold senior titles. Second, employees hold multiple dynamic roles simultaneously, and those roles can be created, modified, or dissolved through recurring governance meetings rather than through management sign-off. Third, a ratified constitution of more than forty pages governs every decision-making process, meaning even founders formally hand authority to the system rather than to individuals. Fourth, the framework separates governance work (defining roles and policies) from tactical work (getting things done), so neither meeting type corrupts the other. The "tension" mechanism ties it together: any gap between current organisational reality and what the organisation's purpose requires is treated as a structured improvement input, not a problem to escalate upward. Decoding the Holacracy Constitution with Brian Robertson offers a practitioner-level entry point into how these rules operate in practice.

The marketed benefits have genuine empirical support. A 2023 peer-reviewed study published in Frontiers in Psychology found that employees in holacratic organisations reported significantly lower illegitimate task scores (2.49) compared to traditional organisations (2.78), alongside higher reported appreciation. Faster decisions, greater autonomy, and a more adaptive structure are real outcomes when the system is implemented well. Approximately 500 organisations worldwide have adopted holacracy or holacracy-inspired governance, according to HolacracyOne's 2024 data, and the commercial ecosystem supporting them is mature. The open-source constitution is available free in multiple languages. GlassFrog provides dedicated governance software. The paid Accelerator platform offers practitioner training with live sessions alongside a free basics course. Certified coaches operate in the United States through HolacracyOne, in the Netherlands through Energized.org, and in France through L'Institut iGi and HappyWork. For organisations evaluating the system, the infrastructure to implement it professionally is available and established.

Where Holacracy Beats Traditional Hierarchy

Having established what holacracy is and the problem it was designed to solve, it is worth giving the framework its genuine due before examining where it falls short.

Decision bottlenecks dissolve by design. In a traditional hierarchy, approval chains concentrate authority at the top, and a single leader's availability becomes the rate-limiting factor for organizational progress. Holacracy addresses this structurally rather than culturally: authority sits in roles, not people, and each circle carries defined decision domains that cannot be informally overridden by a manager. The Holacracy Constitution encodes this as a formal rule, meaning the change is not dependent on a well-intentioned leader choosing to delegate. The structure itself distributes power.

Organizational design becomes a living document. Rather than freezing structure into an org chart drafted at founding, holacracy updates roles through written governance processes. Governance meetings and tactical meetings are deliberately separated, preventing operational status updates from consuming the structural thinking a growing organization constantly needs. Roles, accountabilities, and policies change in response to real work as it actually presents itself, not in response to internal politics or inertia.

The "tensions as inputs" mechanism deserves specific recognition. Instead of suppressing misalignment or routing friction upward through management layers, holacracy encodes a formal process for converting any gap between current reality and organizational purpose into a legitimate agenda item for structural change. This is a genuine innovation in organizational design, and Mooncamp's holacracy overview identifies it as one of the framework's most distinctive features.

Empirical support for autonomy benefits exists. A peer-reviewed study published in Frontiers in Psychology (January 2023) found that holacracy employees reported significantly fewer illegitimate tasks compared to traditional-organization counterparts (mean 2.49 versus 2.78, p < 0.05), alongside higher reported appreciation. For small, knowledge-intensive organizations where every team member operates at high capability with minimal supervision needs, the circle structure maps naturally onto how people already collaborate. The micromanagement overhead that hierarchy generates is a real cost, and holacracy removes it.

The Apex Problem: Who Is Accountable When Circles Cannot Decide?

Holacracy's distributed authority model is architecturally elegant in one direction: downward. Authority flows from the broadest circle to narrower sub-circles, roles are defined by purpose and accountability, and governance meetings exist to resolve structural tensions before they calcify into dysfunction. What the Holacracy Constitution does not provide is any comparable architecture for the apex itself. When a decision exceeds the scope of any single circle, when competing circles cannot resolve a cross-boundary tension, or when a crisis demands a single authoritative voice within hours rather than governance cycles, the model goes structurally silent. The person at the top, typically a CEO or founder, retains residual accountability by default. The model simply offers no framework for what that means or how that person should be supported.

This is not a trivial edge case. Research published by SI Labs in January 2026, drawing on a study of 81 start-ups, found that unclear authority distribution is one of the most common causes of organisational dysfunction. More critically, the same analysis identifies what practitioners call the informal-leader paradox: flat hierarchies without explicit authority assignment "paradoxically often lead to more power concentration with informal leaders." In practice, this means the founder informally overrides circle decisions, or staff escalate to the CEO because no circle has clear ownership of the problem in front of them. The hierarchy has not been eliminated; it has simply been made invisible and, by extension, unaccountable.

The important clarification here is that this is not a character problem. It is a structural design problem. Holacracy's architects were solving a real and serious failure mode in traditional organisations: authority concentrated at the top, decisions bottlenecked, employees disempowered. That diagnosis is correct. But removing positional hierarchy does not dissolve the need for a final decision-maker. It relocates that person to a structurally unsupported position with no genuine peer, no designated deputy carrying formally delegated authority, and no model for their own role within the system they nominally lead.

The Cone Model addresses this gap directly through what it calls the two-person apex. At the top of the cone sit not one leader but two: a leader and a genuine deputy with real delegated authority. This is not succession planning or a conventional COO arrangement. It is the structural cure for the apex individual's own isolation, present and active while the leader is fully in post. The deputy is not waiting in reserve; they are a co-present structural counterpart who absorbs relational and decision load in real time, giving the leader a genuine peer at the altitude where holacracy provides none.

This distinction matters most precisely when the pressure is highest. Holacracy's distributed authority framework separates governance meetings from tactical operations to prevent one from hijacking the other, but governance cycles still operate on a cadence. Crises, rapid scaling decisions, and high-ambiguity strategic pivots do not wait for the next governance meeting. In those moments, the apex individual under holacracy is simultaneously the most exposed person in the organisation and the least structurally equipped. The Cone Model's two-person apex is built precisely for that gap: not as an administrative convenience, but as the structural answer to a structural problem that distributed authority, by design, cannot resolve from below.

The Problem Holacracy Does Not Name: Leader Loneliness as a Structural Flaw

Scan holacracy's foundational literature, its constitution, its governance frameworks, and its practitioner guides, and you will find a comprehensive architecture for distributing authority, clarifying roles, and processing organisational tensions. What you will not find is a single mechanism addressing the relational experience of the person carrying final accountability at the apex of the system. The literature is structurally silent on this point, and that silence is not an oversight. It is a reflection of what holacracy was built to solve: employee autonomy and organisational agility. The person at the top was never the design's intended beneficiary.

This matters because leadership loneliness is not a personal failing. It is not the result of introversion, insufficient social skills, or a coaching gap that a better executive coach could close. It is a structural condition produced when a person occupies the apex of a system that contains no structural provision for their own belonging, genuine peer relationship, or lateral support. The weight of final accountability, when carried without structural companionship, produces isolation as a predictable output, not as a personality symptom.

Holacracy, counterintuitively, intensifies this condition rather than relieving it. Traditional positional hierarchy, for all its rigidity, provides the apex person with something rarely acknowledged: visible, unambiguous legitimacy. Clear decision rights, role-defined authority, and legible accountability relationships are signals that orient the entire system around the leader's position. Holacracy explicitly replaces positional authority with role-based authority distributed across circles. This redistribution is its stated purpose. But the consequence for the person at the top is that those legitimacy signals dissolve, and no structural peer relationship is created to replace them. As hybrid organisational models acknowledge, the tension between distributed authority and the need for anchored accountability does not disappear simply because a constitution redistributes roles. The anchor person remains. Their isolation deepens.

The Cone Model, developed by William J. Oxfield and detailed in The Lonely Leader, names this structural flaw directly and proposes a structural cure. The cure is not coaching; it is architecture. Specifically, it is the two-person apex: a leader paired with a genuine deputy holding real delegated authority, not a succession candidate or a title, but a structural peer who absorbs relational load and eliminates the design condition that produces isolation. Alongside this, the model's framework of 21 human needs at work identifies that fourteen of those needs, including belonging, trust, friendship, and care, are peer-generated within teams rather than leader-sourced. The system itself, when designed correctly, produces the relational environment that sustains everyone within it, including the person at the top.

For leaders who have experienced the specific weight of isolation inside flat or distributed organisations, the diagnostic value of this naming is considerable. Understanding that the source of that isolation is a design flaw rather than a personal one reframes where the solution must be sought. The free Full Cone 360° assessment at theconemodel.com provides a practical starting point for identifying precisely where structural gaps exist in a specific organisation, making the move from diagnosis to structural remedy a concrete and actionable step.

The 21-Need Framework: Which Needs Require a Leader and Which Do Not

Holacracy is, at its architectural core, a decision-rights distribution system. Its constitution assigns authority to roles inside circles, its governance meetings clarify who decides what, and its core value proposition is operational: faster decisions, cleaner accountability, reduced escalation. What holacracy does not do, and has never claimed to do, is map the full spectrum of human needs that employees carry into work each day. It does not ask which of those needs require a person with positional authority to fulfil, and which can be generated laterally between peers. That silence is not a minor omission. It is the primary reason holacracy succeeds in some organisations and quietly unravels in others.

The Framework That Fills the Gap

The Cone Model provides the diagnostic layer holacracy leaves blank. It identifies 21 things people need to flourish at work and draws a precise line between two categories. Seven needs are leader-sourced: Direction, Vision, Mission, Mentoring, Reward, Advocacy, and Autonomy. These require a person with positional authority to deliver them meaningfully. A peer cannot grant you a promotion, set the strategic direction of the organisation, advocate for your interests to a board, or provide the kind of mentoring that carries institutional weight. Fourteen needs are peer-sourced: Belonging, Safety, Correction, Teamwork, Trust, Training, Recognition, Friendship, Encouragement, Accountability, Celebration, Challenge, Forgiveness, and Care. These are not only capable of being generated horizontally between colleagues; they are most authentically generated that way.

This distinction changes the entire organisational design conversation. The question is no longer "how do we distribute all authority?" That framing, which holacracy inherits, treats authority as the central variable in human flourishing. The better question is: "which needs genuinely require positional power, and which should be generated horizontally by the team itself?" These are different questions with different answers and meaningfully different failure modes.

Why Circles Cannot Self-Diagnose Relational Absence

Holacracy's circle structure does create conditions for regular peer interaction, and in principle, a well-functioning circle could generate belonging, accountability, trust, and recognition among its members. The problem is structural: holacracy's governance meetings are designed to process role tensions and operational outputs, not to surface whether a member feels safe, cared for, or genuinely seen. There is no mechanism in the constitution to detect when a circle is failing to produce the fourteen peer-sourced needs. Absence becomes invisible because the framework has no vocabulary for it. You cannot diagnose what you have not named.

The Pre-Existing Trust Variable

This explains holacracy's uneven adoption record with striking precision. Fewer than 1,000 organisations globally practise formal holacracy, and high-profile rollouts have demonstrated real operating costs. A 2023 peer-reviewed study published in Frontiers in Psychology found that success in holacratic environments is moderated by individual personality characteristics, specifically the predisposition toward self-initiation and peer reliance. That finding maps directly onto the 14-need framework: teams with high pre-existing social trust generate belonging, accountability, challenge, and care organically, making holacracy feel liberating. Teams without it discover that removing the manager removes positional structure without replacing what that structure, however imperfectly, was providing. Direction disappears. Advocacy disappears. The relational anchor dissolves. Peer cohesion does not automatically fill the space; it requires the conditions that produce it, and those conditions must be deliberately built, not assumed.

The practical implication is significant for any leader evaluating distributed authority models. Structural redesign that removes positional roles without first mapping which human needs those roles were fulfilling is not liberation. It is subtraction without accounting. The Cone Model's 21-need framework provides the accounting ledger that makes the subtraction visible before it becomes a failure.

The Triangle and the Circle: Reconciling Authority and Belonging

Holacracy's primary structural move is to flatten the triangle. By distributing authority across self-organizing circles and replacing positional titles with dynamic roles, it deprioritizes the vertical chain of command in favor of a governance-process framework. The Cone Model makes a fundamentally different structural choice: retain the triangle, and reconcile it with the circle rather than dissolve one into the other. These are not equivalent design decisions, and treating them as interchangeable options misunderstands what each structural element actually does.

The triangle is not bureaucratic noise. Positional authority carries the clarity signals that direction, vision, and accountability require. When an organization needs to orient itself, set priorities, or correct course, those signals must travel through a recognizable chain. Removing or diffusing positional hierarchy does not eliminate the need for those signals; it simply makes them harder to trace. As Holacracy's own organizational structure documentation acknowledges, authority in holacracy is redistributed to roles rather than eliminated entirely, which suggests that even its architects recognize that some form of directional authority is non-negotiable. The question is where it lives and who carries accountability for it.

The circle is equally non-negotiable, and this is where holacracy's architecture leaves a structural gap. Holacracy's circles are governance units, not relational communities. They define role accountability and manage decision rights through formal governance meetings. What they do not engineer is peer trust, belonging, or the psychological safety that makes teams perform at their highest levels. Google's Project Aristotle research is unambiguous on this point: the single strongest predictor of team performance was not decision-making autonomy, role clarity, or structural flatness. It was psychological safety, a peer-generated condition that emerges from the quality of horizontal relationships within a team, not from the sophistication of a governance process. Wellhub's organizational development analysis frames holacracy's potential benefits as including employee wellbeing and innovation, but treats these as downstream effects of structural flexibility rather than as independently engineered relational conditions. That distinction matters enormously.

The Cone Model treats the organization as a cone: a triangle with a circle inside it. Authority flows downward from the apex; peer trust flows horizontally within teams at each level. Both are structural requirements, not cultural aspirations or emergent side effects. The fourteen peer-sourced needs identified in the model, including belonging, safety, trust, encouragement, and accountability between colleagues, cannot be procedurally mandated through a governance constitution. They require a structure that explicitly creates the conditions for horizontal peer relationships to form and sustain themselves. As practitioners exploring alternative organizational structures increasingly recognize, holacracy is one design option among several, and its optimization for decision efficiency comes at a cost in the relational dimension.

Holacracy optimizes for the triangle dimension, decision rights, role clarity, governance process, while largely leaving the circle dimension to emerge on its own terms. The Cone Model insists that both are non-negotiable design requirements. You cannot replace one with the other, and you cannot rely on cultural goodwill to supply what structural design omits.

Fractal Span and Dunbar's Number: Why Relational Load Does Not Scale Evenly

Holacracy's architecture rests on a foundational assumption that rarely gets examined directly: that governance process can remain constitutionally identical regardless of how many people sit inside a circle. A circle of four and a circle of forty-four run through the same proposal, objection, and integration sequence. The same facilitator role, the same tension-processing logic, the same meeting cadence. What the holacracy constitution does not contain, and has never contained since its 2007 publication, is any mechanism for detecting or responding to the relational load that accumulates as circles expand. This is not a minor gap in an otherwise complete model. It is a structural blind spot with measurable consequences.

The Biology of Trust Has Hard Limits

Robin Dunbar's research into the relationship between neocortex size and social group capacity established that human beings can maintain stable, meaningful trust relationships with roughly 150 people, with empirically observed sub-groupings clustering at approximately 50, 15, and 5. These are cognitive ceilings, not stylistic preferences or cultural artifacts. Below the 150-person threshold, people navigate governance through personal knowledge: they know who to trust, they can track decision provenance directly, and accountability is carried by relationship. Beyond that ceiling, the cognitive infrastructure for personal trust is simply saturated, and governance must shift from relational to procedural. As one organizational design analysis frames it plainly: small organizations run on trust, large organizations run on control. Holacracy's governance process presumes neither; it applies the same constitutional machinery to both, with predictable results as headcount climbs.

Fractal Span: Oscillation, Not Linear Decay

The Cone Model treats this biological reality as a design input rather than an inconvenient complication. Span narrows in a fractal, repeating pattern as organizational altitude increases: approximately 10, then 5, then 2, before resetting to a full circle at each order-of-magnitude boundary. The critical insight is that relational load oscillates with altitude rather than simply degrading as the organization grows. Leaders at different levels of the same organization experience fundamentally different relational demands, and those demands follow a predictable rhythm. A model that does not encode this rhythm cannot help a leader, a circle lead, or an implementation consultant diagnose why a particular level of the organization is struggling while adjacent levels are functioning well. Holacracy offers no such diagnostic instrument.

The practical consequences show up as a recognizable cluster of symptoms in large-scale implementations. Research into holacracy at enterprise scale documents governance meeting time explosion, circle bloat, and role proliferation as organizations grow past the 150-person Dunbar threshold. These are not separate problems requiring separate fixes; they are the same problem wearing different clothes. When relational span is exceeded and trust can no longer carry coordination, the system compensates by externalizing into process and role definition what it can no longer carry relationally. More roles get created, more meetings get scheduled, and the governance apparatus expands to fill the trust vacuum. The holacracy model cannot diagnose this pattern because it has no internal representation of relational load to compare against.

Cross-Civilizational Validation

The evidence that natural span constraints are biological rather than cultural does not begin with Dunbar's laboratory. Jethro's counsel to Moses in Exodus 18 prescribed organizing the Israelites into groups of ten, fifty, one hundred, and one thousand, with designated leaders at each level handling matters within their span and escalating only what could not be resolved locally. The intervals map onto Dunbar's empirically derived sub-groupings with a precision that is difficult to attribute to coincidence. Roman military design reached the same conclusion independently: the contubernium of eight men, the century of eighty, the cohort of roughly 480, and the legion of 4,800 to 5,000 encode the same span rhythm through centuries of field-tested attrition. Modern military unit design has not abandoned these proportions; special forces teams, infantry squads, and platoon structures continue to reflect the same underlying cognitive constraints.

The Cone Model draws on this convergent historical record to position its fractal span cycles as a rediscovery of stable human reality rather than a novel management theory. A governance constitution drafted in 2007 in a software company context cannot claim equivalent empirical depth. The cross-civilizational evidence gives the Cone Model's span architecture a validation that no single modern framework, however thoughtfully constructed, can manufacture from scratch.

When Holacracy Fails: The Zappos Experiment and What the Rollbacks Reveal

When Holacracy Fails: The Zappos Experiment and What the Rollbacks Reveal

Zappos remains the most instructive case study in holacracy's limits, not because the experiment was poorly intended, but because it was pursued with unusual scale, commitment, and transparency. When CEO Tony Hsieh announced the rollout in January 2014, reorganising approximately 1,500 employees into more than 400 self-managed circles, Zappos became the largest organisation ever to attempt full holacracy adoption. The ideological ambition was explicit: Hsieh wanted to eliminate all management titles and create what he described as the most democratic workplace in corporate history. By March 2015, he had activated a generous severance offer for any employee unwilling to continue under the new structure. Roughly 18% of the workforce accepted and left, with departures disproportionately weighted toward experienced leaders who understood, perhaps better than most, what the absence of directional structure would cost them over time.

Three Failure Modes That Appear Across Rollbacks

The Zappos case is not an outlier. A January 2026 analysis of 47 documented holacracy implementations drawn from 655 academic papers found that retail sector organisations, the category Zappos occupies, achieved a success rate of just 50%, compared with 82% for consulting and services firms and 80% for healthcare organisations. The pattern is consistent: holacracy performs well in small, mission-aligned, high-autonomy environments and degrades under scale, performance pressure, or where employees need more directional clarity than distributed governance can supply.

Three failure modes appear with regularity across these rollbacks. The first is governance meeting overload, where circles spend more time redefining roles and resolving process tensions than delivering work. Employees who remained at Zappos after the buyout described confusion and paralysis; reporting at the time characterised the organisation as having ground to a halt under the weight of its own egalitarianism. The second is role proliferation: holacracy replaces fixed job descriptions with fluid, evolving roles held across multiple circles, and at Zappos' scale, the number of dynamic roles grew faster than anyone could track, creating accountability diffusion rather than the accountability clarity the system promised. The third is apex isolation, the structural condition in which the founder or CEO retains residual accountability for the entire transformation with no structural deputy and no distributed leadership support beneath them. Hsieh's April 2015 memo formally declared that there would be "effectively no more people managers," leaving him to carry the weight of a 1,500-person restructuring without a genuine second in command.

Why The Cone Model Predicts These Outcomes

These failure modes are structurally predictable. The Cone Model identifies 21 things people need to flourish at work; 14 of them, including belonging, safety, trust, correction, and encouragement, are generated peer-to-peer rather than by the leader. Holacracy's circle structure distributes decision rights efficiently but does not automatically generate the peer relationships that produce those fourteen needs. Zappos employees who left were not simply resisting change; many were leaving because the structure removed the relational scaffolding they depended on, without replacing it with anything equivalent. The circles redistributed authority. They did not rebuild belonging.

At the apex, Hsieh faced the structural condition The Cone Model identifies as the leader's own most significant vulnerability: a position of ultimate accountability with no genuine deputy holding real delegated authority beside him. The structural cure for apex isolation is not coaching or resilience training; it is a second person at the top with actual decision-making power, a design element holacracy's constitution does not accommodate.

The lesson Zappos offers is precise. Distributing authority is not the error. The error is distributing authority while dismantling the triangle's directional clarity and neglecting to build the circle's peer trust infrastructure in its place. That combination produces structural brittleness that surfaces under exactly the conditions, scale, rapid change, and sustained performance pressure, when organisations most urgently need structural strength.

Holacracy vs. The Cone Model: A Direct Structural Comparison

The six dimensions examined throughout this post now converge into a direct structural comparison. Placing both frameworks side by side reveals not a competition between a new idea and an old one, but a genuine architectural divergence with practical consequences for every leader deciding how to design their organization.

Authority Structure

Holacracy's foundational move is to replace positional hierarchy with distributed role authority inside self-organized circles. The Cone Model makes no such replacement. Positional authority is retained at the apex while horizontal peer trust is built into every level of the structure. Both layers coexist by design rather than one eliminating the other. This distinction matters because organizations do not choose between needing direction and needing belonging; they need both, and a framework that eliminates the positional layer to gain the relational one trades one structural problem for another.

Apex Accountability

Holacracy's circle architecture has no structural provision for the individual carrying final legal, fiduciary, or strategic accountability. That person sits at the top of the system without a genuine peer or a deputized second, which is precisely the loneliness condition this post has traced from its roots. The Cone Model addresses this with a two-person apex: a leader paired with a deputy holding real delegated authority. This pairing is not succession planning; it is the structural cure for the isolation that positional authority, without a genuine counterpart, inevitably produces.

Human Needs Mapping

Holacracy's governance architecture is optimized for role clarity and decision-rights distribution. It does not differentiate which human needs at work require a leader to supply and which can only be generated peer-to-peer. The Cone Model's 21-need framework provides that diagnostic map explicitly: 7 needs sourced from the leader, 14 from peers. When a team is struggling, this framework identifies whether the failure is positional (the leader is not providing direction, vision, or advocacy) or relational (the peer layer is not generating belonging, safety, or accountability). Holacracy offers no equivalent diagnostic.

Scalability Architecture

Holacracy describes nested circles for growing organizations but provides no model for how relational load changes as altitude increases. The Cone Model's fractal span cycles, oscillating at approximately 10, then 5, then 2, grounded in Dunbar's number and cross-validated against military, biblical, and modern organizational evidence, offer a quantitative scalability argument that circle-nesting does not match.

Implementation and Tooling

Holacracy requires full constitutional adoption, structured governance meetings, and certified coaching investment, representing a significant organizational transformation. The Cone Model operates as a diagnostic overlay applicable to an existing structure without constitutional change, lowering the entry threshold considerably. For practical assessment, theconemodel.com offers four free tools, including the Full Cone 360°, the Proximity and Lone-Wolf Check, Find Your Deputy, and Five Leadership Voices, available in English and Dutch, making structured self-diagnosis accessible from the outset.

Which Organizational Model Is Right for Your Context?

Holacracy is likely to perform best in organizations under roughly 150 people, where team members already bring high baseline autonomy, where peer trust is a cultural given rather than something that needs to be built, and where a strong mission sustains intrinsic motivation without requiring much positional direction. A 2023 peer-reviewed study of 95 employees in holacratic companies in Switzerland and Germany found that person-organization fit in holacracy is significantly predicted by Big Five personality dimensions, which means the model quietly self-selects for a particular kind of employee. That is not a flaw in itself, but it is a serious contextual constraint that organizations rarely audit before adoption.

The structural risks multiply at scale, under performance pressure, during leadership transitions, and wherever employees span wide ranges of capability and autonomy. Governance overhead in holacracy scales with organizational complexity, but the relational infrastructure required to carry that complexity does not automatically appear alongside it. When accountability becomes genuinely unclear during a crisis, the governance architecture produces meetings and role clarifications rather than resolution. Organizations with capability heterogeneity, where some people are ready for full self-direction and others are not, face the sharpest exposure here.

The Cone Model is structured for a different set of realities. Because its fractal span model accounts for how relational load changes with organizational altitude, cycling through spans of roughly ten, then five, then two before resetting at each power of ten, it works consistently from a team of five to a global organization of thousands. It does not assume a flat relational surface, which holacracy structurally does. Leaders managing across multiple layers do not face a governance cliff; they face a predictable oscillation of relational weight that the model explicitly maps.

For leaders already carrying the weight of apex accountability without a genuine structural peer, the two-person apex framework provides an intervention that no holacracy tool currently offers. The deputy is not succession planning; it is the structural cure for the isolation that accumulates at the top when authority cannot be genuinely shared.

The most honest guidance is diagnostic rather than prescriptive. The question is not which model is better in the abstract; it is which structural problems are present in a specific organization right now. The free Full Cone 360° assessment at theconemodel.com is designed precisely for that purpose, surfacing the actual structural gaps in your context rather than recommending a universal solution.

Conclusion: Distributed Authority Is Not Enough on Its Own

Holacracy correctly identifies the core failure of traditional hierarchy. Concentrating authority at the top creates bottlenecks, dependency, and disengagement, and its circle-based response to that failure is a genuine structural innovation with real intellectual weight behind it. The criticism examined throughout this post is not that holacracy is wrong. It is that distributing authority downward leaves three structural problems unsolved: the isolation of the apex, the absence of a framework for distinguishing which human needs require a leader from those that are peer-generated, and the inability to account for how relational load shifts unevenly as organizations scale.

The Cone Model does not reject holacracy's insights; it extends them. Retaining the triangle (positional authority, direction, vision) while building the circle (peer trust, belonging, the fourteen peer-sourced needs) produces a structure that is both directive and relational, both scalable and genuinely human. Authority and belonging are reconciled inside a single model rather than traded against each other.

The most productive immediate step for any leader evaluating these frameworks is to run the Full Cone 360° assessment at theconemodel.com. It identifies precisely where your current structure is generating the seven leader-sourced needs and where it is failing to produce the fourteen peer-generated ones. That diagnostic clarity is what makes the difference between wholesale reorganization and targeted structural repair.

Buy Now on Amazon Take the free 360° Assessment About the Book