When people come together around a shared purpose, writing down rules feels premature — even suspicious. "We trust each other," the thinking goes. "Rules are for bureaucracies, not movements." So the founding group begins with informal agreements, handshakes, and shared assumptions about how things will work.
This is almost always a mistake. Not because the trust is misplaced, but because trust between people doesn't automatically create fair structures between roles. When the first real conflict arrives — and it always does — the absence of clear rules doesn't mean that power is absent. It means that power is held by whoever can impose their interpretation of what was agreed.
"Informal organizations don't stay informal. They become informally hierarchical — with all the disadvantages of hierarchy and none of its transparency."
What a Rulebook Actually Is
A rulebook for an incubator-based organization is not a constitution, not a procedure manual, and not a list of prohibited behaviors. It is a shared operational framework — a document that defines how work gets organized, how decisions get made, how contributions get recognized, and what happens when things go wrong.
Its purpose is not to anticipate every situation. It is to ensure that when novel situations arise — and in a VUCA world, they always do — the organization has principles it can apply rather than a political vacuum it must fill.
A good rulebook is short enough to be read, specific enough to be useful, and flexible enough not to become its own obstacle. It is a living document — revisable by agreed process, not by whoever happens to be in charge when an inconvenient clause needs to disappear.
The Eight Areas It Must Address
1. How an incubator is founded
Who can propose one, what the minimum requirements are (a defined problem, a minimum number of founding members, a brief mandate), and what formal acknowledgment from the organization looks like. Without a clear founding threshold, either nothing gets started or everything does — and neither is useful.
2. Membership: who can join and what is expected
Membership in an incubator must be active, not nominal. The rulebook must define what participation means in practice — minimum contribution, how absence is handled, and how someone exits without burning the group's work behind them.
3. Decision-making: what requires consensus, what can be delegated
Not every decision is equal. The rulebook must distinguish between strategic decisions (requiring broad agreement), operational decisions (delegable to smaller groups), and individual decisions (within a member's defined scope). Without this distinction, every meeting becomes a referendum on everything.
4. Ranking and evaluation: how incubators are measured
The ranking system is the core of the merit-based model. The rulebook must define: what dimensions are measured (voter resonance, idea quality, implementation readiness, contribution activity), who performs the measurement, how often, and what happens to the results. Without this, ranking becomes a political tool rather than a structural one.
5. Conflict resolution
Conflicts between members, between incubators, and between an incubator and the wider organization are inevitable. The rulebook must define a procedure — escalation path, mediation options, final arbitration — so that conflicts are resolved by process rather than by whoever can sustain the louder argument longer.
6. Relationship to the wider organization
An incubator is autonomous but not independent. The rulebook must define what the organization owes incubators (services, platform, legitimacy) and what incubators owe the organization (transparency, alignment on core values, accountability for their proposals).
7. Lifecycle and closure
Not every incubator will succeed. The rulebook must define what success and failure look like — and what happens when an incubator completes its mandate, stagnates, or dissolves. The work it produced shouldn't disappear with it.
8. Resources: how support is requested and allocated
Time, money, and organizational attention are finite. The rulebook must define how incubators request resources, on what basis resources are allocated (merit and need, not internal politics), and how use of shared resources is reported. Opaque resource allocation is where the informal hierarchy always reasserts itself.
The Rulebook as Cultural Signal
Beyond its operational function, a rulebook sends a signal that the organization is serious about being what it claims to be. When new members join and find a clear, honest description of how the organization actually works — not just what it aspires to — trust is built faster, energy is invested rather than guarded, and capable people stay longer.
Conversely, organizations that resist writing down their rules are usually protecting something. Often, they are protecting the informal influence of whoever benefits from ambiguity. The resistance itself is diagnostic.
A rulebook doesn't guarantee a good organization. But the absence of one almost always guarantees a bad one.