Contribute/Facilitation Training: Difference between revisions

Jump to navigation Jump to search

Contribute/Facilitation Training (view source)

Revision as of 10:53, 15 July 2014

224 bytes removed ,  15 July 2014
→‎Part 2: Communication Skills
Line 141: Line 141:
== Giving and receiving feedback ==
== Giving and receiving feedback ==


Active listening is a useful skill for all sorts of situations – whether you're taking part in meetings and workshops or dealing with conflict. By actively listening we can come to understand how the speaker feels about a subject or situation – we hear through their words and tune into their underlying emotions, concerns and tensions.
[http://openmatt.org/2011/04/06/how-to-work-open/]


Though active listening is outside the immediate scope of this workshop, please find more information and an activity regarding active listening [[Contribute/Facilitation_Training/Active_Listening|here]]
How to ask for and give constructive, directed feedback.


=== Other strategies ===
What do mean by constructive, directed feedback?


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.
* specific, detailed
* constructive (works towards a solution)
* relevant, contextual (attempts to take into account entire circumstances)
* thoughtful (not reactive)


1. Assume good intent: people are usually not trying to hurt your feelings. Unless language is explicitly hurtful, racist, sexist, classist, or any other kind of -ist that is against the Code of Conduct, assume that people are coming from a place of constructive feedback.
Examples


2. On the Internet everyone does know you're a dog: The Internet is not a place to hide your identity. We are a community of well-wishers working together to make the Web better. Think about the way that you are using language when communicating. Do you sound uninterested or snarky? Do you seem unkind?
not constructive:


3. Make a sandwich: One way to constructively give feedback is to place it in between other, positive statements
* "No"
* "this idea sucks",
* "I don't like it"
 
not specific:
 
* "That's great!"
* "Thank you for your idea."
* "This is a terrible idea."
* "I'm not going to do this."
 
not relevant and/or contexual:
 
* "Good idea! Let me tell you about this other idea I'm working on."
* thread hijacking, providing feedback or commenting on another issue
* trolling
* non-sequitors
 
not thoughtful
 
* ad hominem responses
* this makes me so mad
* reactive statements
* taking things personal
 
Qualities of good feedback
 
* restatement of the issue as you see it
* personal history or experience with issue
* connecting the dots between problem and solution as you see it
* how proposed solution will affect you, your team, the organization
* agreement, block or stand-aside
 
How to ask for constructed, directed feedback
 
* provide context for what you are asking feedback on
* ask specific but open-ended questions:
** how will this change affect you?
** how will this change affect the community?
** what about the content does or does not make sense to you?
** what about the content does or does not resonate with you?
** to what extent does the content match your vision for wiki.mozilla.org?
** to what extend can you support the purpose, scope and governance structured described?
* indicate how you want to receive feedback
* indicate a deadline
* send a reminder
 
===''Practicing feedback in the open: a small group activity (10 minutes)'''===
 
Part 1: Asking for Feedback
 
Think of a recent project you needed to get feedback on. Write a list of specific, open-ended questions to help guide feedback.
 
Part 2: Giving Feedback
 
Give feedback on projects used in Part 1.


=== Know your rights in group discussions===
=== Know your rights in group discussions===
Line 164: Line 222:
*Any participant has the right to have power reflecting their work (and not age or volume)
*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
*Any participant has the right to raise an objection about process or a proposal
===''Practicing feedback in the open: a small group activity (10 minutes)'''===
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 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 a community?
Situation 4: One of your fellow Mozillians keeps interrupting during meetings. How do you tell them that you find their behavior disruptive?




Ckoehler
canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,698

edits

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

Navigation menu