The consultants install the process. It is a good process: clear gates, honest templates, sensible escalation. During their visits, the organization performs it beautifully. Between visits, the work flows exactly as it did before, through the same hallway conversations and the same two people everyone actually trusts.
Everyone is behaving rationally. The process is an artifact. The village is the system.
What the village provides
Every working decision system rests on a web of relationships that appears in no diagram:
- The correction delivered in the hallway before the meeting, which saves everyone the public defeat.
- The informal veto: the person whose quiet "I would not" stops more bad ideas than any gate.
- The memory of who was right last time, and who was wrong, held accurately and without cruelty.
- The standing that lets a junior person say "I think this is wrong" to a senior one, which is earned in a hundred small exchanges and cannot be granted by a policy.
The visible process is maybe a fifth of the system. The village is the other four fifths, and the process works only where those four fifths already exist.
Ritual versus practice
The same behavior can be a practice or a ritual, and the difference is invisible in a snapshot.
A practice happens when nobody is watching, because it is how the work actually moves. A ritual happens when someone is watching, because it is what the watchers expect. The weekly retrospective that changes real behavior is a practice. The identical retrospective that produces identical slides for a sponsor is a ritual. The templates are the same. One has a village inside it. The other has an audience.
This is workflow theater at the level of decision systems, and it is the standard outcome of importing process into a community that was never asked whether the process describes them.
There is a cheap, uncomfortable diagnostic. Ask: would this process survive an audit nobody announced? If the honest answer is no, you do not have a decision system. You have a performance schedule.
Who is missing from the room
A village is not just who is present. It is who is included, and every village defines its insiders somehow.
A decision system built with the people in the room will encode the room: its assumptions about what is obvious, whose time is worth burning, which risks are someone else's to carry. The people not in the room inherit those assumptions without ever agreeing to them. This is how a process can be genuinely fair by its own rules and still systematically serve one part of an organization, or one kind of member of a community, over another.
Resource access is usually the quiet divider. Who can afford to sit in three hours of consensus? Who can afford the career risk of dissent? Who has the slack to document decisions, and whose unpaid hours hold the process together? A system that looks the same for everyone is not experienced the same by everyone, and pretending otherwise is how the shell keeps its shine.
The fix is not a better process. It is a wider room before the process is designed, and it is usually uncomfortable, which is why it is usually skipped.
You cannot install history
The hardest thing about the village is that its essential ingredient is history. Trust is accumulated experience of promises kept and misses survived together. It has no import path.
What can be done is slower and real:
- Start with decisions small enough that being wrong is survivable, and run them through the new process together.
- Let people experience a miss inside the process and watch it be handled honestly. One survived public miss buys more trust than a year of values decks.
- Repeat until the process has memories. A decision system with shared memories is a village forming. Without them it is a form.
This is why the ground series keeps returning to the same move: you cannot shortcut time, you can only stop wasting it. The organization that wants the process has to grow the village that operates it, and growing is measured in shared decisions, not in rollout weeks.
FAQ
Is this an argument against process?
No. It is an argument about sequence and honesty. Process on top of a real village makes the village stronger: it protects the weak, remembers for the distracted, and scales judgment. Process without a village is decoration that slowly teaches everyone the documents are fiction. Build with people, not at them.
How do you tell a village from a silo?
A village carries shared consequence and lets outsiders in through demonstrated reliability. A silo protects itself by exclusion and lets no consequence escape. Both look like strong culture from the outside. The tell is what happens to the first newcomer: a village absorbs them within a season, a silo keeps them at arm's length indefinitely.
Can a village exist across organizations, like a partner network?
Yes, and the same physics applies. Partner networks run on accumulated trust and remembered misses, not on the contract, however thick the contract is. The contract is the process. The network is the village. Negotiate both, and expect the second one to take years.
What does this mean for community projects, not just companies?
It means the same and more. Community and cultural projects die most often from imported process: a governance model, a funding structure, a programming calendar designed elsewhere and delivered here. The process describes a village that does not exist on this ground. Start with the people, the access, and the shared consequence, and let the process grow to the size of the trust.
Related reading
- A Decision System Only Works on the Ground That Grew It
- Culture Is Not Content
- Workflow Theater vs Workflow Gain
- A Room Teaches Before Anyone Speaks
- Spaces That Carry Culture: Spatial Design with Meaning
- Public Space Is Not a Food Court
If your process looks perfect on paper and does nothing between visits, book a discovery call.