Five Things the Holacracy Constitution Did

There are a lot of philosophical approaches to self-management. “Teal” offers a developmental lens—a theory of what kind of organization you’re trying to become, not how to operate once you get there.
Approaches like Sociocracy 3.0 and Corporate Rebels take a pattern language style: here are practices that have worked elsewhere, borrow what fits, leave the rest.
These aren’t criticisms. But what they share is optionality. They give you vocabulary, direction, inspiration—and no binding commitment.
Holacracy has stuck—at least for a while, in a lot of places—and a big part of why was the constitution. Not just what was in it, but the fact that it existed at all.
Here’s what I think it actually did.
1. It gave powerholders a way to make a credible commitment.
If you’re a CEO or founder thinking about adopting Holacracy, you’re being asked to give something up. Real authority. Real discretion. And the obvious question is: what guarantees that this actually holds? What stops you from quietly taking it back the moment it gets uncomfortable?
The constitution answered that question. Not perfectly, but meaningfully. By signing onto it—publicly, formally—a powerholder was making a commitment that had weight. Not just “I believe in self-management” as a sentiment, but a specific, credible promise that could be pointed to. The organization could hold them to it. Other people could read it. It created a form of accountability that didn’t depend entirely on the leader’s ongoing goodwill.
2. It created the conditions for shared learning across organizations.
One of the quiet promises of a shared constitutional standard is that organizations aren’t reinventing the wheel. If two companies are both operating under the same document, their experiences become legible to each other. What one learns, the other can use.
In practice this was always messier than the theory—context varies enormously, and “we both use Holacracy” doesn’t mean you’re always practicing the same thing. But the possibility was real. Practitioners could compare notes across companies. Problems that surfaced in one org could be recognized in another. Solutions could travel.
3. It gave organizations a grammar for their own collaborative space.
Before Holacracy, most organizations had rules—policies, expectations, norms—but no real framework for understanding what kind of thing those rules were. You had a job description and a policy manual and maybe some team agreements, but no way to think about the relationship between them. No shared vocabulary for the meta-level.
The constitution changed that. Suddenly you could look at an old policy and ask: is this really an accountability? A domain? You could translate existing organizational material into a new language. Whether that translation was always correct is beside the point. The point is that people became consciously aware that there was a grammar at all—that collaboration has a meta-structure (or second-order structure), it can be named, and that naming it changes what you can do with it.
4. It separated the rules from the ruler.
When governance lives in a document, it stops being a personal expression of whoever’s in charge. The rules aren’t coming from the CEO’s preferences or the founder’s instincts. They’re coming from something that predates any particular person’s authority—something that, in principle, applies to everyone including the people at the top.
That’s a meaningful shift in legitimacy. Not just “we’ve decided to do things this way” but “here is the structure we are all operating within.” The document becomes the authority. And that makes challenges to specific decisions easier, because you’re not challenging a person—you’re asking whether something fits the structure. That’s a much more navigable conversation.
5. It was written at the right level of abstraction.
Most governance documents are too specific to travel. They’re full of assumptions baked in from the organization that created them—the particular roles they happened to have, the particular decisions they needed to make, the particular culture they were trying to protect. Borrow another company’s policies and you inherit all of that. You spend half your time figuring out what to strip out and what to localize.
The Holacracy Constitution deliberately avoided that problem. It didn’t tell you what to decide. It defined the level at which decisions get made. The constructs and processes were specified; the content was always left to you. Your roles, your domains, your policies—all local, all yours. The grammar was shared. The sentences were your own.
This is what made it genuinely portable in a way that borrowed policy sets never are. You weren’t adopting someone else’s answers. You were adopting a shared framework for generating your own. That’s a different thing entirely—and it’s the thing that let the constitution work across organizations as different from each other as a tech startup and a law firm.
Conclusion
“There are only two kinds of social structure conceivable—personal government and impersonal government. If my anarchic friends will not have rules—they will have rulers.” G.K. Chesterton
Critically, none of this required the constitution to be perfect. It wasn’t. But perfection was never the point. What mattered was that it existed—as a document, as a commitment, as a shared standard that predated any particular person’s authority and outlasted any particular person’s mood.
That’s a general lesson, not a Holacracy-specific one. Written governance doesn’t just record decisions. It changes what decisions mean—who can make them, who can challenge them, and on what grounds. It turns “this is how we do things” into something that can be pointed at, argued about, and held to.
Most organizations never get there. They have norms and habits and preferences, loosely translated into policy. They have optionality without structure. The constitution was the opposite of that. And that opposition is what made Holacracy something other than just another philosophy about how work should feel.



Thanks, Chris. You make some important points here. Great summary.
Another idea: Explicating and objectifying the ruleset also helped to have a basis for an evolutionary meta-loop that would help the community evolve the Constitution itself over time.