Contribute/Recognition Roadmap: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(added categories)
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:Recognition]]
[[Category:Roadmaps]]
{{Contribute_nav_bar}}
{{Contribute_nav_bar}}


<section begin=summary />{{RoadmapSummary
<section begin=summary />
{{RoadmapSummary
|icon=Logo_0002_68.png‎ |64 px
|icon=Logo_0002_68.png‎ |64 px
|pagelocation=pathways_roadmap
|pagelocation=Recognition_Roadmap
|pagetitle=Recognition Roadmap 2014
|pagetitle=Recognition Roadmap 2014
|owner=Recognition Working Group  
|owner=Recognition Working Group  
|updated=February 10, 2014
|updated=August 21, 2014
|description=Vision: Make all types of recognition: meaningful and seamless across the organization, in order to create a vibrant, fun, global culture.
|description=Vision: Make all types of recognition: meaningful and seamless across the organization, in order to create a vibrant, fun, global culture.
}}<section end=summary />
}}<section end=summary />
Line 17: Line 21:
<div style="width:100%;display:block;">
<div style="width:100%;display:block;">


= Goal =


<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<b>[[Contribute_choose_your_own_adventure|More on 2014 goals and how to get involved.]]</b>
</div>
</div>
==Vision and Goals==
==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.  
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.  
Line 41: Line 39:
==What are we working toward in 2014?==  
==What are we working toward in 2014?==  


* '''Unified Open Badges:'''  
* '''Reporting through Tableau:'''  
* '''Dynamic Recognition Toolkit:'''
* '''Recognition Preferences Displayed on Mozillians.org:'''
* '''Create Culture of Recognition:'''  
* '''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 '''[[ ]].'''
See a more '''[[ ]].'''
Line 51: Line 51:
What are we SHIPPING to support community members and community leaders in deepening recognition in a consistent and meaningful way?
What are we SHIPPING to support community members and community leaders in deepening recognition in a consistent and meaningful way?


== Priority 1 ==
== Priority 1: Visualize contribution pathways and recognition data ==
Unified Open Badge System
* Description: Create reports that measure conversion points along pathways
<ul>
* Goal served: Alignment around contribution stages; diagnostic tool to inform best practices
<li></li>
* Time frame
 
** Q3: Scope the project (what would a visualization show?)
</ul>
** Q4: Launch a data visualization
 
** 2015: Move from vouching to recognition model ("testimonial")?
== Priority 2 ==
* Stakeholders/Dependencies:
Dynamic Recognition Toolkit
** Business Intelligence resources
<ul>
** Pierros and the Systems & Data working group
 
** Community Building Team
<li></li>
** Contribution Area experts
<li></li>
<li></li>
<li></li>
<li></li>
 
</ul>
 
== Priority 3 ==
Create Culture of Recognition
<ul>
<li></li>
<li></li>
<li></li>
 
<li></li>
 
<li>
<li>
 
 
</ul>
 
=Timeline=
(in progress)


'''Q1:''' <i>Jan to March</i>: <b>Design and build</b><br
== Priority 2: Vouching for impact ==
/><ul><li>Develop a set of best practices for recognition that exist today</li></ul>
* 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


'''Q2:''' <i>April to June</i>: <b>Prepare and refine</b><br/>
== Priority 3: Get recognition preferences ==
<ul><li></li><ul><li>Community growth focus: Develop and build new tools for recognition<b></b></li></ul></ul>
* 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)


'''Q3:'''<i>July to Sep</i>: <b>Campaign and grow</b><br/>
== Priority 4: Support Adoption of  badges on mozillians.org ==
<ul><li></li><ul><li>Community growth focus: Launch and campaign for new tools<b></b></li></ul></ul>
* 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


'''Q4:'''<i>Oct to Dec</i>: <b>Harvest and celebrate</b><br
== Priority 5: Frictionless story surfacing ==
/><ul><li></li><ul><li>Community growth focus: Measure and reflect<b></b></li></ul></ul>
* 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


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

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


Roadmap!


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

Full Query
ID Severity Summary Whiteboard Priority Status
1057445 normal Vouching as "Testimonials" on Mozillians.org -- RESOLVED
1058905 normal Q3: Consult and help with UX for the way that badges will be displayed on Mozillians.org -- RESOLVED

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

2014-Q4

Full Query
ID Severity Summary Whiteboard Priority Status
1058307 normal Get recognition preferences added to Mozillians.org -- RESOLVED
1058912 normal Support adoption efforts with a goal that 10% of vouched Mozillians have badges on their profiles -- RESOLVED

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

Retrieved from "https://wiki.allizom.org/index.php?title=Contribute/Recognition_Roadmap&oldid=1017164"