canmove, Confirmed users
7,088
edits
Contribute/Funnels/Process: Difference between revisions
→SUMO's regional community building efforts
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Different processes work for different communities, but here we will provide some guidance and best practices for managing your contributor funnels. Moving forward, we are looking into providing tools for you to use and ways to extract meaningful metrics from the inquiries coming in leading to more effective onboarding. | Different processes work for different communities, but here we will provide some guidance and best practices for managing your contributor funnels. Moving forward, we are looking into providing tools for you to use and ways to extract meaningful metrics from the inquiries coming in leading to more effective onboarding. | ||
==What does it mean to say yes?== | |||
A basic question to answer is: 'What does it mean to say yes to community building?' | |||
People are interested in bringing volunteers into their projects, but it's not always clear what will happen once they commit to doing this. Even for projects that have volunteers already, it's not clear what will happen if they start scaling their efforts up by getting connected to a contribution funnel that sends them many people a day who want to help out. | |||
So for example, if you want to commit to bring in volunteers to your team, that may mean you need 1 person from the team to focus on this and spend 3 hours week working on a plan, etc. | |||
==Setting expectations== | |||
I think it's important to set expectations so that people running a funnel don't get discouraged if not everyone who shows up and wants to volunteer goes on to become a contributor. There are two main areas to set expectations around: | |||
* The range of inquiries: Michelle from Recruiting says that from her experience managing a funnel of people applying for a job there is a rule of thirds: Expect that around 1/3 of inquiries are from promising candidiates, 1/3 may be qualified but there's not enough information and 1/3 won't be relevant (support questions, off-topics inquiries, etc). | |||
* The follow-through: Even though someone is expressing interest in contributing, they may not move forward (things change, they didn't realize the time commitment, etc). So we should expect some amount of drop-off in every step forward someone takes to become a contributor. We don't have great metrics now, so it can be hard to measure this -- on the flip side, because we don't have great contribution metrics someone may be moving forward that we don't see. For example, if you email someone how to get involved with your project and they don't respond, that may be because you gave them all the information they needed. | |||
It could be interesting to do some research and demonstrate how this works in other volunteer-based organizations. | |||
===Conversion metrics=== | |||
Speaking of setting expectations through metrics, it would be great to have tips for communities about how to track conversion of potential contributors into active and core contributors. For instance, Mozilla Hispano has manually pulled these numbers together recently: | |||
* 2770 inquiries (18 per day). | |||
* 320 answered the first email (11,5%). | |||
* 40 started their contributions to the community via mentor (12,5% of the answers and 1,5% of the total). | |||
* This means we got around 2 real contributors per week. Of course contributors come and go, so we should wait a few months more to see how many become core contributors | |||
We can also work with the Metrics team to create a live dashboard for a local community to use as a template for other communities. | |||
==Mozilla Hispano's Process== | ==Mozilla Hispano's Process== | ||
| Line 34: | Line 63: | ||
A very important part of this workflow is ensuring that all l10n teams identify these five steps to joining and contributing to their team. Without those, the newcomer flownders and ultimately does not turn into an active contributor. | A very important part of this workflow is ensuring that all l10n teams identify these five steps to joining and contributing to their team. Without those, the newcomer flownders and ultimately does not turn into an active contributor. | ||
==SUMO's regional community building efforts== | |||
SUMO has been doing some regional community building efforts to create Firefox OS support communities in countries where devices will be launching. Madalina referenced a successful Brazilian community building plan they had that built up a new community in about 6 months. Would be good to document and share. | |||
The Webprod team is also getting started on a community building effort and they're documenting things at https://wiki.mozilla.org/Webdev/Web_Production/Community | |||
==Tips from Mozilla Recruiting== | ==Tips from Mozilla Recruiting== | ||
Michelle Marovich from Mozilla Recruiting has pulled together some tips from her experience in the [[Contribute/Workshops/Onboarding|Onboarding New Volunteers Workshop]] | Michelle Marovich from Mozilla Recruiting has pulled together some tips from her experience in the [[Contribute/Workshops/Onboarding|Onboarding New Volunteers Workshop]] | ||
==Mozilla Marketing's Process== | ==Mozilla Marketing's Process== | ||
| Line 66: | Line 99: | ||
https://mozillatunisia.etherpad.mozilla.org/Community-Building-session | https://mozillatunisia.etherpad.mozilla.org/Community-Building-session | ||
==Badge Pathways== | |||
Carla from the Open Badges team is writing a series of posts about badge pathways. This could be useful for people thinking of tying badges to contributions, but the concepts around pathways also applies to contribution pathways that don't include badges. | |||
In particular, the discussions around the different types of pathways can be useful for teams and communities at different stages of development (new communities may need a different type of path than established communities). | |||
* [http://carlacasilli.wordpress.com/2013/03/25/badge-pathways-part-1-the-paraquel/ Badge pathways: part 1, the paraquel] | |||
* [http://carlacasilli.wordpress.com/2013/04/28/badge-pathways-part-2-the-quel/ Badge pathways: part 2, the “quel”] | |||
==Writing Good Emails== | ==Writing Good Emails== | ||
| Line 72: | Line 114: | ||
Some good things in here that apply to writing back to people who want to volunteer, for example slide 48 talks about having one clear ask in the email. | Some good things in here that apply to writing back to people who want to volunteer, for example slide 48 talks about having one clear ask in the email. | ||
==Contribution Paths in Mozilla presentation== | |||
[http://people.mozilla.com/~bking/presentations/docSL/paths.html Slides from Brian King's talk on contribution paths] | |||