Confirmed users
288
edits
Participation/Resources/Designing for participation/Documentation: Difference between revisions
Jump to navigation
Jump to search
Participation/Resources/Designing for participation/Documentation (view source)
Revision as of 05:41, 28 November 2013
, 28 November 2013no edit summary
No edit summary |
No edit summary |
||
| Line 115: | Line 115: | ||
==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 | ||
- | |||
'''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 | |||
'''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 | |||
'''Step 4''' | |||
*time: about 1-2 minutes | |||
*Close out this exercise | |||
*Summarize best ideas you heard | |||
*Share some of your own ideas | |||
*Best practices from across Mozilla include: | |||
**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 is a great way to learn | |||
- | ==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 | |||
- Invite feedback via email | |||