Why Is Anyone Talking About Yammer When We Have (and Love!) Teams?
Microsoft acquired Yammer in 2012 and made it available for their Office 365 customers the following year. Early in 2016, Microsoft rolled out Yammer to their Office 365 commercial customers as “on” by default.
At the time, I was an intranet manager at an association and decided to go along with Microsoft’s “on by default” rollout of Yammer. Why stop it? I started with a pilot for a few weeks to test it out, and then I opened things up to all staff. I got lots of folks interested in using it, but many wanted “private” groups for their teams to collaborate and communicate. They also heavily used the “private messaging” option in Yammer. They contributed to the public groups for sure, and enjoyed engaging across the org, but they really were craving some “private” options.
Imagine the confusion, then, when this “Teams” thing was suddenly all the buzz coming from Microsoft just a year later. Group spaces for people to communicate and post files? Check! “Chat” that seemed a lot like “private messaging”? Check! Option to subscribe and get email notifications for missed activity? Check! Plus, the interface was just so appealing, the chat was a much better experience than the “private messaging” in Yammer, and there were so many additional features in Teams.
Why the heck would we still use Yammer now that we have this new shiny Teams toy?