> 🧩 A Moral Fabric pattern, free for any nonprofit to use and adapt.
What works at two people breaks at five, and it breaks silently. Two colleagues in constant contact need no rhythm at all — a shared list and a chat window is genuinely enough, and adding ceremony would only slow them down. Five people running work in parallel need a shared board and a fixed weekly slot, or coordination reverts to whoever happens to remember. The failure mode is doing nothing until something visibly hurts, then adding four things at once in a reorganization nobody enjoys.
Add infrastructure at thresholds, not by headcount rules, and add one thing at a time.
A shared task list. Nothing else. Skip the ceremony honestly rather than performing a process you don't need.
Remoteness moves the threshold down: two people in different countries need what five co-located people need. Add a weekly tactical with a fixed format, one shared board as the single source of truth, written communication norms, and a named facilitator.
Add written updates before the meeting instead of during it, one recurring discursive slot with a rotating topic owner, and explicit role and accountability mapping — at this size "who owns this" stops being obvious. An optional coworking slot helps where people work alone on similar things.
Split into sub-teams, each with its own tactical, plus one cross-team moment that everyone attends. Move governance into its own slot, because at this size it will otherwise consume the tactical.
Add infrastructure when you see one of these, whatever the headcount:
- Someone learns the same thing twice — knowledge isn't being shared; add written updates or a demo slot.
- Two people discover they did the same work — the board isn't the single source of truth.
- The same decision gets re-litigated — decisions aren't recorded where the work lives.
- Questions arrive as direct messages — no channel norms.
- The weekly runs over consistently — the tactical is absorbing discussion; split it.
- A new colleague asks how something works and gets three different answers — no owner for that documentation.
Decision test: could someone joining next Monday find out what everyone is working on, without asking anyone? If not, that's the next thing to add.
Locate each team in the stages above, then check the signals. The signals win where the two disagree.
Add one thing, and only one. Simultaneous changes make it impossible to tell which helped.
Give it an owner. Practices without a named person die in about three weeks.
Review after a month. Keep, adjust, or remove — removing is a success, not a retreat.
Re-check when the team changes shape: a new hire, someone going part-time, someone moving country.
Nothing here is legally required, but growth has legal thresholds of its own that tend to arrive at the same time. In the Netherlands, a works council becomes mandatory at 50 employees and a staff representation body at 10, and reporting duties around pay and sustainability scale with size. Worth knowing what's on the horizon so team infrastructure and statutory obligations aren't discovered in the same week.
Record your organization's choices:
- Where each of your teams currently sits, and what you last added
- Which signals you actively watch, and who watches them
- Who decides to add or remove a practice
- What you deliberately don't do yet, and why