Conflict that is never named

Why it is hard to see

Because from inside it does not feel like avoidance. It feels like kindness, and quite often it is.

Communities are built by people who wanted somewhere warmer than the world they came from, and confrontation is what they were trying to leave behind. So the group develops a genuine, admirable skill at absorbing friction — accommodating the person who is difficult about the kitchen, working around the one who never does their rota hours, not mentioning the thing everybody noticed. Each individual instance is generous. It is only the accumulation that is fatal.

The second reason: it never produces a bad day. Nothing escalates, because escalation is the thing being avoided. What it produces instead is a slow narrowing — of what can be said, of who talks to whom, and of how much anybody is willing to invest in a place where the real conversation happens somewhere they are not.

And the third, which is why groups defend it: the metric looks excellent. No disputes, no process triggered, no incidents. A community measuring its health by absence of conflict will rate this pattern as its greatest success right up until the year three households leave.

What to check

Ask when the conflict process was last used. “Never” from a ten-year-old community of forty does not mean there has been no conflict. It means the process is unusable, and everybody worked that out privately.

Count the private conversations. Not their content — their existence. If a difficulty is known to eleven people and has never been on an agenda, the group has a route, and it runs entirely outside its own structure.

Ask a recent leaver. Communities almost never do this, and it is the single highest-yield question available: what would you have said if there had been somewhere to say it? People are usually willing to answer once they have gone, which is itself the finding.

If it is already happening

Start with something small enough to be safe to fail. A group with no muscle for this should not begin with its hardest case. Take a minor, genuinely two-sided difficulty and run the process badly on it. What you learn is where it breaks.

Separate raising from resolving. A great deal of avoidance is not fear of conflict but fear of consequence — people stay quiet because naming a thing feels like starting something they cannot stop. A process with an explicit low step, where raising a difficulty produces a conversation rather than a procedure, removes most of that.

Say the accumulation out loud, once. Not as an accusation of the culture — as an observation about cost: we have lost four members in three years and none of us said the difficult thing before they went. That is checkable, and it is much harder to absorb than a complaint about the atmosphere.

Expect it to feel worse before better. A community that starts naming things will have a visibly more difficult six months. It is worth telling people that in advance, because otherwise the first hard meeting gets read as proof the old way was working.

What prevents it

A repair process Repair process The agreed route a conflict takes. The test is not which method a community uses but whether someone who is not in charge can start it. with a genuinely cheap first step, and the habit of using it on things too small to need it. A process only ever tested on catastrophes will not be reached for during one.

Sources & further reading

1. 1 RCOS stress test — Conflict Avoidance Normalization — the specification this page puts into plain language
2. 2 Ostrom, E. — Governing the Commons (1990) — accessible conflict resolution — cheap and local — as a design principle of durable commons
3. 3 Seeds for Change — free practical guides on working through group conflict

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