Forum Discussion
Chris Shaida
Dec 11, 2016Iron Contributor
O365 Groups-based Places - Yammer + Teams + Outlook Groups
We are working on several artifacts as we make sense of how to use the emerging 'O365 Groups as a Service'-based Places. 1) our enterprise's take on the O365 apps broken down into Places, Tools a...
Dec 12, 2016
I'm starting prep to do this exact thing for folks at my company -- rolling out in Jan. So I can appreciate the degree of difficulty...
Some thoughts:
- I don't think the average employee cares or knows about Microsoft Graph. I'd leave that out to reduce complexity. Possible you could replace it with Delve
- Similarly, we know Groups is a foundational element, but it's also a destination.
- We are likely to use the terminolgy as O365 Group Sites and refer to our existing SP /teams/ sites as Team Sites--even though MS does call the Group Sites as Team Sites. Point is that they are more standalone in concept than a vast nested network of sites as with traditional Team Site site collections. This also gives us the opportunity to reinforce the "modern" nature of Group Sites that have fewer "classic" constructs.
- You have some dupes or near dupes in your Outlook vs. Yammer vs. Teams chart. Again, suggest reducing complexity. I do like "Potential for knowledge re-use" as an idea. That's a really good one.
- In theory Microsoft expects many O365 Groups (with Outlook) will be Public and thus discoverable. Are you disabling Public Groups?
- We haven't truly playtested this theory, but I think people are going to understand Groups messages in Outlook using Microsoft's term "next gen distribution lists". Then, it's a matter of trying to understand why they would want to use Yammer instead - or to add Teams or not.
- I really like Microsoft's term "high velocity teams" and tying that to "persistent group chat". I think a lot of people are going to understand why that isn't the same thing at all as Yammer.
- Teams use case: quick conversations with peers (water cooler, who's in the office today, have you seen a certain colleague, where are you with that task, is the outage still going on, who's going to answer the director's question, etc.)
- Yammer use case: "community of interest" conversations (Mac users, home workers, people in a certain building or geo location, groups related to company initiatives or events, broad organization discussions, other event specific conversations - YamJams etc.)
- Chris ShaidaDec 12, 2016Iron Contributor
Thx. Great stuff
.groups as foundational vs destination - our lives would be much easier if ms had not used 'groups' for both
.distinguushing SP sites created by o365 groups from other is excellent
. We haven't disabled public outlook groups but they have had very little pickup (we use yammer extensively) I think the initial consternation for our people will be between yammer and teams.