Contribute/Workshops/Metrics for growth/SelfDirectedSyllabus: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 50: Line 50:
*[https://drupal.org/project/views Drupal Module Page]
*[https://drupal.org/project/views Drupal Module Page]


What would make these dashboards useful to a community manager? To a contributor?
'''Task'''


[https://dl.dropboxusercontent.com/u/987691/Mozilla%20Workshop/Metrics%20for%20growth%20part%202.mov video number 2].
What would make these dashboards useful to:
*a community manager?
*to a contributor?


==second activity==
'''Debrief'''


One of the key metrics any open source community should know is the conversion rate of participants. By this we mean, are potential contributors who signal an interest in joining the community? Do those who engage in a first task then go on to participate in a second task. How many mature into regular contributors? How many take on more complex tasks or come to enjoy great responsibility in the project?
[https://dl.dropboxusercontent.com/u/987691/Mozilla%20Workshop/Metrics%20for%20growth%20part%202.mov video number 2].


We refer to this sequence of conversions as funnel of engagement
'''Follow up Activity'''
Brainstorm three things that would make a dashboard useful to:
*a community manager or head of a module/project
*a contributor to a project


So what do we mean by a funnel of engagement?
==second activity==
- don’t need to be perfectly linear
- allows you to see when you gain people
- how far those people progress in tasks at Mozilla
- where barriers lay


Please watch [https://dl.dropboxusercontent.com/u/987691/Mozilla%20Workshop/Metrics%20for%20growth%20part%203.mov video number 3].


'''Funnels of Engagement'''
The engagement funnels for several Mozilla projects [[Contribute/Conversion_points | have already been mapped]]. You can use one these as a template to create your own and even add it to the wiki page as a reference.
The engagement funnels for several Mozilla projects [[Contribute/Conversion_points | have already been mapped]]. You can use one these as a template to create your own and even add it to the wiki page as a reference.


==Personal Application==
'''Task'''
 
Map out what the funnel of engagement might be for your part of the Mozilla project.
As outlined in the previous video 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.
 
The worksheet template is available as a [https://docs.google.com/a/eaves.ca/document/d/1v4zkMYObGt6RE2l5ch2i3xKz0Tnh-V61OTLdH3pY9r8/edit Google Doc template]
Please make a personal copy of the template to fill out (please leave the template blank for others)


==Debrief Personal Application==
==Debrief==
Please watch  [https://dl.dropboxusercontent.com/u/987691/Mozilla%20Workshop/Designing%20for%20Participation%20Part%204.mov video number 4].
Please watch  [https://dl.dropboxusercontent.com/u/987691/Mozilla%20Workshop/Metrics%20for%20growth%20part%204.mov video number 4].


Please feel free to send questions or ideas to david <a> eaves.ca.
Please feel free to send questions or ideas to david <a> eaves.ca.


You may also find the follow up workshop [https://wiki.mozilla.org/Contribute/Workshops/Identifying_contributors Identifying Contributors] to be interesting.
You may also find the follow up workshop [https://wiki.mozilla.org/Contribute/Workshops/Identifying_contributors Identifying Contributors] to be interesting.

Revision as of 07:58, 24 February 2014

Anyone at Mozilla - module owner, newcomer, veteran, staff, volunteer should feel welcome to initiate or run the Designing for Participation Workshop.

Purpose & Goals

what's the goal of this workshop?

The Identifying Contributors workshop is a sequel to the Designing For Participation and the Identifying Contributors workshops. The Metrics for Growth workshop was created to help Mozilla community members think about how measure - and this improve - the size, nature, contribution rate and overall happiness of their pool of contributors. As such the workshop has these goals:

  • foster a conversation where best practices and ideas can be surfaced and critically assessed, particularly around how suggestion may or may not be relevant to areas the participants work on
  • provide participants with action items they can take back to where they contribute to Mozilla that will help improve how they measure community participation
  • share differing experiences, perceptions, challenges and opportunities around effective metrics as understood by managers, employees, staff, volunteers, newcomers and veteran contributors.

who should participate?

Almost anyone at Mozilla should feel like this is open to them. "Roles" that might want to participate or lead this workshop include:

  • module owners
  • newcomers
  • veterans
  • staff
  • volunteers
  • managers

Some of the more common questions participants often have that make them a good fit for the course include:

  • We are starting a new product/activity/function and want to think about how we can encourage community participation
  • I'd like to understand if our community is growing/shrinking
  • I'd like to try to experiment more around community participation and want to know what the impact will be
  • I need to expand the scope of our work without increasing the financial resources I have
  • I’m a manager and I'd like some tools for thinking about how to evaluate how effectively those who work for me create space and opportunity for community participation.
  • I've just been asked to expand our community participation, what do I do?
  • I'm a long time contributor with lots of thoughts how we could manage community more effecitvely
  • I need to expand the scope of our work without increasing our groups financial resources

slide Deck

The slides for this presentation can be downloaded here in

Syllabus

identify goals

Please start by watching video number 1.

As per the video, please write down 1-4 goals that you have for this workshop

activity

Please look at the following four dashboards used to assess and/or encourage participation in open source projects

Task

What would make these dashboards useful to:

  • a community manager?
  • to a contributor?

Debrief

video number 2.

Follow up Activity Brainstorm three things that would make a dashboard useful to:

  • a community manager or head of a module/project
  • a contributor to a project

second activity

Please watch video number 3.

Funnels of Engagement The engagement funnels for several Mozilla projects have already been mapped. You can use one these as a template to create your own and even add it to the wiki page as a reference.

Task Map out what the funnel of engagement might be for your part of the Mozilla project.

Debrief

Please watch video number 4.

Please feel free to send questions or ideas to david <a> eaves.ca.

You may also find the follow up workshop Identifying Contributors to be interesting.