Dec 04 2017 01:29 AM - edited Dec 05 2017 07:40 PM
Yammer is no longer the only enterprise tool in the MS suite that's similar to how we converse in consumer tools like Facebook, Messenger, WhatsApp, etc...
Now we have MS Teams...and now that means clients we consult with are asking about the differences, etc...the inner and outer loop approach helps.
One of my concerns now is that newbies have to learn different terminology for similar functions across both tools.
I've made a quick list below, please add more if I've missed anything...
GROUP/TEAM LIST
Note: Teams has an extra function where you can unfavourite a team or a channel from the favourites list (which puts it into a collapsed more list)
NEW UNREAD ITEMS
NOTIFICATIONS
Note: If I don't follow a channel in Teams, I will only get notifications in my Activity feed if I'm: mentioned, replies to my posts, replies to my replies.
If I don't check push notifications on a group in Yammer, I will only get notifications in my Yammer Inbox if I'm: mentioned, replies to my posts, replies to my replies...and also posts I have manually followed to inbox
===
Given these are both Microsoft products it would be good to see some consistency with the names of features...this would help user adoption, as understanding one system would give you a headstart in understanding the other system
But this isn't the case...
WHAT IS "FOLLOW"?
Note: Yammer also have a feature called "Follow in Inbox", where you can manually set a notification to get new replies from a post (even if you have not taken part in the conversation of that post)...you can also unfollow at anytime. So basically the notification feature is called "push" when it's for every post from a group going to your inbox, but it's called "follow" when it's for just a post of your choosing from any group
INBOX or ACTIVITY?
Dec 04 2017 11:54 PM
Dec 05 2017 12:03 AM
Jan 15 2018 07:52 AM
Great points although I think it goes further than just Teams and Yammer. Lots of terminology around O365 Groups/Teams follows inconsistent patterns which causes a lot of confusion to end users. A key one is that if an employee creates a Team, they start seeing 'group' in various places such as SharePoint and Outlook. SharePoint Team sites also cause some confusion with staff thinking they are connected in some way.
Jan 17 2018 05:11 AM
I've heard this point consistently since the first version of SharePoint Portal and STS back in 2001 ... two teams not really talking to each other ... bump into each other in the corridor and hey we are both doing something similar - lets err ... collaborate. Sigh ...
Garry @ Selfridges