Before We Fall Apart
A conflict-preparedness studio for groups. Build the capacity to repair before you rupture — proactively, together, in calm weather — and export a shared relational charter you keep. Nothing you write here leaves your browser.
Repair before you rupture
Most groups only learn how to handle conflict during a crisis — when trust is already thin, adrenaline is high, and nobody remembers what they agreed. This studio flips that. It is a calm-weather practice: you build your repair capacity before you need it, together, and write it down as a shared relational charter you can return to.
What is a relational charter?
A relational charter is a short, living agreement a group writes about how it wants to be together when things get hard — not a code of conduct imposed from above, but a set of commitments the group makes to itself. It names how you'll speak, what each person needs to stay in the room, the signal you'll use to pause, and the steps you'll take to repair harm rather than punish people. Like any charter, it works because you wrote it before you needed it, and because everyone had a hand in it.
Why build the capacity in advance?
- Conflict is not the failure — unrepaired rupture is. Every close group will hurt each other eventually. What separates groups that survive it is whether they built a way back before they needed one.
- In crisis, capacity shrinks. When we're activated, we default to fight, flight, freeze or fawn. Agreements made calmly become the scaffolding we lean on when we can't think clearly.
- Prevention surfaces needs early. Naming your tripwires and needs before they're stepped on turns invisible landmines into shared knowledge.
- It distributes the work. Repair shouldn't rest on whoever is most hurt or least powerful. Doing this together spreads the responsibility across the group.
Grounded in three traditions
This studio is the capstone practicum for Nonviolence in Practice: Communication, Resistance & Repair. It draws the three traditions of that flagship into one concrete artefact your group can keep.
Nonviolent Communication
Feelings are signals of universal needs. Naming the need beneath a tripwire — before it's triggered — lets the group meet each other with empathy instead of blame. Your Tripwires & needs tab is built on this.
New Authority & Presence
Strength without aggression: steady, non-escalating presence, refusing to fight and refusing to give in, supported by a network rather than a lone hero. Your agreed pause signal, cool-down norms and support pods carry this.
Restorative & Transformative Justice
When harm happens, the question is not “what rule was broken” but “who was hurt, what do they need, and whose obligation is it to repair?” Your rupture→repair protocol and accountability pods live here.
How to use this studio together
This works best done as a group, out loud, not filled in alone. Set aside roughly 90 minutes with your team, collective, friend-group or organisation. One person can drive this screen while the group discusses; export the charter at the end and each person keeps a copy.
- 0–10 minOpen. Read “Why prepare” aloud. Agree you're doing this in calm weather, not to settle a live fight.
- 10–30 minShared agreements. Move through the presets together; keep only what everyone can genuinely stand behind. Add your own.
- 30–55 minTripwires & needs. Go around the group. Each person names one tripwire and the need beneath it. Listen without fixing.
- 55–75 minRupture → repair & pods. Agree your pause signal, cool-down and repair steps. Each person names their accountability and support pods.
- 75–90 minCharter & close. Name and date the charter, read it back, export it. Agree when you'll revisit it (a good default: every few months).
Shared agreements
These are the commitments your group makes to itself about how you'll be together. Tap the ones everyone can genuinely stand behind — discuss the ones you're unsure about — and add your own. Only keep what the whole group can commit to; an agreement nobody honours is worse than none.
Preset commitments
Our shared agreements
Tripwires & needs
A tripwire is what makes you shut down, go silent, or feel unsafe — the thing that, when it happens, takes you out of the conversation. Underneath every tripwire is an unmet need. Naming both, in calm weather, means the group can recognise a tripwire before it becomes a rupture, and knows what you actually need in that moment.
Rupture → repair protocol
This is the ladder your group agrees to in advance: what you'll do when a tripwire is hit, how you'll cool down, who holds space, and the steps you'll follow to repair. The fields below are pre-filled with a sensible starting ladder — treat it as a template and rewrite every line in your own words. Editable template
Accountability pods
A pod is the small handful of people you'd turn to around harm — a concept from transformative-justice organising. Each person names two: the people who help them stay accountable when they've caused harm, and the people who help them stay resourced when they've been harmed. Naming them now means nobody has to figure out who to call in the middle of a crisis.
Your relational charter
Everything you've built, assembled into one shared charter. Name and date it, read it back to the group, then save, export or print it. Revisit it every few months — a charter is a living document, not a monument.
You built a way back
The measure of a group isn't whether it fights — it's whether it knows the way home afterwards. Keep this charter close, and return to it before you need it.