Pathways roadmap: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(11 intermediate revisions by 2 users not shown)
Line 21: Line 21:


<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<b>[[Contribute|Community Building Contribute Main Page.]]</b>
<span style="center"><span style="font-size:150%">'''[[Contribute|Community Building Contribute Main Page.]]'''</span></span>
</div>
</div>
</div>
==Contribution is our #1 metric==
==Contribution is our #1 metric==


Line 35: Line 35:
*'''Commit where you can:''' We are all superstars. If you cannot commit the time to a task, please do not take it on. Bite off only what you can chew.
*'''Commit where you can:''' We are all superstars. If you cannot commit the time to a task, please do not take it on. Bite off only what you can chew.
*'''Step up, step back:''' Step up to new challenges where you think you can be of assistance. Step back if you are doing or contributing too much. Follow consensus and facilitation best practices
*'''Step up, step back:''' Step up to new challenges where you think you can be of assistance. Step back if you are doing or contributing too much. Follow consensus and facilitation best practices
==Group Process==
*There are four subgroups in the pathways working group
*Each subgroup has a driver
*Pathways will meet every other week
*Drivers will communicate throughout the two weeks and share out to the group at every meeting. Meetings will be used for collaborative sharing and input
*Each driver will set a series of goals from Q1-Q4 and accomplish them
*Drivers will delegate tasks to members of their subgroup
*Drivers could possibly change or rotate every quarter to involve main participants in every aspect of pathways


==What constitutes a contribution pathway?==  
==What constitutes a contribution pathway?==  
Line 51: Line 42:
** '''Following through on interest:''' developing mentorship and new opportunities that challenge and motivate contributors and participants
** '''Following through on interest:''' developing mentorship and new opportunities that challenge and motivate contributors and participants


=Pathways Subgroups and Goals Q1-Q4=
=Pathways Subgroups and Goals Q3-Q4=
High Level Goals:
# Build alignment in the organization around a community contribution stages model.
# Build pathways best practices, resources, templates and tools that are both useful and beautiful, so that we make pathway building scalable and any mozillian can build a pathway.
# Support brand new contributors and the projects they join by building a community of mentors and a system to support them.


==Systems/Tools==
= Next steps on this document =
 
*Definition: Measurement and development of existing and potential systems for pathways.
 
<span style="font-size:150%">'''Action Points:'''</span>
 
<center>'''Q1: Design and build'''</center>
 
*Audit of existing pathways and systems (https://cbt.etherpad.mozilla.org/what-makes-a-pathway )
*Develop framework for CRM tool (https://docs.google.com/document/d/1o403WvYzoNYZ0mM-ciOLo0XFYaWAIC-3YriMvQ_q9qY/edit)
*Define and utilize pathways communication channels
*Explore possibilities for Get Involved page with UX and WebDev
 
<center>'''Q2:  Continue tool development, prepare tools, and refine'''</center>
 
*Develop framework for conversion points
*Initial refresh of Get Involved page
*Research, development and implementation of second phase refresh of Get Involved
*Develop new contributor matching tool that matches new contributors to time-appropriate, relevant projects
*Maintain and regularly update pathways wiki
*Using best practice audit of stewards survey, create script or other mechanism that will sort and maintain new contributor emails (using CRM?)
 
<center>'''Q3: Campaign and grow'''</center>
 
*Implement and utilize CRM tool
*Reach out across organization to encourage use of CRM and other developed tools
*Research, development and implementation of third phase refresh of Get Involved, with CRM integration and more
 
<center>'''Q4: Harvest and celebrate'''</center>
 
*Audit, retool, and continue to build CRM tool
*Run metrics on contributor Get Involved page
*Audit new contributor matching tool
*Utilize best practices checklist for systems
 
'''Driver: Larissa'''
 
'''Passengers of note: Kadir'''
 
==Best Practices==
 
*Definition: Define best practices for finding and developing pathways that ties together the work of the other working groups. Serve as point people for other sub-groups across pathways.
 
<span style="font-size:88%">'''Action Points:'''</span>
 
<center>'''Q1: Design and build'''</center>
 
*Develop definition of minimum contribution
*Explore mentorship possibilities and develop best practices for mentorship models with mentorship groups
*Continue work on "What Makes a Pathway?" https://cbt.etherpad.mozilla.org/what-makes-a-pathway
*Define conversion points across the organization
*Review results of stewards survey
 
<center>'''Q2: Continue tool development, prepare tools, and refine'''</center>
 
*Refine and roll out mentorship program for new contributors with mentorship subgroup
*Encourage local communities to create one resource (video, blog post,  website, event) to support people looking for regional pathways.
*Develop and ship one new pathway
*Analyze new "Get Involved Page" survey with research team
*Develop and maintain cross-organizational Pathways Checklist or other tool that defines:
**Minimum contribution
**Conversion points
**Mentorship definition
 
<center>'''Q3: Campaign and grow'''</center>
 
*Brown bag talk on best practices for new contributors
*Community check in on goal shipment across the CBT
*Cross team analysis of new pathways
*Air Mozilla videos on pathways and best practices across the organization
**Solicit one resource from every team
*Implement findings from "Get Involved Page" survey to seamlessly integrate with defined metrics
 
<center>Q4: Harvest and celebrate</center>
 
*Implement new pathways developed from best practice finder
*Cross-team analysis of effectiveness of new pathway, conversion point, and best practice model
 
'''Driver: Madalina'''
 
'''Passengers of note: Kadir, Jennie, Larissa'''
 
== Priority 3 ==
 
<ul>
<li>Cross team analysis of best practice model</li>
<li>Run metrics on new Get Involved page</li>
<li>Implement new contributor management system</li>
<li>Implement new pathways developed from best practice finder</li>
<li>Incentivize higher levels of participation</li>
 
 
</ul>
 
=Timeline=
(in progress)
 
'''Q1:''' <i>Jan to March</i>: <b>Design and build</b><br
/><ul><li>Develop a set of best practices for finding pathways</li>
<li>Basic refresh of Get Involved Page (http://www.mozilla.org/en-US/contribute/)</li>
<li>Audit and understand already existing mentorship possibilities</li>
<ul><li>Community growth focus: Design new tools, imagine the present and future<b></b></li></ul></ul>
<b>Q2:</b> <i>April to June</i>: <b>Continue tool development, prepare tools, and refine</b><br/>
<li>Meet with stewards and drivers to implement best practices for pathway finding into their individual efforts</li>
<li>Launch new pathway finding tool</li>
<ul><li>Community growth focus: Develop and build new tools for contribution<b></b></li></ul></ul>
<b>Q3:</b> <i>July to Sep</i>: <b>Campaign and grow</b><br/>
<ul><li></li><ul><li>Community growth focus: Launch and campaign for new tools<b></b></li></ul></ul>
<b>Q4: </b><i>Oct to Dec</i>: <b>Harvest and celebrate</b><br/>
<ul><li>Share out new materials developed</li><ul>
<li>Write a report that outlines new contributor pathways found</li>
<ul><li></li><ul><li>Community growth focus: Measure and reflect<b></b></li></ul></ul>


</div>
=== 2014-Q3 ===
</div>
<bugzilla>
    {
        "product": "Community Building",
        "component": "Pathways",
        "target_milestone": "2014Q3",
        "include_fields": "id, severity, summary, whiteboard, priority, status"
    }
</bugzilla>
=== 2014-Q4 ===
<bugzilla>
    {
        "product": "Community Building",
        "component": "Pathways",
        "target_milestone": "2014Q4",
        "include_fields": "id, severity, summary, whiteboard, priority, status"
    }
</bugzilla>


<div style="-moz-border-radius: 10px;background-color:white;border:3px dashed;display:block;padding:20px;margin-top:20px;">
= Next steps on this document =
*Refine and develop Q2-Q4 goals
*Define quantifiable metrics for what makes a contribution pathway
</div>
</div>

Latest revision as of 02:40, 27 August 2014

Grow mozilla large.png Main | Resources | Working Groups | Get Involved Main Page | Team | Maturity Model | Build Principles


Logo 0002 68.png Pathways Roadmap 2014
Owner: Pathways Team Updated: 2014-08-27
Vision: The Pathways working group seeks to remove the barriers to contribution so that participation, however it is defined, is beautifully simple.


Roadmap!

Pathways Areas and Drivers: A 2014 Roadmap

Contribution is our #1 metric

Through defined and innovative pathways we can reach our goal of 1,000,000 Mozillians in ten years and 10x by the end of this year.

Shared Goals across the Pathways Working Group:

  • Support each others' work: Subgroups work together to build together
  • Share out resources and work in the open: Check in regularly and share out resources that may relate to another subgroup's work. Work in the open utilizing our shared communication tools. Follow the group decisions on how to share through defined communications pathways
  • Treat each other (contributor and staff) with respect: The goal of pathways is to make every form of contribution meaningful. Practice what we preach. Be respectful of each others' time and be aware of varying levels of commitment.
  • Commit where you can: We are all superstars. If you cannot commit the time to a task, please do not take it on. Bite off only what you can chew.
  • Step up, step back: Step up to new challenges where you think you can be of assistance. Step back if you are doing or contributing too much. Follow consensus and facilitation best practices

What constitutes a contribution pathway?

    • Targeting interest: through get involved, a regional group, or a specific product
    • Maintaining interest: through systems that funnel from participant to contributor
    • Following through on interest: developing mentorship and new opportunities that challenge and motivate contributors and participants

Pathways Subgroups and Goals Q3-Q4

High Level Goals:

  1. Build alignment in the organization around a community contribution stages model.
  2. Build pathways best practices, resources, templates and tools that are both useful and beautiful, so that we make pathway building scalable and any mozillian can build a pathway.
  3. Support brand new contributors and the projects they join by building a community of mentors and a system to support them.

Next steps on this document

2014-Q3

Full Query
ID Severity Summary Whiteboard Priority Status
1057122 normal Choose your own adventure manual for guides P1 NEW
1058880 normal Define Community Contribution Stages P1 NEW

2 Total; 2 Open (100%); 0 Resolved (0%); 0 Verified (0%);

2014-Q4

Full Query
ID Severity Summary Whiteboard Priority Status
1058890 normal Pathways into Community Building -- RESOLVED
1058892 normal Example Pathways and Template that is Beautiful -- RESOLVED

2 Total; 0 Open (0%); 2 Resolved (100%); 0 Verified (0%);


Retrieved from "https://wiki.mozilla.org/index.php?title=Pathways_roadmap&oldid=1009692"