Skip to main content

Lesson 01 of 6

Power nobody voted for

Five patterns that hand authority to people the group never chose — and why every one of them is built by somebody being helpful.

6 min read Lesson 1 of 6

Start with the thing that makes this lesson difficult.

In almost every community where power has settled somewhere nobody chose, the people holding it are working harder than anyone else. They answer the emails at midnight. They remember why the rule exists. They are the reason the boiler works. Asking a group to constrain them feels like ingratitude, and it usually is experienced as ingratitude, which is why the conversation gets postponed for years.

So the framing that works is not who has too much power. It is what happens when they leave — and that question can be asked with warmth, out loud, in a meeting, without anybody being accused of anything.

The five, and what they have in common

They are separate patterns with separate fixes, but they share a mechanism: a decision that was never assigned found a home. Nobody took the authority. It was left on the table, and somebody sensible picked it up.

If you recognise one, read the others before concluding you have found the whole problem. They co-occur, and they reinforce each other: a founder’s unwritten veto is far more powerful in a group whose decisions have no stated type, because there is nothing to say the veto does not apply here.

Why it is hard to see from inside

Three reasons, and the third is the one that keeps communities stuck.

It looks like competence. Everything above is indistinguishable, day to day, from a group that has sensibly deferred to the person who knows most. The difference only shows up under stress — when the group wants to go a way that person does not.

Nobody experiences themselves as powerful. Ask the founder and they will tell you, sincerely, that they wish other people would take more on. That is usually true. Informal power is not a thing people feel themselves holding; it is a thing other people feel themselves working around.

And the group already knows. This is the part that surprises people. In our experience the pattern is almost never a secret — members will describe it accurately, in private, sometimes for years. What they lack is not perception. It is a legitimate way to raise it that does not read as an attack on someone who has given a great deal.

That is the whole argument for writing things down. Not because a written rule is wiser than a good person, but because a written rule can be discussed without anybody being the subject.

Is it the structure, or is it the person?

Five situations. In each one, decide whether you are looking at something the structure produces — which would happen to whoever was standing there — or something about this particular person. They look identical from inside, and the wrong answer costs years.

1. Over six years three different people have held the money role. Each time, within about a year, the group is complaining that spending decisions get made without them.

Where this comes from

2. One member routinely talks over others. They have been asked privately three times, by three different people, and agreed each time. Nobody else who has facilitated has done this.

Where this comes from

3. Nothing proceeds if the founder disapproves, though no document says they may decide anything alone. Asked about it, the founder says — sincerely — that they wish other people would take more on.

Where this comes from

4. A question about the guest policy went to the whole group last spring and was settled by two people in the autumn. Both times, everyone involved thought they were following the normal process.

Where this comes from

5. A member is genuinely unpleasant in meetings — several people have stopped coming. They are also the only person who understands the accounts, and have been for eleven years.

Where this comes from

If it is already happening

Stabilisation before prevention. A community in the middle of this does not need a governance redesign; it needs the next three months to be less bad.

Name the smallest true thing. Not “we have a power problem” — “I noticed the last four decisions about money were made between meetings.” A specific, checkable observation is arguable. A diagnosis is not, and it will be experienced as an accusation.

Ask the succession question, not the power question. What happens to this if you are ill for a month? It is a real question, it is kind, and it produces the same information.

Write down one decision. Not the whole matrix — one. Pick the category that keeps going wrong and state who decides it, by what method, within what limit. A community that has never written any of this down will find the first one takes an evening and the second takes twenty minutes.

What prevents it

A decision matrix , and the thing communities forget to pair with it: a register of who currently holds each role. The matrix says what a role may do; the register says who is in it today, which is the question a new member actually has.

Then the two rules that make it hold:

  • A decision nobody can classify goes to the higher tier. Without that, every borderline case drifts toward the easier meeting.
  • The table says how the table is amended. A document that cannot describe its own amendment will be amended informally, by whoever notices first.

Sources & further reading

  1. 1 RCOS stress tests — Governance & Power — four of the five patterns this lesson covers, in specification form
  2. 2 RCOS stress tests — Culture & Influence — the fifth — authority from charisma, which the standard files under culture rather than governance
  3. 3 Freeman, J. — The Tyranny of Structurelessness (1970/1972) — why a structureless group is impossible, and what informal elites form around
  4. 4 RCOS Core — Layer 2: Governance & Decision Logic — authority boundaries, the decision matrix, and the safeguards against concentration
  5. 5 Conflict, power and repair — the joiner-facing version, for reading a community from the outside

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

Words used here

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.
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.
Decision matrix
A table mapping each kind of decision to who may make it, by what method, and within what limits.
Blocking concern
In consensus, an objection serious enough to stop a proposal. Healthy systems define narrowly who may block and on what grounds.
Facilitation
Running a meeting's process without taking a side on its content. The role that decides whether a decision method works at all.
Agreements
The written rules a community has consented to. Distinct from values: agreements say what happens, and what follows when it does not.
Stay close to the work

Letters from a young project.
Rare, but real.

We're early — a small project finding its shape. When something actually shifts — a new chapter of the RCOS Standard, a note from the Ecuador pilot, an invitation to gather — we'll write. No schedule. No filler.

RSS Feed
EcoHubs
EcoHubs Community

We are co-creating the RCOS Standard for regenerative living. Join us to design communities that thrive in harmony with nature.

DiscordMastodonFarcasterXYouTubeInstagramLinkedInGitHub
© 2026 EcoHubs.community · Built in the open, with care and regenerative principles.