- 1 Christie comments
- 1.1 Part 0: Introductions and Icebreakers
- 1.2 Rules for a safer space
- 1.3 Part 1.1: Why am I in this room?
- 1.4 Part 1.2: Layers Exercise
- 1.5 Part 1.3: Creating alliances and group norms
- 1.6 Part 2.1: What is Active Listening?
- 1.7 Part 2.2: Giving and Receiving Feedback in Open Source Communities
- 1.8 Part 3.1: Preparing for Facilitation
- 1.9 Part 3.2: Qualities of a good facilitator
Part 0: Introductions and Icebreakers
"In my community voices are listened to and appreciated" Is this asking people to speak for others? Note sure how 'heard' vs 'listen to' translates across locales.
"I feel like I can bring up conflict in my community" I would change "I feel like I can bring up conflict in my community and have it resolved successfully." Maybe it should be two questions.
"My community is diverse" Is there a better word than diverse here? What are we trying to reveal from audience with this question?
"Meetings run smoothly and are not boring" Would probably say "run well" instead of "smoothly."
Rules for a safer space
I have a lot of thoughts about this section, but they aren't all organized yet.
Part 1.1: Why am I in this room?
Does assigning roles to participants negatively affect their experience in the workshop? Can these roles be split between the two facilitators?
Part 1.2: Layers Exercise
We talked about adapting this exercise to use post-it notes to encourage participants who would be more comfortable interacting that way. Is that an adaptation we still want to make?
Part 1.3: Creating alliances and group norms
Using two terms here is confusing. Are designed alliances the same thing as group norms? Can we pick one term to use? Or only teach one thing?
Part 2.1: What is Active Listening?
We should compare the seeds of change handout with the TRIBE handout and make sure they are not contradictory.
Part 2.2: Giving and Receiving Feedback in Open Source Communities
I'm pretty uncomfortable with #1 and #2 here as written. #3 is okay but needs clarification.
I some of the content in the Hacker School rules. But I wonder how well it translates to a more global and/or non-technical audience? I'd almost rather pull this and use something more from the NVC world. I think that would be more widely applicable.
Part 3.1: Preparing for Facilitation
Can we give examples of ways to collapse roles when appropriate and when it doesn't make sense to switch facilitators so often?
Part 3.2: Qualities of a good facilitator
These seem more like 'actions' to me, rather than qualities.