Yammer Reviews

• External collaboration with partners: There is a unified way to send updates about departments and the enterprise, rather than sending separate communications.
• Inbox and notification for updates: This helps to manage messaging to stakeholders in a centralized and contextual way, rather than silo information sharing.
• Integration with Microsoft Office feeds: Since the enterprise works with Office, it is easy to use along with those tools.

We have used targeted notifications regarding the outages and maintenance windows to communicate with our stakeholders. This has helped centralized messaging for us.

Yammer can improve the effectiveness of its usage by addressing the metrics that measure user trust and perception. It measures the sentiments of posts using analytics and increases the ease of use.

I have used this solution for three years.

There were no stability issues. The product has been fairly stable.

There were no scalability issues.

I would give technical support a rating of 7/10.

The setup was straightforward.

This is a good option for medium to large-sized business enterprises.

We looked at the Slack solution.

If you are a Microsoft Shop, then Yammer has the potential to tie up with SharePoint and address a lot of the enterprise needs, in terms of messaging and content management.

• IM
• Groups
• Mobile applications
• Integration with Office
• Notifications

The product has allowed cross-functional discussions across every business group throughout the company. There was very little communication across business units prior to deployment. It is easy to find experts in a particular subject matter with a simple post to a group or to the company-wide group.

• Asynchronous, persistent chats
• Search capability
• Tighter integration with Outlook (i.e., be able to post directly to Yammer groups from Outlook)

I did not encounter any issues with stability.

I did not encounter any issues with scalability.

We previously used Chatter from Salesforce. We switched because the company was deploying Office 365 and it made more sense strategically to fully leverage Yammer instead. There were a smaller number of users on Chatter versus Yammer.

The user account setup is not automatic as a person activates Office 365. I was not involved in the setup of the environment.

This is an excellent choice if you have made the investment into Office 365. Announcement of teams should offer even better functionality. If you are not an Office 365 shop, then there are probably better options (i.e., Slack, Facebook for Work).

• Announcements
• Notes
• @mentioning
• How not to follow conversations once your inputs have been received

From the point of view of knowledge sharing, we created a group per project. While we had SharePoint for storing documentation, we were able to link to these and give them content in Yammer.

• @mentioning and the fact that you can't then tidy up the name.
• Linking differing groups, without introducing hierarchy.
• I did a lot of UAT and security both internally to organisations and being a cloud SaaS caused issues. Therefore, I’d like to see more support documentation with regard to this.

I have used it for about three years.

Yammer was embedded in SharePoint. We experienced outages almost every Thursday; assuming this is a scheduled software update.

Technical support wasn't great. Our touch points in Microsoft Ireland were not knowledgeable enough on the product; issue experienced while going from Freemiun to Enterprise.

I did not previously use a different solution; first time using social enterprise.

Initial setup was very straightforward. It was prior to O365 integration. Simply access the Yammer URL, and set up your credentials. The company provisioning was carried out by Microsoft but I believe this was straightforward.

Before choosing this product, I don't believe we evaluated other options, but this was not my call.

Take the time to decide why your organisational culture will benefit from social enterprise. Let your workforce know that it is coming, communicate your organisational vision for it, and have a launch plan, training, champions and encouragement.

Yammer provides a simple to use, intuitive platform for enterprise collaboration within the social networking information model. Like other products in this space, Yammer takes a crowd-sourcing approach to knowledge management in the enterprise by allowing users to leverage powerful tagging and content collaboration tools to communicate and capture information and expertise.

Yammer is not as feature rich as the most mature offering in this space, Jive, however it makes up for this with strikingly intuitive ease of use and a much lower cost.

We are system integrators, and we use this solution in our group for social networking.

The most valuable feature of this solution is the communication events. We can set up meetings and events. 

I would like to see secure communication channels for our group.

This solution needs to be integrated with the Microsoft Cloud.

This solution would be improved if it was well integrated with other communication applications.

We have been using this solution for between three and five years.

We have a lot of applications for communication, including WhatsApp, Facebook, and Instagram. In the future, I think that we need to have only one application for communication.

I would rate this solution a seven out of ten.

• Ease of creating groups
• Simple but good user experience on mobile
• Ability to adaptively stream videos inline in the wall
• Ability to track foul words

• Increased collaboration between geographically distributed teams.
• Good way to share files and videos on topics of common interest.

Cannot import/invite bulk users from an active directory security group.

Two years.

No issues.

No issues.

Not interfaced with the support team.

Used Jive, but switched as Yammer became bundled with Office 365 at no additional cost.

Not involved in admin activities/setup, hence I cannot comment.

Cannot comment, as I do not have this info.

Jive and SharePoint.

Create a good governance mechanism and be weary of group/community explosion in the initial fad days. Need to ensure duplicate groups are not created.

Collaboration and the integration with O365. There are so many features, everything you could ever want, which is great for team collaboration.

It breaks down the silos of communication in organizations.

It just needs a more defined roadmap. Yammer is part of O365 and the whole platform is ever evolving, and new features show up sometimes unannounced, and you don't find out until one of your end users mentions it.

We have been using the solution for over five years.

We did not have any issues with stability.

We definitely did not have any issues with scalability.

We didn't use any other solutions previously, other than Facebook or Twitter.

The setup is extremely easy.

Pricing is part of the O365 subscription.

We did not evaluate other solutions.

You need an upper-level management buy-in and a good communication plan for end users to make this successful.

I just wanted to try out the program to know what it was and how it works and if it could enhance our office communications.  

I do not see the point of the product, and I do not like it to be honest. For example, one thing which I do not like overall with Microsoft products is that they are constantly changing them. The issue with that is that most of the updates and features which they are pressing users to adopt are not good or just not wanted or needed by the customers using the products.  

As an example, we did an email migration. Some of our users had contacts that were linked with the Outlook linking feature. This is a newer feature in Outlook, and nobody wanted it in the first place. It just made things confusing by adding unwanted information automatically, and a new feature does not need to be confusing. It shoul be tested first, it should be optional, and the current software trend is to do public beta testing. One person in our company had something like 30 linked contacts — emails and full phone numbers which were not his actually his own contacts. In the migration, these contacts all showed up as his.  

Microsoft has too many updates and they are updates that are not wanted. I could understand if updates were discussed or features are wanted, but Microsoft just throws things out there. In this case, they actually rolled back the feature some time after releasiung it. That should not be necessary and it just makes for further confusion. I think I am actually saying nothing new here, but lately almost every update which is coming out has some bugs or stops something else from working. Sometimes it is a driver problem, sometimes it is something else. But the frequency of the rollouts just increases the frequency of the bugs. It is not the best plan for software management.  

I would say the whole experience was negative, so that is why we stopped using it.  

We used the product recently for a short period of time less than a year ago.  

We did not use it long enough to really do testing and evaluation of the stability.  

It is enterprise software and was meant to be scalable. We never got to the point of rolling it out for the company.  

I have contacted technical support and it was okay but not very helpful. Many times the support people can not actually do anything. If I call about a problem with a feature or a bug, they can not fix it over the phone. So yeah, maybe they are trying their best and they are polite, but if you call about an actual problem rather than how to use a feature, they can not really be of much help. The support guys were great, but the issue is that they are not magicians.  

The initial setup was straight-forward. We were able to set it up on and we did it by ourselves.  

On a scale from one to ten where one is the worst and ten is the best, I would rate Microsoft Yammer as a four-out-of-ten. It was probably not useless, but it was of no help for our company and our situation.   

On-premises