Changes

Jump to: navigation, search

Communication Research

4,259 bytes added, 22:18, 20 August 2014
Updates
====Week 2:====
Posted etherpad to collect initial community feedback: https://etherpad.mozilla.org/Yammer-Inclusion
 
====Week 2:====
Results from the etherpad posted:
 
For active users: What are your main reasons to use Yammer? (short phrases please)
* Discuss large company decisions +6
* Debate leading to resolution or organizational action +1
* Share articles/ideas +1
* Get the word out about new initiatives +2
* Asking questions when you aren't sure who to ask +5
* Asking questions when there is no appropriate place to ask elsewhere +2
* Feel connected to the community +2
* As a new hire, reading old threads to find out what people think about issues +1
* Connect with people by sharing cat gifs
* As a remotie, it's my virtual watercooler for casual conversations +1
* I use it for company-wide discussions since it's a bit more opt-in than emailing "all". +1
:* And less taxing. An email needs to be deleted, archived, or otherwise handled. A Yammer comment can be scrolled past/ignored.
* If someone pings me on there by name, I'll go look at Yammer for a while.
* It is nice to see people "like" a post.
* Discover shared alignments with other people. Who thinks like I do?
* Gives me a sense of people's personalities and possible friendliness
* Share ideas or news that I think might be of general interest to Mozillians, in a way that they can ignore if they're not interested.
 
For inactive users: What are your main reasons for NOT using Yammer?
* It's usually unproductive +3
* Most employees do not use it so as a contributor I find no value
* Too many channels already, no pressing reason to use Yammer +6
* It's time consuming +3
* Offers no clear value/use so I never started +1
* Frustrating experience/interface +2
* Is mostly negative, and I think staying positive is critical for overcoming challenges +1
* Tool closed source, prefer other options that are more in line with our values +1
* IRC usually suffices for casual conversation.
* Facebook-like interface, fun but a bit distracting from work
* Internal Yammer has no non-employees; other Yammer doesn't have enough take-up
* Conversations can quickly turn very idealistic instead of realistic and are full of bickering and complaints that provide no tangible next steps.
 
Do you have any difficulties on Yammer due to your location/timezone?
* No +8
* Do you have any difficulties on Yammer due to your level of fluency in English?
* What types of activity do you reserve for the staff network (vs. the exchange that includes volunteers)?
* Confidential/non-public information +1
* Internal discussions that are not ready to be opened up to the broader community +3
* Personal information
* Opinions and information about sensitive topics like strategy or our partners
* Discussions about Mozilla's culture
* Discussions about our work environment, like remote work, snacks, and wifi +1
* Discussions about benefits
* Discussions that we have decided we want to keep secret even though most times they are not confidential and should be shared out but we do not.
* I use the staff Yammer for most comments, simply because it has a bigger audience. A post to the staff Yammer is more likely to be seen than a post to the volunteer Yammer, even though the volunteer Yammer is supposed to be a superset of the staff Yammer. Few people (and very few staff) read the volunteer Yammer, partly because it's so hard to remember how to get to it.
 
What Yammer functions would you consider vital for your work?
* None +6
* Its very existence
 
What role(s) do you expect Yammer to perform for the organization?
* Place for open discussion +3
* Allow people to voice concerns and create action +3
* A place to share smaller announcements where a Monday lightning talk may not be the right channel. +1
 
What do you do on Yammer that you cannot do in any other communication channel?
* Share an announcement or get feedback from a core group of contributors. As a channel it can be more effective than a blog post, tweet or lightning talk at the Monday project meeting. Plus, most people get a daily email digest of Yammer posts and are likely to read your post.
* Have a sense of a social network. Mozillians, irc, mailing lists don't provide this.
* Share an idea / comment that will be seen by the relevant person (who may be unknown at first) without distracting everyone else (which all@ does)
==Feedback==
273
edits

Navigation menu