Changes

<section begin=summary />{{RoadmapSummary|icon=Logo_0002_68.png‎ |64 px|pagelocation=Contribute/Recognition can /draft|pagetitle=Recognition at Mozilla|owner=Community Building Team|updated=May 8, 2014|description=We should all be an item like a badge or can recognized. We should all be a recognition of potential by helping volunteers develop through mentoring and trainingrecognizing.}}<section end=summary />

{{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 and rewards are not the same thing. /Toolkit|Recognition Toolkit]] 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 actionwhat you're looking for. }}

People do not contribute to Mozilla for rewards. =<div align="center"> People contribute to Recognition at Mozilla because they believe in our Mission and their work for the project offers them:* 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)A Working Guide </div>=

We recognize things <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 people contribute allow them to accomplish something. It is more about who the project as person is then what they have done. An acknowledgment might sound something like: ‘You are truly committed to a way to acknowledge that they high level of excellence.’ Or ‘You are passionate about what you do.’ Or ‘Your persistence and focus have taken actions ensured that have impact on our this project. We recognize them in ways that acknowledge get done – despite all the obstacles that they might have achieved autonomy, mastery and purposediscouraged you.<br>Taken from TRIBE:Awareness of Self https://wiki.mozilla. org/People:TRIBE </div>

====Everyone should be recognized''People do not contribute to Mozilla for rewards.====It's that simple'' People contribute to Mozilla because they believe in our Mission. 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 =People Contribute 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. Three Reasons=

==== 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, *mastery (to learn and the work that they create new things)*purpose (to do, belongs to all of us. 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 acknowledge that they have achieved autonomy, mastery and purpose.Recognition creates cultural identity around a project. It's easy allows us to leave it tangibly illustrate to people in "power"that they are part of the project, but and identify that underestimates our own ability to they make a difference in the lives an impact as part of the people we interact with on a daily basisgroup.

====Something to think about====Taken Our concept of motivation at Mozilla is drawn from TRIBEDan Pink's book ''Drive:Awareness of Self httpsThe Surprising Truth About What Motivates Us,'' [http://wikiwww.mozillated.orgcom/talks/dan_pink_on_motivation/People:TRIBEwhich he has conveniently summed up in this 18 minute Ted Talk.]

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

===How does recognition differ around The responsibility of ''seeing'' other people for their accomplishments, the world===Notes from impact they have made, and the recognition sessions held at 2013 Summitwork that they do belongs to all of us.

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

Recognition brainstorming exercise from Community Builders meetup at MozCamp Asia in 2012: https:Mozilla can take on many different forms. Please go to the [[Contribute/Recognition/etherpadToolkit|recognition toolkit]] in order to see the different ways that Mozillians around the world are recognizing.mozilla.org/contributor-recognition-brainstorm

=Ways to recognizeRecognition in Different Cultures=

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 thereWe are still building resources around this topic, but below are some takeaways from sessions we've had.

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

A simple note of thanks is a great way to recognize someone. * email* blog post: https://blog.mozilla.org/community/category/spotlight/* postcard* etc.===Best Practices=====Badges==Carla Casilli has some great things to say about badges here: http://carlacasilli.wordpress.com/2014/03/17/a-foundational-badge-system-design/ Excerpt:"A badge system structure for manyAfter 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 upResources, top-downGuides, and middle out. It not only allows for growth, it thrives on it. Introducing the 3 Part Badge SystemThis 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==Archived Materials=* [https://docscbt.googleetherpad.com/a/mozilla.comorg/spreadsheet/ccc?key=0AnUOR-0CBMsTdDQ2TVlFX2xHTjhuaVYxUndDSmU5RUE#gid=1 Template for designing badges and criteriaWaystoRecognize Ways to Recognize]* I work at Mozilla. How do I make a badge?** Start here: [https://badgescbt.etherpad.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/RecognitionMozillians Recognizing Mozillians]* This is best for entire badge systems, vouching for verifiable skills/experience and learning. * Learn more by following their blog http[https://openbadgescbt.tumblr.com/ <b>Coming soon! </b> Badgekit-- currently in Private Betahttp://badgekit.openbadges.org/ ===Examples=== * WebQA Badges: https://qualityetherpad.mozilla.org/2013/12/webrecognition-qa20meeting-gets-badges/20notes Meeting notes from Recognition Working Group]* IT badge designs: http[https://clcbt.ly/image/1e3t0h1F093t and http://cletherpad.ly/image/403E170C3t0J* Creative Collective badge designs (from old Creative Collective site): http://wwwmozilla.flickr.comorg/photos/musingt/3811604179/in/setrecognition-72157617765620270goals Recognition Plan Q1 2014]* More: [https://openbadgescbt.etherpad.mozilla.org/Internal2013-Mozmeetup-badgetrack-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 [[GearStore2013 Community Building Recognition Track]] 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://repsetherpad.mozilla.org/featured/ Reps of the month programrecognition-guide-sc Recognition Guide from Santa Clara] * 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://wikietherpad.mozilla.org/GearStore). It’s a good place to start. *Don’t start at the top of the gear pyramid contributor-recognition- there’s no where to go if you give the best gear first. brainstorm MozCamp Asia Recognition Session]*Use the bugzilla form: https[http://bugzillawww.mozillailoveopensource.orgio/form.gear. All gear requests (except I love open source 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]developer recognition] (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://mozilliansopensource.orgcom/life/12/3/ mozillians.org], our blue-drop-awards-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 recognition-open-source-way by creating a unique certificate to honor their involvement. Some examples include:Drupal's Blue Drop Awards]* [http://wwweconomics.youtubemit.comedu/files/watch?v=hF5hrnPAPI8 Community Leadership Award given to Channy at MozCamp Asia in 20123023 MIT Paper on the Dynamics of Open Source Communities] * [httpshttp://air.mozillajonobacon.org/?tag=engineer Distinguished Engineer award Jono Bacon writes a lot about open source and videosrecognition] * [http://fridge.ubuntu.com/2013/06/14/certificates-for-ubuntu-members/ Ubuntu's membership certificate] ===Best Practices===