Yammer's UX and UI are areas with certain shortcomings where improvements are required. Yammer's UX and UI should be made more user-friendly and organized. For improvements in the area of stability, the solution requires improving its UI and UX while ensuring better integration with other tools, like Microsoft Teams. Sometimes, there seems to be some overlapping of features in the solution, especially in the area related to the creation of a repository, because of which one may not be able to identify when using Teams and Yammer, making it in the area which is unclear owing to a lack of best practices.
It looks slightly less clean on Chrome compared to Microsoft Edge, but it's a minor difference. There is room for improvement in user experience, like positions of elements.
Yammer should include more integrations. It would be useful if I could fully integrate all my work into the solution. I would like to have an option to seamlessly share a document or a presentation using Yammer so that everybody can access, see, and appreciate it. I would like to have the option to do that without having to set up a whole post separate from my everyday work. Suppose you work in marketing, and your job is basically to socialize a whole lot of events or ideas. It would help if you could instantaneously share that work while you're doing it so that you can get people ready on a platform.
Microsoft Modern Workplace Solution Architect at Novartis Pharmaceuticals
Real User
Top 10
2023-07-31T16:02:00Z
Jul 31, 2023
Although Microsoft is working on it, having a centralized network instead of creating multiple networks based on a domain would help businesses with multiple companies or child companies. A single network Yammer would be a better option for administrators and not for end users because end users wouldn't know it.
Director at a financial services firm with 51-200 employees
Real User
2020-10-08T07:25:26Z
Oct 8, 2020
The way you want to control the communication could be an issue. It depends on what kind of company you are. We are a public company, and there are some regulations that we need to comply with. Its ease of use can be an issue for a company because anybody can subscribe and use it. There are many competitors that are overlapping. Since Microsoft bought Yammer, it tends to be in the shadow. It is not put in the front from the service perspective.
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.
Program Manager Change & Communication at a insurance company with 501-1,000 employees
Real User
2019-10-23T05:52:00Z
Oct 23, 2019
Because we are in Belgium, we have two languages and the program is only in one language. It could have been interesting to have it in both French and in Dutch. We tried to integrate into SharePoint, but it was not really efficient.
Senior Manager at a non-tech company with 5,001-10,000 employees
Real User
2019-10-15T05:02:00Z
Oct 15, 2019
Yammer shall not stay an independent non integrated service and shall not duplicate what team and outlook services do - it can be the heart of outlook conversations / publishing
General Manager: Internal Communication at a comms service provider with 1,001-5,000 employees
Real User
2019-10-13T05:48:00Z
Oct 13, 2019
The solution must be able to stream by itself, without integration, the same way that you are able to do it on Facebook Live, Instagram, etc. Streaming must be embedded into it. The ability to just be live, I think is very important. You don't want to leave the app to go live. You want to be able to just go live within the app. So I think that their internet streaming ability would be a very good feature to add.
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.
Yammer is an enterprise social network that allows employees,managers, executives, teams and different office branches to engage,collaborate and innovate over one interactive virtual network.
Yammer creates a social workplace that drives innovationthrough the sharing of ideas and business intelligence, boosts productivity inteams and projects, and encourages communication and connectivity betweenemployees, no matter where they are located.
Sometimes, we lose access to the solution for unknown reasons.
Yammer's UX and UI are areas with certain shortcomings where improvements are required. Yammer's UX and UI should be made more user-friendly and organized. For improvements in the area of stability, the solution requires improving its UI and UX while ensuring better integration with other tools, like Microsoft Teams. Sometimes, there seems to be some overlapping of features in the solution, especially in the area related to the creation of a repository, because of which one may not be able to identify when using Teams and Yammer, making it in the area which is unclear owing to a lack of best practices.
It looks slightly less clean on Chrome compared to Microsoft Edge, but it's a minor difference. There is room for improvement in user experience, like positions of elements.
Yammer should include more integrations. It would be useful if I could fully integrate all my work into the solution. I would like to have an option to seamlessly share a document or a presentation using Yammer so that everybody can access, see, and appreciate it. I would like to have the option to do that without having to set up a whole post separate from my everyday work. Suppose you work in marketing, and your job is basically to socialize a whole lot of events or ideas. It would help if you could instantaneously share that work while you're doing it so that you can get people ready on a platform.
Although Microsoft is working on it, having a centralized network instead of creating multiple networks based on a domain would help businesses with multiple companies or child companies. A single network Yammer would be a better option for administrators and not for end users because end users wouldn't know it.
Yammer has very limited features.
The way you want to control the communication could be an issue. It depends on what kind of company you are. We are a public company, and there are some regulations that we need to comply with. Its ease of use can be an issue for a company because anybody can subscribe and use it. There are many competitors that are overlapping. Since Microsoft bought Yammer, it tends to be in the shadow. It is not put in the front from the service perspective.
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.
Because we are in Belgium, we have two languages and the program is only in one language. It could have been interesting to have it in both French and in Dutch. We tried to integrate into SharePoint, but it was not really efficient.
Yammer shall not stay an independent non integrated service and shall not duplicate what team and outlook services do - it can be the heart of outlook conversations / publishing
The solution must be able to stream by itself, without integration, the same way that you are able to do it on Facebook Live, Instagram, etc. Streaming must be embedded into it. The ability to just be live, I think is very important. You don't want to leave the app to go live. You want to be able to just go live within the app. So I think that their internet streaming ability would be a very good feature to add.
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.
I would like to see a fancier user interface. That is one of the weak points of Yammer.