Contribute/Recognition Roadmap

From MozillaWiki
Jump to: navigation, search


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-09-22
Vision: Make all types of recognition: meaningful and seamless across the organization, in order to create a vibrant, fun, global culture.


NOTOC

<

div style="display:block;-moz-border-radius:10px;background-color:#FF9966;padding:20px;margin-top:20px;">

Roadmap!

<

div style="display:block;background-color:#FFFFFF;-moz-column-gap:20px;padding:20px;margin-top:20px;-moz-border-radius:10px;margin-top:30px;">

<

div style="width:100%;display:block;">

Vision and Goals

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.

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

  • By the end of 2014, in partnership with the systems and data working group, we deploy a largely automated reporting system for recognizing contributors utilizing tableau.
  • By the end of 2014 we will support Mozillians.org as a place for recognition so that vouching, recognition preferences, and badges become part of our standard practice.
  • By the end of 2014 we will begin to establish a culture of recognition that is evident through retention increase in new and existing contributors.

How is this related to the Top Line 2014 goals? In support of the 2014 goals, it's important to remember that adoption and retention in our community is impacted by recognition everyday. We each have the ability to make positive change for community members by taking action around recognizing their efforts.

What are we working toward in 2014?

  • Reporting through Tableau:
  • Recognition Preferences Displayed on Mozillians.org:
  • Adoption of Badges on Mozillians.org:
  • Vouching as "Testimonials" on Mozillians.org:
  • We will know when we have been suceessful in influencing the culture when we see a positive impact to retention:

See a more [[ ]].

2014 Priorities

What are we SHIPPING to support community members and community leaders in deepening recognition in a consistent and meaningful way?

Priority 1: Visualize contribution pathways and recognition data

  • Description: Create reports that measure conversion points along pathways
  • Goal served: Alignment around contribution stages; diagnostic tool to inform best practices
  • Time frame
    • Q3: Scope the project (what would a visualization show?)
    • Q4: Launch a data visualization
    • 2015: Move from vouching to recognition model ("testimonial")?
  • Stakeholders/Dependencies:
    • Business Intelligence resources
    • Pierros and the Systems & Data working group
    • Community Building Team
    • Contribution Area experts

Priority 2: Vouching for impact

  • Description: Get vouching to become recognition by "vouching for impact" in 2014. Have vouch descriptions serve as recognition in addition to documenting a person's contributions.
  • Goal served: Support mozillians.org as a vehicle for recognition
  • Time frame
    • Q3:
      • Document how to and when to write a "testimonial vouch"
    • Q4:
      • Socialize and drive to 1/3 of new vouches are "testimonials"
      • Create an opt in privacy setting around vouching so that vouches can be shared publicly
  • Stakeholders/Dependencies:
    • Community Tools team and William R
    • Privacy team
    • SUMO, MDN, and Webmaker teams for evangelism

Priority 3: Get recognition preferences

  • Description:
    • List of all ways we recognize contributors
    • Get preferences added to Mozillians.org, with visibility/privacy settings)
    • Allow personal opt out of any type of recognition
    • Share with project with goal of 25% of vouched Mozillians expressing preferences
  • Goal served: Support mozillians.org as a vehicle for recognition
  • Time frame
    • Q3: Create list of preferences; create requirements and designs for mozillians.org
    • Q4: Launch recognition preferences and get 25% adoption
    • 2015: Add the ways that a contributors has already been recognized?
  • Stakeholders/Dependencies:
    • Community Tools team and William R
    • Gear Store (Andrea)

Priority 4: Support Adoption of badges on mozillians.org

  • Description: Support the adoption of Mozilla badges by Mozilla contributors
  • Goal served:
    • Support mozillians.org as a vehicle for recognition
    • Create a culture of recognition
  • Time frame
    • Q3: Consult on the design the way that badges will be displayed; create awareness and excitement about badges coming to mozillians.org profiles
    • Q4: Launch on mozillians.org; execute adoption efforts with a goal that 10% of vouched Mozillians have badges on their profiles
  • Stakeholders/Dependencies:
    • Badges team
    • Community Building team
    • Community Builders support for advocacy
    • UX designers

Priority 5: Frictionless story surfacing

  • Description: Making stories on Mozillians.org easier to discover via feeds, filtering and search
  • Goal served:
    • Support mozillians.org as a vehicle for recognition
    • Create a culture of recognition
  • Time frame
    • Q4: Design what surfacing looks like; define the scope; create requirements
    • Q1 (2015): Launch a view of surfaced stories
  • Stakeholders/Dependencies:
    • Community Tools team
    • Better vouches as recognition

Timeline & Bugs

2014-Q3

Bugzilla query error


Warning: implode(): Invalid arguments passed in /var/www/wiki/core/extensions/Bugzilla/templates/error.tpl on line 5

2014-Q4

Bugzilla query error


Warning: implode(): Invalid arguments passed in /var/www/wiki/core/extensions/Bugzilla/templates/error.tpl on line 5