The founder's informal veto
No rule grants it and everyone routes around it anyway — the objection that ends a discussion without ever being tested.
What it looks like
- Proposals get quietly checked with one person before they reach a meeting.
- Their objection ends a discussion, and nobody asks which rule it came under.
- Members describe ideas as "not worth raising", without being able to say why.
- The agreements say nothing about them having any special standing.
- When they are away, decisions wait rather than proceed.
Why it is hard to see
Because it is usually correct.
A founder has been right more often than anyone else in the room, on this specific subject, for years. The objection that ends the discussion is generally a good objection — it is based on more information, which is the whole problem. Deferring to someone with more context is not a failure of a group. It is what a sensible group does.
The failure is that the deference was never bounded. Nobody wrote down which decisions it applies to, what would count as overriding it, or when it stops. So it applies to everything, indefinitely, including the decisions where the founder’s extra context is worth nothing at all.
The second reason it stays invisible is that it produces no incidents. A formal veto leaves a record — a blocked proposal, a minuted objection. An informal one leaves nothing, because the proposals that would have triggered it were never made. What you are looking for is not an argument. It is an absence: things people stopped bothering to raise.
What to check
Ask three people who joined in the last two years to describe a decision they decided not to propose. If they all name the same person, the veto exists whatever the agreements say.
Then the succession question, which is the one that can be asked without accusation: what happens to this decision if that person is ill for a month? A community with a bounded arrangement answers it easily. A community with an unbounded one discovers, out loud, that it cannot.
If it is already happening
Do not start by removing anything. The founder is usually carrying real load, and a group that opens with “your influence is a problem” will spend the next year on the relationship instead of the structure.
Start by converting one decision, not the person’s standing. Pick a category — spending under a threshold, say — and write who decides it, by what method, within what limit. The founder should be in the room when it is written, and it should be framed as what it is: making the thing they have been carrying into something the community can carry.
Then check the conversion actually happened. The failure mode after this one is a transition that exists on paper: roles created, elections held, and everyone still checking informally before deciding anything. That is harder to fix than doing nothing, because the group now believes the problem is solved.
What prevents it
Authority that is assigned, scoped and time-bounded from the start — including the founder’s, especially the founder’s. A founding group that writes down what its founders may decide, and for how long, is not expressing distrust. It is making the founders replaceable, which is the only way a community outlives them.
Sources & further reading
- 1 RCOS stress test — Founder Informal Veto — the specification this page puts into plain language
- 2 Foundation for Intentional Community — Founder's Syndrome — the same pattern under the name the wider nonprofit sector uses
- 3 Freeman, J. — The Tyranny of Structurelessness (1970/1972) — delegate specific authority, for specific tasks, by an agreed procedure
Written by EcoHubs members, with AI assistance for drafting and editing, and reviewed by a person before publication. Facts are checked against the sources listed; anything we could not verify is marked. How this is written
The specification
This page is the plain-language version. RCOS publishes the stress test itself — the failure pattern, what is being tested, and what a compliant community would have in place.
Terms used here
- Founder transition
- Turning the authority that built a community into something anyone can hold or inherit. Communities that skip it cannot disagree with their founders or continue without them.
- Informal power
- Influence nobody granted and nobody can withdraw. It forms whether or not a community writes a structure down, and denying it only makes it unaccountable.
- Blocking concern
- In consensus, an objection serious enough to stop a proposal. Healthy systems define narrowly who may block and on what grounds.
- Agreements
- The written rules a community has consented to. Distinct from values: agreements say what happens, and what follows when it does not.
These travel together
Failures are rarely alone. If this one is familiar, check the others from the same lesson before concluding you have found the whole problem.
- Authority that comes from being compelling
Someone is so persuasive that disagreeing with them feels like a failure of understanding rather than a difference of view.
- Speakers who fill the room
Nothing is blocked and nobody is silenced — but only some people's proposals ever get finished, and the group calls it consensus.
- The clique that decides before the meeting
The real conversation happens in the kitchen and the meeting ratifies it — so attendance stops changing anything, and then stops.
- Decisions with no stated type
The same question is routine or constitutional depending on who you ask — so the answer depends on who gets to frame it.