Yammer Inclusion Reserach Findings



[On behalf of Tre Kirkman]

A few weeks ago in my blog I announced the Yammer Inclusion research initiative as part of the Diversity & Inclusion strategy. To begin the research I created a public etherpad to gather feedback from the community around uses and problems with Yammer. Today I’d like to share out some key findings and provide an update on next steps.

On the Yammer Inclusion etherpad, feedback identified Yammer as a place to ask questions when there is no readily apparent alternative. In addition, it seems to be a place for community building, especially for remote staff. Inactive users complained that Yammer is frustrating, time consuming, and overly negative, offering no compelling reason to use over other Mozilla communication channels. These issues were both technical (frustrating interface, etc.) and procedural (discussions too ideological).

Responders preferred the staff Yammer for posts containing sensitive or confidential information, although some felt the split leads to a situation where the community exchange is neglected and unused. Overall, there was a common theme that Yammer primarily functions as an open forum to share ideas, engage a wider community, and locate an unknown point of contact better than other channels of communication.

In the coming weeks I will research the recurring issues raised from the initial feedback to find potential solutions. For more information on the initiative, visit the wiki page Communication Research wiki. Please email me at tkirkman at mozilla dot com if you have feedback or ideas to share.

Firefox 32 New Contributors



With the upcoming release of Firefox 32, we are pleased to welcome the 68 developers who contributed their first code change to Firefox in this release, 53 of whom were brand new volunteers! Special thanks to Sezen Günes for compiling these statistics for this release. Please join us in thanking each of these diligent and enthusiastic individuals, and take a look at their contributions:

Grow Mozilla discussion this Thursday



If you’re interested in helping new people get involved with Mozilla, join us Thursday for an open community building forum.

Quality and Impact and the Future of the Grow Program

Sean Bolton


As you know, the Grow program was initially designed to to align with the “Enable Communities that have Impact” goal. The events were intended to mentor and train core contributors to help us bring our products to market and bolster our efforts to recruit new contributors in region.

Since then, we’ve received a lot of extremely helpful and direct feedback from participants, community members who did not attend and from a number of leaders within the Project. The sentiment, echoed on the Project call yesterday, was that the new focus was too much about increasing the size of our community, and not enough about the quality and impact of contribution.

Based on input from our community, and a lot of discussion last week during the community building team’s work week, we’ve made the very difficult decision to cancel all upcoming Grow events this year, including Tunisia, which was scheduled for this September. The decision was made so that the team can focus on launching a redesigned program aimed at providing more interesting and meaningful opportunities to contribute and innovate. This is very late notice, particularly for Mozillians who have spent time and energy completing applications for Tunisia, creating content, and helping with logistics and planning for the event. Know that we would never have made such a decision if we did not feel in our hearts it was the right one.

What’s next – refocus on quality and impact

We are really looking forward to seeing what opportunities we will have to come together as Mozillians in the near future. We know doing that (bringing communities together) is essential for individual, community and Project growth so planning around this isn’t going to stop – it just may look a little different. We’ve been thinking about things like smaller group meet-ups, either organized by Mozilla or as part of other, larger events like an upcoming open-source conference, where communities work together to provide solutions to very specific problems.

Now that we’ve made the tough decision about Grow, we can shift our focus towards a new program — one that focuses on the quality and impact of contributions and our community has a real, strategic, concerted impact on our goals this year.

We have some ideas already are we’re guessing you have some too so let’s start brainstorming! Here is the challenge we leave you with…

How might we design a program that results in contributions that are more fulfilling to our contributors and have a meaningful impact on our goals this year.

Please share your ideas here: https://etherpad.mozilla.org/grow14

– The Community Building Team

Lessons from LEGO (and other thoughts on community)

Sean Bolton


Communities form when you find a group of people that you feel you can be yourself around. In this environment, you don’t have to self-edit as much to fit in. You get the feeling that these people share a similar view of the world in some way. Communities form when the answer to, “are they like me?” is “yes.”

It’s not very surprising then that communities can form around brands as brands often represent a certain view of the world. Smart companies notice this and they engage these people in a win-win partnership to give their community value and to create value for the organization. That is no easy task. Here is a bit about how LEGO does it…

LEGO cares deeply about their community. They know that these people drive their brand, provide the best form of marketing and can help fuel new product development. And the community members get a powerful sense of fulfillment in meeting similar people and getting to be more of a creator than a consumer – they get to make LEGO their own. When working with community LEGO follows these principles (a non-exhaustive list):

  1.  Every engagement must be win-win
    • This matters because only in win-win partnerships do both sides have a good experience and can community continue to grow. It means that there is some saying no. But the saying no is so that more yes can happen later.
  2. LEGO does not interfere with community
    • This is powerful because it lets people all over the world organize their groups in a way that best makes sense for them. LEGO does not have to waste resources and can be more culturally sensitive by letting others manage their groups in the ways that best suits them.
  3. Members are respected and expected to respect each other
    • Every community should have a code of conduct to ensure that people respect each other. This is common practice so that members don’t get abused.
  4. Empower people to do what they want to do
    • You can’t force community to do something there is no passion behind doing – it’s just not how it works. The fact that LEGO is explicit about that is a big deal and it makes community respect them for it. That’s powerful.

LEGO has high quality standards and the way their community team works is no exception. They have a communication structure that empowers people to help and learn from each other so that not every person needs to communicate with LEGO directly. There are designated ‘ambassadors’ that communicate directly with LEGO – they help distill and clarify communication, taking a sort of leadership role in the community. This helps LEGO better focus resources and helps build a stronger sense of community among members (win-win).

There is a massive community surrounding LEGO, over 300K. To reference, we currently have about 8K at Mozilla. While our communities do different things, we are all fundamentally driven to be part of that group that makes us feel like we can be more of ourselves. It gives people a sense of belonging and fulfillment – something we all want in life. That is why community management matters. Without it, these large groups of people can’t exist and that sense of belonging can be easily lost.

[Post also appeared on Sean Bolton’s blog.]

Yammer Inclusion Research



Dino on behalf of Tre Kirkman

My name is Tre Kirkman, a summer intern with the Legal and Policy teams. I am currently a student at Stanford University studying Public Policy, African-American Studies, and Computer Science. I am especially interested in the ways that organizations create (or fail to create) inclusive spaces for employees to thrive.


When I first arrived at Mozilla I met with Dino to find out how I may contribute to the Diversity & Inclusion Strategy. After taking some time to refine my ideas with both Dino and Mardi, I came across the Roadblocks to Productivity survey, which highlighted the need for Mozilla to refine and improve its modes of communication.


To that end, I will be helping with a Diversity and Inclusion Initiative and Removing Roadblocks to Productivity by conducting research into staff use of Yammer — How do we use it? What draws in regular users or pushes away inactive users? Is it an inclusive space? My project will try to gather useful community feedback and social listening data to accurately assess Yammer’s role within Mozilla. Ultimately, I hope this research will be a useful resource for both initiatives as they work to continue making Mozilla an amazing place to work.

Next week I will put up an etherpad with a few short questions for community feedback. In the meantime please email me at tkirkman at mozilla dot com if you have questions, concerns, or ideas to share.

E-Mail Subject Line Etiquette: helping decrease communication stressors



Dino posts on behalf of Payam Keshtbod

Hi everyone!

My name is Payam Keshtbod, a Mozilla Volunteer Contributor on the People Team. I am currently a student at Indiana University with an interest in Industrial/Organizational Psychology, particularly on how “mental stressors” affect employee productivity and overall well-being. Stressors are things that cause mental tension for individuals.

I will be contributing to a Diversity and Inclusion Initiative and helping on the Removing Roadblocks to Productivity,  regarding ineffective communication. My project will look at how we can put in place some good practices to decrease stressors and ineffective communication in e-mail subject lines.

If interested please go on to this etherpad to contribute your ideas. I would love to hear your ideas on how you can make subject lines in emails more clear, effective, and efficient for the writers and readers.

Please email me, payam.keshtbod(at)gmail(dot)com) to comments, questions, or feedback! I will update weekly as community feedback comes in.

Grow Mozilla discussion this Thursday



If you’re interested in helping new people get involved with Mozilla, join us Thursday for an open community building forum.

APPLICATION EXTENDED! LAST CALL! Apply to attend Grow Tunisia by MONDAY!



We are aware that the application to Grow Tunisia (formerly MozCamp) closed early by mistake so we are extending the application through MONDAY, AUGUST 4! Please apply now if you haven’t already!

This is the final reminder that applications to attend the regional event for dedicated community builders in Europe, the Middle East and Africia, Grow Tunisia (formerly MozCamp), are now due by Monday, August 4 with the extended deadline.

Grow Tunisia will take place in Tunis from Friday, September 26, through Sunday, September 28. Participants must be available to arrive on Thursday, September 25, and should plan to depart on Monday, September 29.

If you’re unsure if you meet the application requirements, please apply! We have a panel of Reps and other community members who will be reviewing each application, so they can determine if applicants fit the requirements so you don’t have to.

To find out more about the Grow program and the Grow Tunisia event, please check out the wiki.

If you have any questions, please take a look at the FAQ first and if your question isn’t there, ping me on IRC in #Grow2014 (lmn) or reply to me via email.

New Get Involved Page Prototypes and Community Involvement So Far

Sean Bolton


Mozilla is not just one voice and the way we build our products, especially the Get Involved page, needs to reflect that.

We have involved the community on this project so far in many ways including meetings, blogs, etherpads, surveys, mail lists, card sorting, MozCamps and more. We will continue to do so.

As much as we at Mozilla like to dream of a world where community is a default, it takes some intentional planning to make it that way. The mysterious magic of community is actually less mysterious than it may seem. With the Get Involved page project, we have seen the value of planning ahead and creating intentional structure for community involvement. In doing this we allow both community members to feel useful and make sure that their involvement creates a more successful final product – there is an unarguable value in having community involved.

Continuing with this momentum, today there are 3 early prototypes available which have been created from a history of working with the community on this project. Each one has a distinct approach different from the others, for testing purposes.

You have the opportunity to share your input on these early prototypes and we have provided an easy structure for you to share that with us so we can be sure to incorporate it in the evaluation of a final design – we don’t want your valuable feedback getting lost in overflowing email inboxes. Please use the following Survey Gizmo link to provide your feedback by August 7th (links to prototypes are in the survey): http://www.surveygizmo.com/s3/1747304/Feedback-Get-Involved-Prototypes When doing so, remember to approach this page from the perspective of a potential contributor. We are specifically checking for how easy, clear and compelling it is to get involved. Please check the wiki page for future updates. We thank you for your participation here – it makes a difference for future contributors.