01-04-2017 11:29 AM
01-04-2017 11:29 AM
Hello all! After a LONG sabatical I am happy to be back in this network and wanted to kick off of the new year by sharing a best use case template that has worked very well for our organization and we have gradually seen an uptake with Yammer in different business groups. This might be helpful for anyone that might be needing to structure Yammer groups with clear and measurable objectives. It can be modified to your organizations' needs and has been helpful in gaining buy-in from leadership as well as accountability for users. For confidentiality reasons, I can't share a specific example but I hope the information in this document can shed light for anyone who needs it.
One last comment, although not all Yammer groups are following this structure (yet!) I can happily say that 100% of the teams that are following this structure have demonstrated a 70+% engagement from kickoff of group:-).
01-04-2017 02:21 PM
A great share - thanks Lillian. I think your document does a great job of defining the clear purpose and value to be acheived through the community, as well as the range of activities that will bring the community to life.
I've attached a document I've been using to help scope communities of practice in my organisation, with a key focus on leveraging Yammer as one of the community's channels. I create this document in partnership with the person charged with or seeking to set up a community. The initial questions are similar to yours, but you might find the last page interesting. It summarises the scope of the community and has some simple guidance and tips for community members to help them see what good looks like. We provide the last page to community members as part of the launch of the community, so they have a simple reference. See what you think.
01-05-2017 09:30 AM
I absolutely love your page 3! Fantastic job laying out the scope, the specific Yammer actions (like, comment), and my favorite "what a good Yammer post looks like". I think this is great, thanks so much for sharing! Your timing is perfect because I have a group that needed guidance on what exactly was the benefits. Looking at your document I like the language used because it creates that accountability from start. I'm going to give this section a try and see how it goes with the group. Thanks again!
01-05-2017 04:53 PM
01-03-2018 11:13 AM
Thanks for the template! Just curious, is your organization also using MS Teams? Yammer is great for communicating to the critical masses of the organization, but once you start getting into collaborative communication needs of internal departments (e.g. Finance as per your example), I'm thinking in most cases MS Teams is more robust and a better fit - your thoughts?
01-16-2018 06:42 AM - edited 01-16-2018 08:05 AM
Hi @Steve Seki,
(editing response because I misread your question)
Yes, I 100% agree with your thoughts, but I will say, we are treading carefully just because in the last year Yammer gained even more leadership endorsement and support. In fact, our new CEO has brought positive cultural change so we are seeing a very healthy interest in Yammer and sharing across the organization.
Funny thing, last year a small team of 3 people was adamant that they wanted to work with a "more modern" tool like Teams and they didn't want to bother with Yammer. So along with senior leadership we went through requirements etc. and we recommended creating an MS Team along with a Yammer group that they could add as a tab in Teams. (They needed a place for backend work and a public place for gathering ideas from people.) Yet, after all the work and conversations the team decided to go in another direction and by the end of the year I just decided to let things be.... However, to my surprise, earlier this week this same team created a private and public group in Yammer (which I could insert smh - shake my head emoji here) and don't want to bother with Teams after all!
Similarly, the legal department decided Yammer was what they wanted to use for departmental communication and decided to use a private group (they also didn't want to deal with Teams.)
So all that to say, we aren't going to push Teams too much just yet. Ideally, we would like for people to use Teams for smaller environments but if Yammer works for them then we will let them run with that solution. The reality is that people ask us to "tell" them what to use, but in the end it comes down to what they feel more comfortable with.
By the way, I'm attaching visual we use (inspired by Ignite 2017 Inner Loop Outer Loop and other community sharing.)
01-16-2018 08:22 AM
Thank you!! Happy to share! I enjoy your Twitter and community sharing too ;-).
Here's a quick update for all since I started this post!
We ended 2017 with a strong positioning for Yammer. Our company now has 4 top executives supporting and endorsing Yammer (HR, Global Communications, Legal and Operations). We made a conscious effort in 2017 to focus on relevant use cases and tracked successes that tied to cultural changes and $$ objectives. Each use case was linked and labeled with language that resonated in our company. For example: #Think External or #Maximize Resources and we used those examples to market and promote Yammer.
For 2018, we will be moving things like Organizational Announcements to Yammer which will encourage more use of the tool overall. I'm hoping to see our CEO engage in Yammer by the end of this year ;)
01-16-2018 11:16 AM
Thanks for your response and diagram - very insightful. We are planning on rolling out Teams and Yammer simultaneously following the model in the diagram below (similar to yours).