Contribute/Recognition: Difference between revisions

Jump to navigation Jump to search

Contribute/Recognition (view source)

Revision as of 20:50, 13 May 2014

8,470 bytes removed ,  13 May 2014
no edit summary
No edit summary
Line 1: Line 1:
{{contribute_nav_bar}}
__NOTOC__


Recognizing volunteers for their contributions will deepen and extend relationships and will help us develop casual contributors into core contributors.
{{Contribute_nav_bar}}


Recognition can be an item like a badge or can be a recognition of potential by helping volunteers develop through mentoring and training.
<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 />


=Tell me more about Recognition=
===What and Why we Recognize===


Recognition and rewards are not the same thing.  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.
{{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.}}


People do not contribute to Mozilla for rewards. People contribute to Mozilla because they believe in our Mission and their work for the project offers them:
=<div align="center"> Recognition at Mozilla: A Working Guide </div>=
* 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 things that people contribute to the project as a way to acknowledge that they have taken actions that have impact on our project.  We recognize them in ways that acknowledge that they have achieved autonomy, mastery and purpose.  
<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>
Taken from TRIBE:Awareness of Self https://wiki.mozilla.org/People:TRIBE </div>


Recognition creates cultural identity.  It allows people to have a tangible illustration  that they are seen as being part of the project, and identify that they make an impact as part of the group. 


If you want an overview of motivation, watch this Tedtalk, it's great.
__TOC__


http://www.ted.com/talks/dan_pink_on_motivation
=Recognition at Mozilla is Mission-Based=


===Who should be recognized===
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.


====Everyone should be recognized.====
''People do not contribute to Mozilla for rewards. ''' People contribute to Mozilla because they believe in our Mission.'''''
It's that simple. When anyone does something that makes an impact, it's important that we give them a sense that their impact was seen.  That is what recognition is.


What makes recognition meaningful is different for everyone.  It's vitally important to have different types of recognition in your toolkit when working with communities. You should use the concepts of autonomy, mastery and purpose to determine the types and reasons for recognition. 
=People Contribute for Three Reasons=


===Who should be doing the recognition===
According to social science, people contribute for:
[[File:Mozilla communities.png|thumbnail|right|Mozilla Community Logo]]


==== Everyone. ====
*autonomy (the need to direct our own lives)
The responsibility of <i>seeing</i> other people, for who they are, the impact they have made, and the work that they do, belongs to all of us. 
*mastery (to learn and create new things)
*purpose (to do better by ourselves and our world in some way)


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 people we interact with on a daily basis.
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 acknowledge that they have achieved autonomy, mastery and 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.


====Something to think about====
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.]
Taken from TRIBE:Awareness of Self https://wiki.mozilla.org/People:TRIBE


"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.’


Acknowledgement is an important skill. People are usually motivated by getting positive feedback about their strengths. This kind of recognition is often more meaningful and effective in creating loyalty than other more traditional rewards, including money."
==We Should All Be Recognizing==
<big>
We should all be recognizing. We should all be recognized.</big>''


===How does recognition differ around the world===
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. 
Notes from the recognition sessions held at 2013 Summit


Santa Clara Session: https://etherpad.mozilla.org/recognition-guide-sc
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.


Combined Notes from Brussels and Toronto:
=Recognition Toolkit=


Recognition brainstorming exercise from Community Builders meetup at MozCamp Asia in 2012: https://etherpad.mozilla.org/contributor-recognition-brainstorm
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.


=Ways to recognize=
=Recognition in Different Cultures=


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


You can introduce a new volunteer who has started helping you out.  At the Monday project meetings there is a space to introduce new volunteers and you can add information there.
We are still building resources around this topic, but below are some takeaways from sessions we've had.


* For example, here's the [https://wiki.mozilla.org/WeeklyUpdates/2013-10-28#Introducing_New_Volunteers introduction to the set of new volunteer developers for Firefox 25]
==Certain Forms of Recognition Don't Work for Everyone==


===Best Practices===


<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."
*Mentoring can be a good way to include community members


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


A simple note of thanks is a great way to recognize someone.
=Resources, Guides, Archived Materials=
 
* [https://cbt.etherpad.mozilla.org/WaystoRecognize Ways to Recognize]
* email
* [https://cbt.etherpad.mozilla.org/RecognitionMozillians Recognizing Mozillians]
* blog post: https://blog.mozilla.org/community/category/spotlight/
* [https://cbt.etherpad.mozilla.org/recognition-20meeting-20notes Meeting notes from Recognition Working Group]
* postcard
* [https://cbt.etherpad.mozilla.org/recognition-goals Recognition Plan Q1 2014]
* etc.
* [https://cbt.etherpad.mozilla.org/2013-meetup-track-recognition 2013 Community Building Recognition Track]
===Best Practices===
* [https://etherpad.mozilla.org/recognition-guide-sc Recognition Guide from Santa Clara]
==Badges==
* [https://etherpad.mozilla.org/contributor-recognition-brainstorm MozCamp Asia Recognition Session]
Carla Casilli has some great things to say about badges here:  http://carlacasilli.wordpress.com/2014/03/17/a-foundational-badge-system-design/
* [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]
Excerpt:
* [http://economics.mit.edu/files/3023 MIT Paper on the Dynamics of Open Source Communities]
"A badge system structure for many
* [http://jonobacon.org Jono Bacon writes a lot about open source and recognition]
After much thought and many contemplative examinations, I’ve developed an archetypal badge system structure that I’m happy to recommend to the open badges community. Here are the many reasons why I think you’ll want to implement it.
 
    It’s simple.
    It’s modular.
    It’s easy to implement.
    It encourages a range of creativity.
    It works for organizations of vastly different sizes.
    It accomplishes the difficult task of working from bottom up, top-down, and middle out.
    It not only allows for growth, it thrives on it.
 
Introducing the 3 Part Badge System
This badge structure is the one that I developed for the Mozilla badge system that we are in the process of building. I’m calling it the 3 Part Badge System (3PBS). It’s composed of three interlocking parts and those three parts create a flexible structure that ensures feedback loops and allows the system to grow and evolve. Or breathe. And by breathe, I mean it allows the system to flex and bow as badges are added to it.
 
While some community member organizations have expressed a desire for a strict, locked-down, top-down badge system to—in their words—guarantee rigor (and you already know my thoughts on this), this system supports that request but is also designed to include active participation and badge creation from the bottom up. I’d say it’s the best of both worlds but then I’d be leaving out the middle-out capacity of this system. So in reality, it’s the best of all possible worlds.
 
This approach is a vote for interculturalism—or the intermingling and appreciation of cultures—in badge systems. Its strength arises from the continuous periodic review of all of the badges, in particular the team / product badges as well as the individual / community badges."
 
 
===Making badges at badges.mozilla.org===
* [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnUOR-0CBMsTdDQ2TVlFX2xHTjhuaVYxUndDSmU5RUE#gid=1 Template for designing badges and criteria]
* I work at Mozilla. How do I make a badge?
** Start here: https://badges.mozilla.org/en-US/
 
These badges are great for badges that can be created by anyone within the community and do not have specific visual requirements. An individual or community can create any type of badges they like.
 
===Open Badges Initiative ===
 
http://www.openbadges.org/
 
* This is best for entire badge systems, vouching for verifiable skills/experience and learning. 
* Learn more by following their blog http://openbadges.tumblr.com/
 
<b>Coming soon! </b>
Badgekit-- currently in Private Beta
http://badgekit.openbadges.org/
 
===Examples===
 
* WebQA Badges: https://quality.mozilla.org/2013/12/web-qa-gets-badges/
* IT badge designs: http://cl.ly/image/1e3t0h1F093t and http://cl.ly/image/403E170C3t0J
* 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
 
===Measuring Effectiveness===
 
There are a few things to consider when measuring the effectiveness of your badge program:
 
* What are your goals?  Are you interested in growing contributors or retaining contributors (ie, stopping churn)?
** 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)
** 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)
 
* 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.
 
* 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?
 
==Gear==
 
Recommendation: The issuing of swag should be considered in a manner similar to the process used to develop a badge system. In short that means teams should work to define the process or steps required to "earn" different levels of swag. Regular team review of community contribution will help to ensure that swag (as well as badges) are fulfilling the desired function and supporting the desired recognition.
 
We recommend creating opportunities for your team to regularly consider who you would like to recognize by sending a shirt, mug, etc.  These regular reminders could be done by:
 
* Add an agenda item to regular team meetings asking for nominations for volunteers who have made important contributions recently.  Make sure to include link to the [[GearStore]] wiki page so people know where to go to get delivery scheduled.
 
* Update the badges.mozilla.org site to send notifications to point people when people earn a certain badge.  This wouldn't be used to automatically issue swag, but would be a useful reminder for team members to consider nominations for contributors who you'd like to recognize. (Note: this feature doesn't exist now on badges.mozilla.org).
 
* Create a regularly recurring contributor spotlight, such as the [https://reps.mozilla.org/featured/ Reps of the month program]
 
* Thought: This may require developing a sort of swag pyramid that indicates levels of expertise or commitment required to earn different levels of swag. Or not, because this may make the system too rigid.
 
Where to schedule delivery for swag: https://wiki.mozilla.org/GearStore
 
Case study: [[Marketplace/Reviewers/Points_and_Incentives|AMO points and incentives program]]
===Best Practices===
Giving Gear:  Top 10 Things to Know by Jennifer Balaco September 30, 2013
 
*Check the wiki (https://wiki.mozilla.org/GearStore). It’s a good place to start.
*Don’t start at the top of the gear pyramid - there’s no where to go if you give the best gear first.
*Use the bugzilla form: https://bugzilla.mozilla.org/form.gear.  All gear requests (except for Reps events) go through this form.
*Know why you’re recognizing someone - it most likely will be asked. Be specific.
*If you are recognizing someone, you need their email address. The Gear Team can contact the person to get shipping and size information.
*Requests are processed on Mondays.
*Once your request has been approved, it is sent to Staples. You will receive an email from Staples with the UPS tracking information once it has shipped.
*If you have questions about gear, you can email gearteam@mozilla.com or visit the #mozgear IRC room.
*Give feedback. We don’t have the resources to add every item, but we’re always considering new additions. Also, we know the process and we’re not sure where things are confusing. Let us know.
 
==School Credit==
 
Officially vouching for contributions can be a very powerful way to recognize student volunteers who would like to receive school credit for their efforts.
 
Standard verification letters from academic institutions often contain language that we can't accept though.  For example, language that references an internship can't be used to verify volunteer contributions.
 
Academic institutions want to find good learning experiences for their students and they may be willing to work with us to modify their acceptance letters.  Dia created the following template student contribution letter after working with a University to change the language in their standard form.
 
Feel free to use this template as a starting point for a discussion with an academic institution you'd like to partner with to recognize existing student contributors or to create a source of future contributors.
 
* [[File:Student Contributor Letter.pdf|Student contributor letter template]] (PDF file)
* [[File:Student Contributor Letter.odt|Student contributor letter template]] (ODT file)
 
There is also a template form for a completion letter that documents what activities have been accomplished by the student.
 
* [[File:Contributor Completion Letter.odt]] (ODT file)
===Best Practices===
 
==Invitation to Mozillians==
Inviting a contributor to [http://mozillians.org/ mozillians.org], our community directory, is a great way to recognize someone and also get them better connected with Mozilla. This directory is a resource to make it easy for Mozillians to learn who is involved, what they do and how to connect with them. It also allows contributors to receive email communications from Mozilla with important news and announcements.
 
===Best Practices===
 
==Learning Resources==
 
We can give contributors access to various learning resources: Rosetta Stone, Safari, LEAD/TRIBE, etc.
 
==Certificates==
 
For long-time core contributors, you can recognize them in a very heartfelt way by creating a unique certificate to honor their involvement.  Some examples include:
 
* [http://www.youtube.com/watch?v=hF5hrnPAPI8 Community Leadership Award given to Channy at MozCamp Asia in 2012]
 
* [https://air.mozilla.org/?tag=engineer Distinguished Engineer award and videos]
 
* [http://fridge.ubuntu.com/2013/06/14/certificates-for-ubuntu-members/ Ubuntu's membership certificate]
 
===Best Practices===




[[Category: Contribute]]
[[Category: Contribute]]
Jennierose
canmove, Confirmed users
868

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/976568"

Navigation menu