simplypresents: Microsoft

Microsoft 365. Your productivity cloud across work and life.

Yammer and Teams: spot the difference?

Started 8 days ago

Glad to hear during the Microsoft session that we're not the only ones struggling to explain the difference between Yammer and Teams. 

It's great for comms teams to understand the use cases in theory, but it shouldn't fall to us (entirely) to convey this to end users. Are there any plans to differentiate the UX so people can see straight away that the two platforms have a different purpose?

Good to hear from you, Ben. There will always be some degree of overlap given they're both communication tools, afterall. We've done quite a bit of work in our update to the Yammer UI to really focus it on being for communities. One big change we made was renaming "Yammer Groups" to "Yammer Communities". We think that teams and communities are different and wanted Yammer to convey that better.

I believe you've seen and have access to the Yammer preview. I'd be curious as to your input on what UI/UX elements should change in order for the purpose to be more clear. 

Hi Florance, thanks a lot for your response. I've been using the new Yammer for a couple of months now and it certainly looks smarter - I do agree with the renaming of "groups" to "communities". And there are a host of other UI cues that many comms professional will take note of. 

The challenge is that most people don't look that closely. On both platforms, they see a long feed of conversations, with a list of groups down the left hand side, the same round avatars, "likes"/reactions, @-mentions, GIFs... On a superficial level, anyone would be forgiven for thinking they're the same.

Honestly, I don't know what the solution is - I just think it would reduce confusion if they looked more different. What if each experience started by showing the kinds of content that make that platform useful, perhaps as an array of panels at the top of each community/team? Maybe for Yammer this could mean pulling out a few popular questions and answers, polls, stories, videos, etc.; whereas Teams could show more work-focused content such recently updated documents, upcoming meetings, notes/recordings, and so on.

Obviously there's a balance because you don't want things to look cluttered, but I do believe that leading users into the experience more would help us to drive adoption, particularly of Yammer.

Sorry - obviously I meant to start that with "Hi, Angus!" - it's been a long week :)