For the past several days, rumors have been swirling around that Microsoft is about to buy Yammer. The Wall Street Journal is saying it’s a done deal, although neither Microsoft nor Yammer has made an official announcement.
If this acquisition does come to pass, it will be interesting to see how it plays out. Microsoft has been very successful with SharePoint — but it’s a very different animal from Yammer. At this point, enterprises buy three levels of collaboration tools: (1) production (e.g., Documentum, Open Text), (2) purposeful (e.g., Lotus Notes, SharePoint), and (3) ad hoc (e.g., Box, Yammer). If Microsoft buys Yammer and puts it within the SharePoint division, over time it runs the risk that it will make Yammer more SharePoint-like — and thereby eventually dull the features that make it complementary to SharePoint.
Ideally, Microsoft should create a Collaboration division that contains both SharePoint and Yammer — in other words, make the product divisions subordinate to a way of working. However, Microsoft has been organized into product divisions for years, so I doubt that will come to pass. Again, it will be interesting to see if and how Microsoft + Yammer plays out….
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
The Education CIO Challenge: IT Is a Team Sport
This video will outline key Education CIO challenges and recommendations based on business and technology trends in education as well...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.