canmove, Confirmed users
868
edits
Contribute/Lifecycle/draft: Difference between revisions
no edit summary
Jennierose (talk | contribs) No edit summary |
Jennierose (talk | contribs) No edit summary |
||
| Line 115: | Line 115: | ||
|-valign="top" | |-valign="top" | ||
|bgcolor="Asparagus"|[[Contribute/Lifecycle/draft#Sustaining| '''Sustaining''']] | |bgcolor="Asparagus"|[[Contribute/Lifecycle/draft#Sustaining| '''Sustaining''']] | ||
| *The community’s voice is heard and is influential organization-wide | | | ||
*The community’s voice is heard and is influential organization-wide | |||
*Community energy is maintained through renewal activities | *Community energy is maintained through renewal activities | ||
*The community positively impacts top-line team goals on an on-going basis | *The community positively impacts top-line team goals on an on-going basis | ||
|} | |||
==<center>Contribution Lifecycle Resources</center>== | |||
{| border="1" cellpadding="2" | |||
|-valign="top" | |||
|bgcolor="orange"|[[Contribute/Lifecycle/draft#Pre-Work|'''Pre-work''']] | |||
| | |||
*<i>Getting Ready for Participation Workshop</i> Modules | |||
**What’s possible? | |||
**Active vs Passive Transparency Exercise | |||
**Communication Channels, and how/when to use them | |||
**Action Plan for Next Steps | |||
*Video on the impact of working with contributors-- we need this to be made-- can a contributor make it, possibly working through Dia and her video producers? | |||
*Info on where they can go to ask questions/field concerns-- Consumable “contact us” documentation | |||
*Get involved page tutorial, how it works, how to get connected (this is a part of a larger structure: not all pathways are on the Get Involved page) | |||
**Way to reach out to specific locales and skill sets to get the things your community needs. | |||
|-valign="top" | |||
|bgcolor="Beau Blue"|[[Contribute/Lifecycle/draft#Starting | '''Starting''']] | |||
| | |||
*[[Contribute/whatmakesapathway| What Makes a Healthy Pathway]] This wiki page serves as a guide for developing a pathway and collection of best practices from existing Mozilla contribution pathways. A pathway is a living process to be iterated on in every phase of the lifecycle. | |||
*Communities of practice can start with different intents. For instance, an exploratory study by the American Productivity and Quality Center (APQC)6 found four different strategic intents for forming communities for professionals on different teams or locations: | |||
**to help each other solve everyday work problems in their discipline, | |||
**to develop and disseminate a set of best practices, | |||
**to develop and steward the tools, insights, and approaches needed by members in field assignments, and | |||
**to develop highly innovative solutions and ideas. | |||
*Although most communities serve more than one purpose, communities tend to focus on one and adapt the structure, roles, and activities most suited to that intent. Then they fit other activities into the structures. Pathways are a first step in defining contribution opportunities to the intent of the community. | |||
*[[Contribute/Workshops/Designing_for_participation| David Eaves Workshop: Designing for Participation]] | |||
*[[Contribute/Workshops/Identifying_contributors| David Eaves Workshop: Identifying Contributors]] | |||
*Taken from: [https://kindle.amazon.com/work/cultivating-communities-practice-managing-knowledge-ebook/B001JG2C64/B004OEIQ7W| Cultivating Communities of Practice: A Guide to Managing Knowledge.] Activators perform a number of key functions across the lifecycle: | |||
**Identify important issues in their domain. | |||
**Plan and facilitate community events. This is the most visible aspect of the coordinator role. Informally link community members, crossing boundaries between organizational units and brokering knowledge assets. | |||
**Foster the development of community members. | |||
**Manage the boundary between the community and the formal organization, such as teams and other organizational units. | |||
**Help build the practice—including the knowledge base, lessons learned, best practices, tools and methods, and learning events. | |||
**Assess the health of the community and evaluate its contribution to members and the organization | |||
|-valign="top" | |||
|bgcolor="red"|[[Contribute/Lifecycle/draft#Learning and Preparing for Growth| '''Learning and preparing for growth''']] | |||
|Awaiting your awesome input! | |||
|-valign="top" | |||
|bgcolor="Barn red"|[[Contribute/Lifecycle/draft#Scaling| '''Scaling''']] | |||
|Awaiting your awesome input! | |||
|-valign="top" | |||
|bgcolor="Asparagus"|[[Contribute/Lifecycle/draft#Sustaining| '''Sustaining''']] | |||
|Awaiting your awesome input! | |||
|} | |} | ||