273
edits
Changes
Created page with "==About== What is the project: This project aims to evaluate Yammer as a communication tool, identify its strengths, weaknesses, and its role within Mozilla. Why are we doing..."
==About==
What is the project: This project aims to evaluate Yammer as a communication tool, identify its strengths, weaknesses, and its role within Mozilla.
Why are we doing it: We have a lot of different ways to communicate at Mozilla, and the sheer volume of communication can be overwhelming. The roadblocks to success survey identified communication as a main area of concern. As part of the effort to improve communication, I will examine how our community utilizes Yammer as a tool, what role(s) we expect Yammer to perform, and whether any changes are necessary.
Over the next six weeks I will be collecting data and community feedback around how we use Yammer (effectively and ineffectively), and will report back my findings to the people team and to the Mozilla community.
==Steps==
1. Collect Initial Data — Collect community feedback on how they use Yammer. Solicit feedback both from active users (e.g. why do you use?) and non-active users (what keeps you from using?). Start analyzing usage data/trends.
2. Collect Data Pt. 2 — Use initial input to offer a targeted set of questions based on findings from phase one. Points of interest may include: expectations (outcomes, etiquette, etc.), difference between staff and community space, and better understanding of points of stress/tension. Reach out to owners of Yammer groups to understand productive use. Gather social listening data.
3. Compile and Report Back — Synthesize data and community feedback, report back key findings to people team and then Mozilla community.
==Feedback==
Please email Tremaine Kirkman to provide feedback!
I will update weekly as community feedback comes in...
What is the project: This project aims to evaluate Yammer as a communication tool, identify its strengths, weaknesses, and its role within Mozilla.
Why are we doing it: We have a lot of different ways to communicate at Mozilla, and the sheer volume of communication can be overwhelming. The roadblocks to success survey identified communication as a main area of concern. As part of the effort to improve communication, I will examine how our community utilizes Yammer as a tool, what role(s) we expect Yammer to perform, and whether any changes are necessary.
Over the next six weeks I will be collecting data and community feedback around how we use Yammer (effectively and ineffectively), and will report back my findings to the people team and to the Mozilla community.
==Steps==
1. Collect Initial Data — Collect community feedback on how they use Yammer. Solicit feedback both from active users (e.g. why do you use?) and non-active users (what keeps you from using?). Start analyzing usage data/trends.
2. Collect Data Pt. 2 — Use initial input to offer a targeted set of questions based on findings from phase one. Points of interest may include: expectations (outcomes, etiquette, etc.), difference between staff and community space, and better understanding of points of stress/tension. Reach out to owners of Yammer groups to understand productive use. Gather social listening data.
3. Compile and Report Back — Synthesize data and community feedback, report back key findings to people team and then Mozilla community.
==Feedback==
Please email Tremaine Kirkman to provide feedback!
I will update weekly as community feedback comes in...
