Collaboration Silos
Traditionally, our collaboration tools have been divided into silos based on the mode of communication. In the Microsoft space, we've used Outlook and Exchange for persisten...
Updated Apr 30, 2021
Version 3.0
Blog Post
We are planning on building out our existing Teams site, primarily for building community in our 3000-team member organization – so really using Teams as our virtual watercooler instead of Yammer. In looking more closely at the number of existing Teams across our org, as part of this process, we also want to consider potentially minimizing and streamlining the number of Teams and instead roll those up under an uber Team containing multiple channels – much like one would use Slack. Besides Permissions, what do we need to consider? What are some of the best practices out there?
In addition to Teams, we also have a Communications SharePoint site that we use across our org. Understanding that each Team is connected to a unique SharePoint through an O365 group, we’re wondering if we create this uber Team that comes with a O365-connected SharePoint, so we need the Communications SharePoint site we have today. Can we just transition everything to the Teams SharePoint? What are the limitations, considerations, etc.?
Who is currently “rocking” a Teams site like no one else. What are some ideas and best practices for a 3000+ person org that can help us make the right decisions in this area?