There has been a lot of discussion in the past weeks about enterprise social computing, especially based on the Microsoft stack. Just look at the great posts from Jeremy Thake<\/a> and Nick Patel<\/a>. And, let\u2019s not kid ourselves: Microsoft is market leader in that field – all the other potential competitors are quite behind. Microsoft invested a whole lot money and resources in the new social features stack that came with SharePoint 2013. And, bought a market leader, cloud-based enterprise social network called yammer<\/a>, for 1.2 billion US$. Without intention of beating a dead horse, I just wanted to state my opinion on the topic here, an opinion that comes out of the experience that I have made in the past few months with my customers.<\/p>\n

<\/p>\n

<\/p>\n

Microsoft has some strong cards in the hands \u2013 even though it has some serious architectural issues (posts in SharePoint lists?!), and some teething troubles, SharePoint 2013 came with a solid social features stack. It blends very good with the SharePoint content and SharePoint landscape. And there has been a great demand from customers for this type of social-on-top-of-content features.<\/p>\n

Enterprise social is all about content and productivity. It lives together with the content, it draws its power from the content, and for the most of the customers, it really doesn\u2019t matter without content, and without their corporate context.<\/p>\n

And then, there is yammer. It had a great adoption story for being easy to setup and start \u2013 it\u2019s just a click away. It is like a facebook, without being facebook. Basically, for whatever reason you would start a facebook group as a private person, you would start a yammer network in the corporate world. But, yammer is unconnected and unrelated to the content. It is a separate system, which needs separate login. It is a closed system, very difficult to build on top, at least at the moment. Further-more, it\u2019s a cloud-only platform (you can\u2019t install yammer on premise, just like you cannot install facebook on premise). And that can be a real drawback, especially for some conservative, \u201cold-fashioned\u201d European companies, which love SharePoint.<\/p>\n

So, when will yammer really matter in the corporate world? When will it bring an added value to the customers, other than being facebook without being facebook? The answer is really simple – when it seamlessly blends into enterprise content.\u00a0 I don\u2019t think that being cloud-only will be a real drawback, at least not in a long run \u2013 customers will eventually get used to it. Yammer needs to step out of its shell, to blend together with content, to ditch the separate file storage and use SharePoint in the background, to solve the identity problem (you just cannot have one identity for Yammer, and another one for the rest of the Office 365!), and to offer a great developer story. As a developer, I predict that Microsoft will need to rebuild Yammer from the ground, if they want to make it work.<\/p>\n

It will eventually happen, I don’t know when, but it will. Then, I\u2019ll bet my money on yammer. But these steps need to be made.<\/p>\n

Until then, it is facebook without being facebook. A good start, but there needs to be more to it.<\/p>\n