The work that breaks people

Here is the thing that makes this lesson different from the others.

With power, with conflict, with money, the community usually cannot see the pattern. With this one it can. Members will describe it accurately, in detail, unprompted. They will name the person carrying too much. They will say it is not sustainable. And then nothing will change, for years.

That gap — between accurate diagnosis and no repair — is the whole subject.

The five

• Care work nobody counts — the noticing, remembering and smoothing that never reaches a rota
• Responsibility that becomes authority — the person who does it ends up deciding it, without anybody granting that
• Growth that outpaces onboarding — new members arrive faster than the community can teach itself to them
• Self-sufficiency without contribution — households quietly withdraw into their own lives, and the commons is maintained by whoever minds
• Information nobody can reach — the accounts, the passwords, the history, the reason the rule exists

Why knowing is not enough

That is the mechanism, and it generalises. The people best placed to redistribute the work are the people currently doing it, and they are the people with no capacity to run a redistribution project. So the group circles: it notices, it says so, it feels bad, and the situation persists — while everyone involved behaves reasonably and cares about each other.

Three things follow, and they are the practical content of this lesson:

Complaining is not an intervention. A community that has raised something twenty times and seen no change does not have a communication problem. It has a missing structure, and more conversation will not produce one.

The work has to be enumerated before it can be shared. You cannot hand over “the admin”. You can hand over “renewing the insurance in March”, “reconciling the account quarterly”, and “keeping the key register” — three named things with three holders. The enumeration is most of the labour, and it is the step that gets skipped.

Somebody who is not overloaded has to run it. This is the part communities get wrong most reliably. Asking the overloaded person to organise their own unloading is asking for one more task from the person with the least room, and it is why the attempt fails on the third week every time.

Would that actually redistribute anything?

One member is carrying far too much and everybody knows it. Here are five things a community might do next. All of them are well meant. Two kinds of response fail reliably, and both feel like progress at the time.

1. At the next meeting the group agrees that this member has too much on, and that everyone should step up more.

A description, not an intervention correct answer Right, and a community can do this twenty times. "You have too much" is a description, and a description cannot be acted on — there is nothing in it anybody could start on Monday. A group that has raised something repeatedly and seen no change does not have a communication problem; it has a missing structure, and more conversation will not produce one. It would change something Nothing here would. "Everyone" is not a holder and "more" is not a quantity, so there is no version of next week in which anybody has done this or failed to. It is the single most common response to overload and it has no mechanism in it at all. It asks the overloaded person for one more thing Not directly — nothing is asked of them here. That is a different failure, and this one is gentler and just as ineffective.

2. The group asks the overloaded member to write down everything they do, so it can be shared out.

It asks the overloaded person for one more thing correct answer Right, and this is the version communities get wrong most reliably, because it looks like exactly the right step. Enumeration is most of the labour — and asking the person with the least room to produce it adds a task to the top of the pile. It is why the attempt fails in the third week, every time, and why the group concludes the person does not really want to let go. It would change something The list is the right artefact and this is the wrong author. Everything that follows depends on a document only the busiest person can write, which means it does not get written. A description, not an intervention It is more than a description — it names a concrete deliverable. The problem is who it is addressed to.

Where this comes from

3. A member who holds no roles spends two hours with them, writes down each separate thing they do, and comes back to the group with a list of eleven items.

It would change something correct answer Right — and note that nothing has been handed over yet. This is the step that gets skipped, done by the only kind of person who can do it: somebody with capacity. Eleven named items can each find a holder. "The admin" cannot. The list is also usually shorter than the group feared and more alarming in what it reveals about single points of failure. A description, not an intervention A list of eleven named responsibilities is the opposite of a description — it is the thing that makes every later step possible, and it took one person two hours. It asks the overloaded person for one more thing Two hours of their time, once, to produce something that removes work permanently. That is the trade worth making, and it is affordable precisely because somebody else is holding the pen.

Where this comes from

4. The group creates a wellbeing working group to look at workload across the community and report back in due course.

A description, not an intervention correct answer Right. A body with no list, no named owner and no date is a description with a membership. Projects need an owner and a deadline; without them this reports back in due course, which is to say at the meeting after the one where somebody remembers to ask. Compare the two hours in the previous question, which produced something. It would change something A working group is not a holder — it is a set of people who may each reasonably assume another of them is doing it. "In due course" is not a date. It asks the overloaded person for one more thing Usually it does, in the end: the overloaded member joins the working group about their own overload, because they know the most. But the primary failure here is that nothing in it has an owner.

5. The community writes into its agreements that no one person may hold more than three named roles at a time.

It would change something correct answer Right, though what it changes is subtler than a handover. Without a stated limit there is no moment at which anybody is entitled to say this is too much without it sounding like a complaint about their own capacity — which is exactly why the overloaded person never says it. A ceiling makes overload a fact about the structure that anyone may point at. A description, not an intervention A written rule is not a description of the situation; it is a constraint on it, and it applies to people who have not joined yet. It does not redistribute anything by itself, which is why it belongs alongside the audit rather than instead of it. It asks the overloaded person for one more thing It asks them for nothing. What it does is remove the need for them to be the one who raises it, which is the specific thing they have been unable to do.

Where this comes from

If it is already happening

Do the audit, not the conversation. One person, two hours, a list: everything that has to happen for this community to keep functioning, and who currently does it. Not who is supposed to. Who does.

Look for the single points of failure. Anything with one name against it and no second person who could do it. That list is usually shorter than people fear and more alarming than they expect.

Then take the top three and give each one a name, a scope and a handover date. Not all of it. Three. A community that redistributes three responsibilities properly has learned how, and can do the rest; a community that tries to redistribute everything produces a spreadsheet nobody maintains.

And write the limit down. How many roles one person may hold, or how many hours a month is too many. Without a stated limit there is no moment at which anybody is entitled to say this is too much without it sounding like a complaint about themselves — which is exactly why the overloaded person never says it.

What prevents it

Named roles with terms and handovers, a stated ceiling on how much any one person carries, and a definition of contribution that counts the invisible work Invisible work The noticing, remembering and smoothing that keeps a community running and never appears on any rota. It distributes itself unevenly. as work. None of that is about fairness. It is about a community being able to continue when somebody is ill.

Sources & further reading

1. 1 RCOS stress tests — Operations & Coordination — the five documented patterns this lesson covers, in specification form
2. 2 RCOS Core — Layer 5: Operations & Coordination — the Role Registry, workload boundaries, and the single-point-of-failure clause
3. 3 Freeman, J. — The Tyranny of Structurelessness (1970/1972) — delegate specific authority for specific tasks, rotate them, and spread information widely
4. 4 Daily life in community — the work nobody put on the rota, and what a week actually contains

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