How to manage communications across >100s of individual projects under 1 team?

Question

Has anybody implemented practical solutions within their organization for not only organizing communications across 100s of projects, but also encouraging folks to use whatever structure you have in place?

 

These aren't necessarily large projects, but we (a) don't want to create a new Team for every single one, and (b) having 100+ channels in a Team is unruly and also will hit the channel limit.

 

For context: we have a Team and associated well-built out SharePoint Online site for a large program/contract within my company, but there are 100s of individual projects managed under this program/contract. We want to organize communications to be project specific to alleviate disparate email traffic and stop random text chains and 3rd party group chats that staff take upon themselves.

 

Has anybody come up with any reasonable processes for this within the Teams/Microsoft platform, or is this ultimately a people problem?

Answer 1

Hi @Cascarano, Ryan

As far as I know, users can create 250 teams, global admins can create 500,000 teams, and each team can create 200 channels.

According to your description, we recommend that you divide into different teams or channels according to the different attributes of the project, and even add some tags to better manage the project. Microsoft provides some articles on organizing large teams that you can refer to:

Best practices for organizing teams in Microsoft Teams

Manage large teams in Microsoft Teams - Best practices.

Manage tags in Microsoft Teams

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

---