Vision vs purpose vs mission

Almost every community has a founding statement, and almost none can tell you which of these three it is.

That sounds like a semantic complaint. It is not. These three things have completely different shelf lives and should be changeable by completely different means — and when they live in one paragraph, the whole paragraph inherits the strictest rule in it. A community that wants to stop running the café now has to reopen the sentence about why it exists, in the same meeting, with the founders in the room.

Purpose is the one that is constitutional

A purpose states the enduring reason the community exists. The sharpest test is that it cannot be completed. “To steward this land as a working farm held in common” cannot be ticked off. “To convert the barn into six dwellings” can — which makes it a project wearing a purpose’s clothes, and communities that adopt one of those spend the years after completion in a strange, unnameable drift, having quietly achieved the only thing they ever wrote down.

The second test is that a decision can genuinely contradict it. That is what makes a purpose load-bearing rather than decorative: if no allocation of money, land or labour could ever be inconsistent with your purpose, it is not doing constitutional work — it is a mood.

Which is why a purpose belongs at the top tier Decision tiers Sorting decisions by what they cost to get wrong, and giving each class its own method and timeline., alongside the invariants, and should be difficult to change. Not because founders’ words are sacred. Because everybody who joined did so on the basis of it, and a purpose an ordinary majority can amend on a Tuesday is a promise the community has not actually made.

One purpose, not several. Communities routinely carry two — a place to live well together, and a demonstration project for the wider world — and never rank them. Both are honourable and they conflict constantly: about visitors, about money, about how much of the year is spent hosting. The failure is not having two. It is never having said which one yields.

Vision is a picture, and nobody can breach it

A vision describes the place as you hope to find it in twenty years: the woodland grown in, the second generation staying, the workshop paying for itself. It is written to be read aloud, and its job is to make the effort legible to the people making it.

The mistake is treating it as an obligation. A vision that says “everyone contributes joyfully” is aspirational when it is on the wall and coercive the moment it is quoted at somebody in a meeting. Visions do not have breaches, because there is no way to comply with a picture. If your community can put somebody in the wrong by citing the vision statement, what you have written is an unenforceable identity constraint, and it will do the damage of a rule with none of the protections of one.

Keep it, though. Communities that discard the vision as fluff usually discover they have nothing to hand a prospective member that explains why any of this is worth it.

Mission is the one with a date

A mission is the current answer to what we are doing about it — and it is the only one of the three that is supposed to change. Three years of work, a handful of named outcomes, somebody accountable for each.

Two things follow from that. Missions should be easy to change, at the ordinary decision tier, because a plan you cannot revise without a constitutional process is a plan you will quietly abandon instead of amending. And missions should be allowed to finish. A community that completes its mission and celebrates it has done the thing; a community that treats “we did it” as an existential problem has been using the mission to carry the purpose all along.

The test that separates them, in one question each

Take whatever your community has written down and ask:

• Could we achieve this and be finished? If yes, it is a mission, whatever it is called.
• Could somebody be in the wrong for acting against it? If no, it is a vision — so do not put it where rules live.
• Would changing this make people wonder whether to stay? If yes, it is your purpose, and it should be protected accordingly.

Most communities find, doing this, that they have one document that answers all three inconsistently, and no record of when any of it was last agreed.

What goes wrong when they are one document

Three specific failures, and they are common enough to be predictable.

The plan cannot change. Everything is fused to the constitutional layer, so revising this year’s priorities means reopening the founding text. The community avoids this, sensibly, and the plan simply stops being accurate instead.

Or the purpose changes by accident. The opposite failure and the more expensive one. The document gets edited to reflect current activity — reasonably, a bit at a time — and eighteen months later the stated reason for existing has moved without any decision that anyone would recognise as constitutional. This is mission drift, and it is the least dramatic way a community becomes something the people who joined it did not join.

And nobody can say which version is in force. Where one document does three jobs, it is revised often enough to accumulate versions and treated as sacred enough that nobody dates them. The fix is clerical: an adoption record and a summary of what changed, on each — ratification Ratification A hold between a proposal passing and it taking effect, during which the result is confirmed before it becomes real. that leaves a trace.

The remedy for all three is the same, and it is a morning’s work: separate the three into three documents, write down which tier may change each, and date them.

Sources & further reading

1. 1 RCOS Core — Layer 0: Identity & Scope — purpose definition, scope, invariants and identity constraints — the source of every clause quoted here
2. 2 RCOS stress tests — Membership & Boundaries — mission drift and competing purposes, in specification form
3. 3 The purpose that quietly changed — what it looks like from inside when the reason for existing moves without a decision
4. 4 Who belongs, and who decides that — the lesson this sits under — scope, identity constraints, and the edges of a 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