wiki content export 2026-05-02
This commit is contained in:
parent
3a98d0b8f0
commit
e5ca18f272
2 changed files with 2 additions and 2 deletions
|
|
@ -121,8 +121,6 @@ createdBy: Jennie R.F.
|
|||
* Where do you notice a gap between your intentions and your effects?
|
||||
* Check in with Peer Supports:
|
||||
* How did the teams receive the WWH exercise?
|
||||
* Share resources:
|
||||
* Sociocracy 3.0: [Agree on Values](https://patterns.sociocracy30.org/agree-on-values.html)
|
||||
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -241,6 +241,8 @@ When you're designing your conflict and removal policies, ask: Is it more worth
|
|||
|
||||
This doesn't mean tolerating ongoing harm. Your process should distinguish between someone who is genuinely working to change and someone who is performing accountability while continuing the behaviour. The former needs support and real consequences; the latter needs a different response.
|
||||
|
||||
We'll take about this more in two weeks during our conflict resolution session.
|
||||
|
||||
#### The complexity of removing someone you care about
|
||||
|
||||
The person you're removing is probably someone you care about. They're your collaborator and maybe your friend. The instinct to paint them as an irredeemable villain or monster makes the decision easier, but it's dishonest and in itself harmful to everyone. People who cause harm in your studio are human beings in your community - and yes, they hurt others, and that needs to be addressed. Holding both the care and the harm is one of the hardest tasks in cooperative work. Make room for that complexity rather than forcing everyone into a binary of good/bad.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue