Participation/Resources/Designing for participation/Documentation: Difference between revisions

correct categories
No edit summary
(correct categories)
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Category:Participation]]
[[Category:Resources]]
[[Category:Workshops]]
[[Category:Metrics]]
Anyone at Mozilla - module owner, newcomer, veteran, staff, volunteer should feel welcome to initiate or run the Designing for Participation Workshop.  
Anyone at Mozilla - module owner, newcomer, veteran, staff, volunteer should feel welcome to initiate or run the Designing for Participation Workshop.  


Line 36: Line 40:
*I'm a contributor and I'd love to expand how much I contribute or have been trying to explore new parts of the project to contribute to with little success.
*I'm a contributor and I'd love to expand how much I contribute or have been trying to explore new parts of the project to contribute to with little success.


==Slide Deck==
The slides for this presentation can be downloaded here in
*[https://wiki.mozilla.org/File:DesigningForParticipationPDF.pdf#file Designing For Participation PDF Version]
*[https://wiki.mozilla.org/File:DesigningforParticipationKeynote.zip#file Designing For Participation Keynote Version]


==assumptions==
==Assumptions==
It is worth noting that this course is not for everyone. Participants in this course are assumed to know what an open source project is and, at a high level at least, how it works.
It is worth noting that this course is not for everyone. Participants in this course are assumed to know what an open source project is and, at a high level at least, how it works.


Line 44: Line 52:
*this course works best with something between 3-25 participants. Anything more than that and it gets unwieldy, especially if you are not used to facilitating/teaching
*this course works best with something between 3-25 participants. Anything more than that and it gets unwieldy, especially if you are not used to facilitating/teaching
*please ensure that participants have access to the internet so they complete the workshop, or print them out in advance
*please ensure that participants have access to the internet so they complete the workshop, or print them out in advance
=Basic Tips on Facilitation=
Link?


=Syllabus breakdown=
=Syllabus breakdown=
Line 115: Line 120:


==Personal Application==
==Personal Application==
Purpose:
*In this section we attempt to take the lessons learned from the case study and apply them to the area of interest for each participant.
*Another purpose is to give each participant some actionable ideas they can take away from the workshop
Logistical note:
*If participants are all from different parts of Mozilla, they can work on their own worksheet. If they are from the same area/group/module they can work collectively on the problem
*time: about 15-20 minutes (however, if you are not bound to a one hour workshop, this session could last much longer.


===Slide 5===
===Slide 5===
*time  
*time: about 15-20 minutes
- Google Doc template - encourage people to make a copy so they can edit without creating chaos


- purpose: give people - if they write it down, they have some structured thinking they can take away from the workshop
'''Step 1'''
*Provide Instructions for the exercise:
**Introduce the exercise, inform people that you have a worksheet that you think can help structure their thinking and help explore opportunities for how to redesign the work they do at Mozilla to enable greater participation.
**The worksheet template is a [https://docs.google.com/a/eaves.ca/document/d/1v4zkMYObGt6RE2l5ch2i3xKz0Tnh-V61OTLdH3pY9r8/edit Google Doc template]
**Encourage participants to make a personal copy of the template so they can fill out their own
**Participants will have about 7 minutes to fill out the form
**Many ideas are better than a few good ideas


- also a great vehicle for a breakout group & conversation.
'''Step 2'''
*Participants fill out the template
*Generally give the 7 minutes


Generally, filling out the template generates many ideas and serves as a great vehicle for a breakout group & conversation


'''Step 3'''
*time: about 7 minutes
*Debrief exercise
*Goal of the debrief is:
**validate people's ideas
**share & cross-pollinate
**gently challenge and push back when ideas don't conform with Mozilla values
*Instructions:
**Have participants share some of their favourite brainstormed ideas
**Facilitator should capture ideas in this conversation & share this as a list


Core team:
'''Step 4'''
 
*time: about 1-2 minutes
- core FF for Android team has no volunteer contributors
*Close out this exercise
 
*Summarize best ideas you heard
- incentives could be "part of the team," coder "rep", etc.
*Share some of your own ideas
 
*Best practices from across Mozilla include:
- triaging issues - what level / skill set is required. - helping to identify skills needed
**incentives could be "part of the team," coder "rep", etc.
 
**triaging issues - learning what level / skill set is required is a great way to learn how Mozilla works as well as learning to identify skills needed
- encouraging lurkers - watching people, watching bugs
**encouraging lurkers - watching people, watching bugs is a great way to learn
 
 
 
Goal of debrief is:
 
- validate people's ideas
 
- share & cross-pollinate
 
- gently challenge and push back when ideas don't conform with Mozilla values
 
 
 
Facilitator should capture ideas in this conversation & share this as a list
 
 
 
Wrapping up:
 
- If there's a follow-up class, share details
 
- Ask each participant to name one thing they're taking away from the workshop that was useful, and one thing they want to learn more about.


- Invite feedback via email
==Wrap up==
*time: about 2-5 minutes
*Purpose: to create a sense of shared value (or determine if the workshop did not create value for participants
*Process:
**Ask participants to share best thing they learned or heard
**Ask participants to share one action they intend to take as a result of the workshop
**Ask each participant to name one thing they're taking away from the workshop that was useful, and one thing they want to learn more about.
*Logistical questions to consider
**If there's a follow-up class, share details
**Invite feedback via email
Confirmed users
392

edits