Encouraging adoption in enterprise social networks

This content is 8 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

In my job, consulting with many organisations who are adopting Microsoft products and services, including Office 365, I have a lot of discussions about Yammer and other modern communication methods (e.g. Sway).

Many have already had pilots with Yammer and found it didn’t work for them. Some are smart enough to realise that it wasn’t Yammer at fault but a lack of executive sponsorship. Adapting a new medium for communication takes time; it needs a cultural shift. If your boss uses it, you might consider giving it a try (although when I had a team, my experience at getting them to use Yammer was best described as mixed). But if your boss’ boss uses it, or the CEO, and the internal communications team are are using it instead of email, then you might stand some chance of success – because, as well as executive sponsorship, it needs critical mass (which means people need a reason to visit).

Of course, the platform itself has to be usable. In my last place the corporate social platform was Newsgator (which was awful), coupled with an old version of SharePoint and, aside from the teams whose job it was to evangelise its use, it was pretty much ignored. In fact, so much so that other social networks popped up in their own bubbles: the sales community were using Salesforce Chatter; although Yammer actually seemed to gain more traction in some areas (via an external network hosted by Microsoft for partner engagement) because there was something of value there for people.

So, we need executive sponsorship, critical mass, and a usable platform, with content that people value. But there’s something else too – people have to stop using the old methods in parallel.

Recently, I witnessed one organisation where someone posted some infomration on Yammer and it got a flurry of activity/commentary on the original post (so far so good). Then someone else sent an email to a distribution group to highlight the same information. That sender might not have seen the original post but email isn’t a good way to share links about new products. Some (myself included) may consider it as just unsolicited bulk email (spam) but spam that’s sent from inside the organisation. To make matters worse, because Office 365 Clutter doesn’t filter out email from people in your management chain, that email will never be filtered.

No, no, no, no! Post once, on the right medium*. Yammer for information sharing/comments on a topic that might run and run; instant messaging for messages that require a response… instantly (the clue’s in the name) and stop abusing email (which, incidentally is an asynchronous communications mechanism to which you should not require, or even expect, a response). As for voice mail, SMS, etc. Well, who knows… anyway, I’m supposed to be writing about getting people using enterprise social networks here – not a lecture on communication methods (and I know one size doesn’t fit all).

So, that’s my view – which you might agree with, or you may not. But it’s been cathartic to have a little online rant and at least it means I’ll get at least one blog post up this month! For another view, take a look at what the Yammer team at Microsoft shared with me – a 2012 Office blog post on Deploying a Successful Enterprise Social Network: Best Practices From the Field.

 

Mark Wilson is an increasingly busy, grumpy and ranty man, who wants to reduce the volume of email arriving in his Inbox…

* I do have to admit that, on occasion, I have been known to email a group of people and say “please reply to my thread on Yammer”, because I knew a lot of them didn’t use it but I wanted everyone to see the replies withough creating a Reply All email storm. This is not good.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.