Contribute/Recognition Roadmap: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 28: Line 28:


Goal:  
Goal:  
Make all types of recognition: meaningful and seamless across the organization, in order to create a vibrant, fun, global culture.
Make all types of recognition: meaningful and seamless across the organization, in order to create a vibrant, fun, global culture.



Revision as of 19:15, 10 February 2014

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


Logo 0002 68.png Recognition Roadmap 2014
Owner: Recognition Working Group Updated: 2014-02-10
Vision: TBD


Roadmap!

Goal Statement

Recognition advances our mission. We recognize because it is a tangible expression of our values. It creates inclusive cultural identity, offers legitimacy, shows appreciation and fosters growth. It creates engagement and purpose and is simply put, the right thing to do.

Goal: Make all types of recognition: meaningful and seamless across the organization, in order to create a vibrant, fun, global culture.

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

See a more [[ | detailed list of what our contributors do]].

2014 Priorities

What are we SHIPPING to support these goals and bring in more people? What are contributors helping us build?

Priority 1

Core, foundational work that blocks other priorities

  • What makes a strong pathway?
  • What kinds of contributions can people make? How can we open the funnel?
  • Working definition of a pathway that we can move forward with
  • Review all the existing pathways (functional and regional) and see what needs to be done. Create a collaborative mechanism that can categorize and organize where people are coming from
  • Go through current requests for pathways (other section of Contribute)
  • Understand how regional pathways can foster and nurture volunteers
  • Initial refresh of "Get Involved" page

Priority 2

What we will tackle first.

  • Define criteria for Contributor Management System
  • Build CMS that satisfies all stakeholders
  • Make a plan for what we are going to offer for people who are building pathways
  • Continue refreshing "Get Involved" page to be more inclusive and organic for new contributors

Priority 3

  • Communicate resource kit out so that people know what they can do

Timeline

(in progress)

Q1: Jan to March: Design and build
  • Develop a set of best practices for finding pathways
  • Basic refresh of Get Involved Page (http://www.mozilla.org/en-US/contribute/)
  • Audit and understand already existing mentorship possibilities
    • Community growth focus: Design new tools, imagine the present and future

Q2: April to June: Prepare and refine

    • Community growth focus: Develop and build new tools for contribution

Q3: July to Sep: Campaign and grow

    • Community growth focus: Launch and campaign for new tools
Q4: Oct to Dec: Harvest and celebrate
    • Community growth focus: Measure and reflect