> 🧩 A Moral Fabric pattern, free for any nonprofit to use and adapt.
Teams add meetings one at a time and almost never remove one. The weekly sync that started as blocker-clearing ends up carrying status updates, brainstorming, decision-making and social connection at once. It runs long, everyone attends out of obligation, and none of the four things is done well. Meanwhile the meetings the team actually needs — a proper deep dive, a retro — never get scheduled, because the calendar is full.
Fix the format of two meetings. Invent everything else on purpose.
These carry the operational load, and they only stay cheap if they stay tight:
- clears blockers and syncs what changed. One output: everyone leaves unblocked with next actions owned. The Asana mechanics are in Weekly meetings: your team rhythm in Asana .
- changes roles, accountabilities and policies. One output: a written change to how the team is organised. Keeping it separate is what stops the tactical from drifting into "how should we work" every week.
Deep dives, retros, coworking slots, demos, walks, learning sessions — no prescribed format, and nobody needs permission to start one. Put it in the calendar, try it, drop it if it doesn't earn its slot.
If two people can resolve something between them, they do. A shared agenda costs everyone in the room their attention, so the bar for reaching it is that the whole team genuinely needs to hear it or weigh in.
one weekly tactical of 30–45 minutes, a governance slot at the end of it or monthly, and one recurring discursive slot — one topic, one owner, queued a week ahead. That third slot is where cross-pollination actually happens, and rotating who brings the topic makes it double as knowledge transfer.
Decision test: name the single output of every recurring meeting on your calendar. If you can't, cancel it or split it in two.
List every recurring meeting and write its one output next to it. Overlaps and zombies become obvious immediately.
Cancel or merge anything whose only output is shared awareness. That is a written update, not a meeting.
Protect the tactical. The facilitator's job is to interrupt: monologues, topics that concern only two people, and consensus-seeking on decisions someone already has the authority to make.
Add one discursive slot per team, with a named owner for the topic queue.
Rotate facilitation monthly, so the skill spreads and the format survives absences.
Review the set every quarter. Adding is easy and removing never happens by itself.
Nothing here is legally required. Two exceptions sit outside this pattern and keep their own rules: statutory bodies such as a works council, and your board or supervisory board, whose meetings, notice periods and minutes are governed by your statutes and national law.
Record your organization's choices:
- Which two formats you fix, and where governance happens — inside the tactical, or its own slot
- Your discursive slot: cadence, who owns the topic queue, whether attendance is optional
- Facilitator rotation and how it's assigned
- Which updates are async only, and where they get written
- Who can start and cancel a recurring meeting