Responsibility that becomes authority
The person who does a thing ends up deciding it — nobody granted that, and nobody can take it back without taking the work back too.
What it looks like
- Decisions in an area are made by whoever handles that area, without anybody deciding they should be.
- Members say one person has too much, and have said so for a long time.
- Nobody could take a task over without a substantial handover that has never been written.
- The overloaded person would like help and cannot say what help would look like.
Why it is hard to see
Because the authority is a side effect of the work, and the work is a gift.
Somebody takes on the maintenance. Because they do it, they know the state of the buildings, which contractor is reliable, and what last year’s repair cost. So when a maintenance question arises, asking them is not deference — it is efficiency. Their answer is better informed than anybody else’s would be.
Over time the community stops distinguishing between asking the person who knows and the person who decides. Nobody granted authority. It accreted out of competence, and it is genuinely difficult to point at the moment it stopped being consultation.
The second reason it persists is more uncomfortable. Removing the authority means removing the work, and the work is the part nobody else wants. A community that says “you should not be deciding this alone” without also saying “and here is who will do it instead” has asked someone to keep the burden and give up the compensating say. That is worse than the current arrangement, and the person will reasonably refuse.
And the third: the holder often experiences the opposite. Ask them and they will say, sincerely, that they wish other people would take some of it on. They are not defending a position. They are stuck in one.
What to check
Take one domain and separate two questions: who does the work, and who decides what happens. If the answer is the same name and no document says it should be, this is running.
Ask what a handover would require. A responsibility that can be handed over in a briefing is a task. One that would take three months and a lot of undocumented context is a dependency, and the community is exposed to it whether or not anyone is unhappy.
Then ask the holder what help would look like. The revealing part is not whether they want help — almost everyone does. It is whether they can specify it. “I don’t know, some of the admin” is the diagnosis: the work has never been broken into pieces, so it cannot be shared.
If it is already happening
Somebody who is not the holder has to run the redistribution. This is the step communities skip, and skipping it is why the attempt fails around week three. Asking the overloaded person to organise their own unloading is one more task for the person with the least room.
Enumerate before you delegate. “Maintenance” cannot be handed over. “Getting three quotes when a repair exceeds €500”, “the annual boiler service”, and “keeping the contractor list” can be — three named things with three holders and three handover dates.
Split the deciding from the doing, explicitly. For each piece: who does it, and what may they decide alone? A spending limit is usually enough. It converts an informal authority into a stated one of roughly the same size, which is far less threatening than it sounds and is the actual fix.
Expect the holder to be relieved and also strange about it. Somebody who has carried a thing for years has their competence bound up in it, and handing it over is a loss as well as a relief. Naming that out loud makes the transition much easier than pretending it is purely administrative.
What prevents it
Roles that carry a stated decision authority and a term, so that doing the work and deciding it are separately assigned from the start — and a handover requirement that forces the undocumented context out of one person’s head while there is no crisis.
Sources & further reading
- 1 RCOS stress test — Invisible Power via Responsibilities — the specification this page puts into plain language
- 2 Freeman, J. — The Tyranny of Structurelessness (1970/1972) — delegate specific authority to specific people for specific tasks, and rotate them
- 3 Founder transition — the same conversion problem, at the scale of a whole community
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.
RCOS stress test — operations-coordination/invisible-power-via-responsibilities
Terms 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.
- Invisible work
- The noticing, remembering and smoothing that keeps a community running and never appears on any rota. It distributes itself unevenly.
- Agreements
- The written rules a community has consented to. Distinct from values: agreements say what happens, and what follows when it does not.
- 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.
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.
- Care work nobody counts
The noticing, remembering and smoothing that never reaches a rota — done by the same people, unrecorded, until one of them stops.
- Growth that outpaces onboarding
New members arrive faster than the community can teach itself to them — so they learn a version, and the version drifts.
- Self-sufficiency without contribution
Households withdraw into their own lives, one reasonable decision at a time, and the commons is maintained by whoever still minds.
- Information nobody can reach
The accounts, the passwords, the history and the reason the rule exists — held by whoever happened to be there, and reachable only through them.