Contribute/Recognition: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(59 intermediate revisions by 8 users not shown)
Line 1: Line 1:
Recognition Guide
__NOTOC__


==Badges==
{{Contribute_nav_bar}}


<section begin=summary />{{RoadmapSummary
|icon=Logo_0002_68.png‎ |64 px
|pagelocation=Contribute/Recognition/draft
|pagetitle=Recognition at Mozilla
|owner=Community Building Team
|updated=May 8, 2014
|description=We should all be recognized. We should all be recognizing.
}}<section end=summary />


===In Production===


* [https://carlacasilli.wordpress.com/2013/05/06/state-of-the-union-mozilla-badges/ State of the Union: Mozilla Badges] (Good summary of active badge projects at Mozilla as of May 7, 2013)
{{admon/note|Looking for the tools?|If you want to see the actual tools you can give to your community for recognition at Mozilla, the [[Contribute/Recognition/Toolkit|Recognition Toolkit]] is what you're looking for.}}


===In Process===
=<div align="center">  Recognition at Mozilla: A Working Guide </div>=


* Engagement badges
<div align="center"> The skill of acknowledgement is a statement of a person’s best qualities. It is more than just a compliment. You are observing and stating qualities that the person has that allow them to accomplish something. It is more about who the person is then what they have done. An acknowledgment might sound something like: ‘You are truly committed to a high level of excellence.’ Or ‘You are passionate about what you do.’ Or ‘Your persistence and focus have ensured that this project get done – despite all the obstacles that might have discouraged you.<br>
* IT badge designs: http://cl.ly/image/1e3t0h1F093t and http://cl.ly/image/403E170C3t0J
Taken from TRIBE:Awareness of Self https://wiki.mozilla.org/People:TRIBE </div>
* Creative Collective badge designs (from old Creative Collective site): http://www.flickr.com/photos/musingt/3811604179/in/set-72157617765620270
* More: https://openbadges.etherpad.mozilla.org/Internal-Moz-badge-issuers


===Notes===


Official badges from a Mozilla team vs. fun badges from individual Mozillians
__TOC__


How to measure if your badges are effective.
=Recognition at Mozilla is Mission-Based=


===Other===
Recognition is different from rewards. While recognition is the act of acknowledging that something has happened, or that an action has already been taken, rewards are thing used to motivate people to take an action.


* Notes on other people interested in issues badges:
''People do not contribute to Mozilla for rewards. ''' People contribute to Mozilla because they believe in our Mission.'''''
* Friend of the Tree, invitation to events, [http://www.mozilla.org/credits Credits], spotlight blog post, LEAD, module owner/peer, [https://bugzilla.mozilla.org/show_bug.cgi?id=484416 timeline of contributions]...


===Measuring Effectiveness===
=People Contribute for Three Reasons=


There are a few things to consider when measuring the effectiveness of your badge program:
According to social science, people contribute for:
[[File:Mozilla communities.png|thumbnail|right|Mozilla Community Logo]]


* What are your goals?  Are you interested in growing contributors or retaining contributors (ie, stopping churn)?
*autonomy (the need to direct our own lives)
** This is likely to be tied to the maturity of your community.  New communities just getting started will likely be interested in growth (ie, there is not much of an existing community yet to need to worry about retention) and more established communities will likely be interested in retention (ie, their processes have evolved where they have pathways to get new people involved and they want to keep people engaged)
*mastery (to learn and create new things)
** The answer to this determines how you analyze the data (ie, a new community can have a simpler approach to analytics that doesn't try to manage both the entrance of new contributors and the exit of existing contributors becoming inactive)
*purpose (to do better by ourselves and our world in some way)  


* What's a meaningful time frame for growth?  Can a new contributor progress through the set of contributor activities for your project in days, weeks, months.  For instance, a new Firefox coding contributor would take multiple releases to go through the process of getting their development environment set up, finding a good bug, creating a patch, going through review process, etc.
We recognize what people contribute to the project as a way to acknowledge that they have taken actions that have impact on our community, on us, and on our project. We recognize them in appropriate ways that grant autonomy, show that they have achieved mastery and that we share a common purpose.
Recognition creates cultural identity around a project. It allows us to tangibly illustrate to people that they are part of the project, and identify that they make an impact as part of the group.


* Since badges are opt-in, can you combine the data about who chose to accept a badge and who was eligible for one but didn't accept it?  Could these two groups act as separate cohorts for a twin study?
Our concept of motivation at Mozilla is drawn from Dan Pink's book ''Drive: The Surprising Truth About What Motivates Us,'' [http://www.ted.com/talks/dan_pink_on_motivation/ which he has conveniently summed up in this 18 minute Ted Talk.]




==Gear==
==We Should All Be Recognizing==
<big>
We should all be recognizing. We should all be recognized.</big>''


https://wiki.mozilla.org/GearStore
The responsibility of ''seeing'' other people for their accomplishments, the impact they have made, and the work that they do belongs to all of us.


Case study: [[Marketplace/Reviewers/Points_and_Incentives|AMO points and incentives program]]
It's easy to leave it to people in "power", but that underestimates our own ability to make a difference in the lives of the community that runs and supports this project.


==Learning Resources==
=Recognition Toolkit=


Rosetta Stone, Safari, LEAD/TRIBE, etc.
Recognition at Mozilla can take on many different forms. Please go to the [[Contribute/Recognition/Toolkit|recognition toolkit]] in order to see the different ways that Mozillians around the world are recognizing.


==More==
=Recognition in Different Cultures=


Recognition brainstorming exercise from Community Builders meetup at MozCamp Asia in 2012: https://etherpad.mozilla.org/contributor-recognition-brainstorm
We are a global organization and must realize that different cultures recognize people in different ways.
 
We are still building resources around this topic, but below are some takeaways from sessions we've had.
 
==Certain Forms of Recognition Don't Work for Everyone==
 
 
<big>''We need to be culturally sensitive and know our communities''</big>
[[File:Community-thebolt-future.png|thumbnail|left|Be the future of Community]]
*Public exposure can be awkward for certain contributors. Some people are private
*Try to communicate in a way that's appropriate to the culture you've working in. Don't be overly excited if the situation doesn't call for it.
*Think about the kinds of swag that you send to people. Realize that a tshirt in some places is considered identity, while other contributors are tired of getting the same stuff. Send swag appropriately, and don't overdo it or underdo it. (see Contribution Toolbox for more on swag)
*Be transparent and communicate out the way people can take on new roles and new privileges in the community. Be consistent in your "asks."
*Offering Mentoring can be a good way to include and recognize community members - showing people that you consider them someone you want to spend time with
 
See references and resources guide at the bottom for etherpads and notes about the ways we recognize in different cultural contexts.
 
=Resources, Guides, Archived Materials=
* [https://cbt.etherpad.mozilla.org/WaystoRecognize Ways to Recognize]
* [https://cbt.etherpad.mozilla.org/RecognitionMozillians Recognizing Mozillians]
* [https://cbt.etherpad.mozilla.org/recognition-20meeting-20notes Meeting notes from Recognition Working Group]
* [https://cbt.etherpad.mozilla.org/recognition-goals Recognition Plan Q1 2014]
* [https://cbt.etherpad.mozilla.org/2013-meetup-track-recognition 2013 Community Building Recognition Track]
* [https://etherpad.mozilla.org/recognition-guide-sc Recognition Guide from Santa Clara]
* [https://etherpad.mozilla.org/contributor-recognition-brainstorm MozCamp Asia Recognition Session]
* [http://www.iloveopensource.io/ I love open source for developer recognition]
* [http://opensource.com/life/12/3/blue-drop-awards-community-recognition-open-source-way Drupal's Blue Drop Awards]
* [http://economics.mit.edu/files/3023 MIT Paper on the Dynamics of Open Source Communities]
* [http://jonobacon.org Jono Bacon writes a lot about open source and recognition]
 
 
[[Category: Contribute]]
[[Category:Recognition]]

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 at Mozilla
Owner: Community Building Team Updated: 2014-09-22
We should all be recognized. We should all be recognizing.


Note.png
Looking for the tools?
If you want to see the actual tools you can give to your community for recognition at Mozilla, the Recognition Toolkit is what you're looking for.

Recognition at Mozilla: A Working Guide

The skill of acknowledgement is a statement of a person’s best qualities. It is more than just a compliment. You are observing and stating qualities that the person has that allow them to accomplish something. It is more about who the person is then what they have done. An acknowledgment might sound something like: ‘You are truly committed to a high level of excellence.’ Or ‘You are passionate about what you do.’ Or ‘Your persistence and focus have ensured that this project get done – despite all the obstacles that might have discouraged you.
Taken from TRIBE:Awareness of Self https://wiki.mozilla.org/People:TRIBE


Recognition at Mozilla is Mission-Based

Recognition is different from rewards. While recognition is the act of acknowledging that something has happened, or that an action has already been taken, rewards are thing used to motivate people to take an action.

People do not contribute to Mozilla for rewards. People contribute to Mozilla because they believe in our Mission.

People Contribute for Three Reasons

According to social science, people contribute for:

Mozilla Community Logo
  • autonomy (the need to direct our own lives)
  • mastery (to learn and create new things)
  • purpose (to do better by ourselves and our world in some way)

We recognize what people contribute to the project as a way to acknowledge that they have taken actions that have impact on our community, on us, and on our project. We recognize them in appropriate ways that grant autonomy, show that they have achieved mastery and that we share a common purpose. Recognition creates cultural identity around a project. It allows us to tangibly illustrate to people that they are part of the project, and identify that they make an impact as part of the group.

Our concept of motivation at Mozilla is drawn from Dan Pink's book Drive: The Surprising Truth About What Motivates Us, which he has conveniently summed up in this 18 minute Ted Talk.


We Should All Be Recognizing

We should all be recognizing. We should all be recognized.

The responsibility of seeing other people for their accomplishments, the impact they have made, and the work that they do belongs to all of us.

It's easy to leave it to people in "power", but that underestimates our own ability to make a difference in the lives of the community that runs and supports this project.

Recognition Toolkit

Recognition at Mozilla can take on many different forms. Please go to the recognition toolkit in order to see the different ways that Mozillians around the world are recognizing.

Recognition in Different Cultures

We are a global organization and must realize that different cultures recognize people in different ways.

We are still building resources around this topic, but below are some takeaways from sessions we've had.

Certain Forms of Recognition Don't Work for Everyone

We need to be culturally sensitive and know our communities

Be the future of Community
  • Public exposure can be awkward for certain contributors. Some people are private
  • Try to communicate in a way that's appropriate to the culture you've working in. Don't be overly excited if the situation doesn't call for it.
  • Think about the kinds of swag that you send to people. Realize that a tshirt in some places is considered identity, while other contributors are tired of getting the same stuff. Send swag appropriately, and don't overdo it or underdo it. (see Contribution Toolbox for more on swag)
  • Be transparent and communicate out the way people can take on new roles and new privileges in the community. Be consistent in your "asks."
  • Offering Mentoring can be a good way to include and recognize community members - showing people that you consider them someone you want to spend time with

See references and resources guide at the bottom for etherpads and notes about the ways we recognize in different cultural contexts.

Resources, Guides, Archived Materials

Retrieved from "https://wiki.mozilla.org/index.php?title=Contribute/Recognition&oldid=1017166"