Forum Discussion
When to use O365 Groups - is the Intranet dead?
Our organization is struggling to get started with SPO and O365 Groups. Yes, I know there are dozens of articles and threads about 365 groups and how they work - and for shorter project teams, group...
Our approach has been to create private and semi-private workspaces for teams that need to get things done. And yes, some of that is creating content to share internally with other people which requires open spaces to publish that content.
Office 365 offers a lot of different tools to do that and we've applied them all in different use cases: distribution lists, open Yammer groups, SharePoint publishing sites overlaid with LiveTiles, SharePoint enterprise wiki sites, and we look forward to having the new Communication sites in the tool belt.
So using IT as an example...
IT teams communicate using a set of Yammer groups. They also have a set of open Yammer groups for community engagement. We post information and we get questions and other feedback in return. Complaints too, that's part of the business. Internal IT documentation is maintained in a wiki document library in a SharePoint site. Documentation and help articles for users are maintained in an enterprise wiki open to the community. Video content is in Office 365 channels.
Maybe we would have done some of the stuff that is in Yammer using a tool like Teams or Groups instead if they had been available when we set all this up. We're debating what, if anything, might be worth migrating.
Office 365 offers a lot of different tools to do that and we've applied them all in different use cases: distribution lists, open Yammer groups, SharePoint publishing sites overlaid with LiveTiles, SharePoint enterprise wiki sites, and we look forward to having the new Communication sites in the tool belt.
So using IT as an example...
IT teams communicate using a set of Yammer groups. They also have a set of open Yammer groups for community engagement. We post information and we get questions and other feedback in return. Complaints too, that's part of the business. Internal IT documentation is maintained in a wiki document library in a SharePoint site. Documentation and help articles for users are maintained in an enterprise wiki open to the community. Video content is in Office 365 channels.
Maybe we would have done some of the stuff that is in Yammer using a tool like Teams or Groups instead if they had been available when we set all this up. We're debating what, if anything, might be worth migrating.
