Contribute/Facilitation Training: Difference between revisions

Jump to navigation Jump to search

Contribute/Facilitation Training (view source)

Revision as of 20:16, 10 July 2014

3,584 bytes removed ,  10 July 2014
→‎other strategies
(adding more notes to consensus section)
Line 174: Line 174:
Saying thank you: "This is what you did; this is what I feel; this is the need of mind that was met."
Saying thank you: "This is what you did; this is what I feel; this is the need of mind that was met."


=== other strategies ===
=== Other strategies ===


Facilitator: There are many ways that people coexist in online communities, and we are going to talk about how to build communities while working against trolling, meanness, and other issues.
Facilitator: There are many ways that people coexist in online communities, and we are going to talk about how to build communities while working against trolling, meanness, and other issues.
Line 184: Line 184:
3. Make a sandwich: One way to constructively give feedback is to place it in between other, positive statements
3. Make a sandwich: One way to constructively give feedback is to place it in between other, positive statements


<big>'''Feedback in hacker communities...'''</big>
=== Know your rights in group discussions===


[https://www.hackerschool.com/manual#sub-sec-social-rules Hacker School Social Rules]
<big> Know your rights!</big>
*Any participant has the right to ask questions without being considered foolish
*Any participant has the right to make a proposal and see it come to a vote
*Any participant has the right to contribute without having to be loud or pushy
*Any participant has the right to be treated respectfully
*Any participant has the right to have power reflecting their work (and not age or volume)
*Any participant has the right to raise an objection about process or a proposal


'''No feigning surprise'''


The first rule means you shouldn't act surprised when people say they don't know something. This applies to both technical things ("What?! I can't believe you don't know what the stack is!") and non-technical things ("You don't know who RMS is?!"). Feigning surprise has absolutely no social or educational benefit: When people feign surprise, it's usually to make them feel better about themselves and others feel worse. And even when that's not the intention, it's almost always the effect. As you've probably already guessed, this rule is tightly coupled to our belief in the importance of people feeling comfortable saying "I don't know" and "I don't understand."
<big>'''Practicing feedback in the open: a small group activity (10 minutes)'''</big>
 
'''No well-actually's'''
 
A well-actually happens when someone says something that's almost - but not entirely - correct, and you say, "well, actually…" and then give a minor correction. This is especially annoying when the correction has no bearing on the actual conversation. This doesn't mean Hacker School isn't about truth-seeking or that we don't care about being precise. Almost all well-actually's in our experience are about grandstanding, not truth-seeking. (Thanks to Miguel de Icaza for originally coining the term "well-actually.")
 
'''No back-seat driving'''
 
If you overhear people working through a problem, you shouldn't intermittently lob advice across the room. This can lead to the "too many cooks" problem, but more important, it can be rude and disruptive to half-participate in a conversation. This isn't to say you shouldn't help, offer advice, or join conversations. On the contrary, we encourage all those things. Rather, it just means that when you want to help out or work with others, you should fully engage and not just butt in sporadically.
No subtle sexism
 
Our last social rule bans subtle sexism, racism, homophobia, etc. This one is different from the rest, because it's often not a specific, observable phenomenon ("well-actually's" are easy to spot because they almost always start with the words, "well, actually…").
 
If you see something that's unintentionally sexist, racist, homophobic, etc. at Hacker School you're welcome to point it out to the person who made the comment, either publicly or privately, or you can ask one of the faculty to say something to that person. Once the initial mention has been made, we ask that all further discussion move off of public channels. If you are a third party, and you don't see what could be biased about the comment that was made, feel free to talk to faculty. Please don't say, "Comment X wasn't homophobic!" Similarly, please don't pile on to someone who made a mistake.
 
We want Hacker School to be a space with as little bigotry as possible in it. Therefore, if you see sexism, racism, etc. outside of Hacker School, please don't bring it in. So, for example, please don't start a discussion on the mailing list of the latest offensive comment from Random Tech Person Y.
 
Why don't we want public discussions of sexism, racism, etc. at Hacker School? For many people, especially those who may have spent time in unpleasant environments, these conversations can be very distracting. At Hacker School, we want to remove as many distractions as possible so everyone can focus on programming. There are many places in the world to discuss and debate these issues, but there are precious few where people can avoid them. We want Hacker School to be one of those places.
Why have social rules?
 
The goal isn't to burden Hacker School with a bunch of annoying rules, or to give us a stick to bludgeon people with for "being bad." Rather, these rules are designed to help all of us build a pleasant, productive, and fearless community.
 
If someone says, "hey, you just feigned surprise," or "that's subtly sexist," don't worry. Just apologize, reflect for a second, and move on. It doesn't mean you're a "bad" person, or even a "bad" Hacker Schooler. As we said above, these rules are meant to be lightweight. We've all done these things before. In fact, we originally adopted a no well-actually policy for our company because Nick and Dave well-actually'd each other all the time.
 
<big>'''Practicing positivity in the open: a small group activity (10 minutes)'''</big>


Situation 1: Another contributor has just come up with an idea for a new app. You think that this idea is a bad one. She asks for feedback on the app from your community. How do you respond?  Think of five good responses and five bad responses.
Situation 1: Another contributor has just come up with an idea for a new app. You think that this idea is a bad one. She asks for feedback on the app from your community. How do you respond?  Think of five good responses and five bad responses.


Situation 2: A contributor you're friendly with is running an event and you think they're doing a poor job. How do you tell them?
Situation 2: A contributor you're friendly with is running an event and you think they're doing a poor job. How do you tell them?
Situation 3: In a meeting, another participant dismisses a woman's comment by saying "That's just like a woman to say" after a disagreement. What do you do as an individual? As


== Part 2.3: Active Listening Activity ==
== Part 2.3: Active Listening Activity ==
Jennierose
canmove, Confirmed users
868

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/996152"

Navigation menu