{"id":4550,"date":"2019-02-09T12:41:14","date_gmt":"2019-02-09T17:41:14","guid":{"rendered":"http:\/\/lisa.rushworth.us\/?p=4550"},"modified":"2019-02-04T12:59:16","modified_gmt":"2019-02-04T17:59:16","slug":"do-you-know-if-you-should-create-a-new-team-or-new-channel","status":"publish","type":"post","link":"https:\/\/www.rushworth.us\/lisa\/?p=4550","title":{"rendered":"Do you know \u2026 if you should create a new Team or new Channel?"},"content":{"rendered":"

Do you know \u2026 if you should create a new Team or new Channel?<\/strong><\/p>\n

It\u2019s certainly a good idea to break topics into different locations in Microsoft Teams \u2013 cognitive research on how efficiently people multi-task<\/a> suggests this, it\u2019s easier for non-impacted individuals to ignore information that\u2019s not relevant to them if it\u2019s not interspersed with information they need<\/em>, and spreading topics out reduces the frequency of posts \u2013 ten new conversations don\u2019t appear while you\u2019re reading a thread. But should you create a new channel or a new Team?<\/p>\n

There are a few technical limitations that make \u201cTeam\u201d generally the right answer. Each channel in a Teams space has the same permissions<\/a> \u2013 if you want to restrict access to confidential information or if you want to involve additional people \u2013 people who don\u2019t need access to your other channels, you need to create a new Team.<\/p>\n

You can archive a Team<\/a>, but you cannot archive a channel<\/a>. If you create a new channel for every project, your Teams space can become cluttered with old projects. The channels get collapsed into a \u201cmore channels\u201d fly-out, but I still find myself renaming channels \u201czzSomething Or Other\u201d to get really <\/em>done projects sorted to the bottom of the more channels fly-out.<\/p>\n

You cannot move a channel into another Team<\/a>. If the project moves to another group (such transitions are common in IT \u2013 there\u2019s a development\/implementation phase, then the project moves to production support under a different group) \u2026 there\u2019s no way to transition the information in a channel to another group. Even if that\u2019s not standard operating procedure in your organization, reorgs happen. A supported system becomes big enough to warrant its own group or staff is re-aligned \u2013having the historic knowledge of the Teams discussion available to the new organization is beneficial. (Not to mention, if you could move a channel into another team, you could indirectly archive channels by moving<\/em> them into an archived Teams space!)<\/p>\n

There are<\/em> some scenarios where a new channel makes sense \u2013 that daily e-mail chain where people decide where to eat lunch could become a channel. There\u2019s no reason to move the historic restaurant selection to another group \u2013 or, for that matter, retain<\/em> it. If group lunches become \u2018not a thing\u2019 \u2013 just delete the channel. And anyone not<\/em> heading to lunch today can ignore the channel. Similarly, \u201cWater Cooler\u201d discussions \u2013 a place where the comradery we took for granted when sitting in the same physical space can re-emerge \u2013 make sense as channels.<\/p>\n","protected":false},"excerpt":{"rendered":"

Do you know \u2026 if you should create a new Team or new Channel? It\u2019s certainly a good idea to break topics into different locations in Microsoft Teams \u2013 cognitive research on how efficiently people multi-task suggests this, it\u2019s easier for non-impacted individuals to ignore information that\u2019s not relevant to them if it\u2019s not interspersed …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[677],"tags":[675,691,729,666,686],"class_list":["post-4550","post","type-post","status-publish","format-standard","hentry","category-office-365","tag-did-you-know","tag-microsoft-office","tag-microsoft-office-365","tag-microsoft-teams","tag-ms-teams"],"_links":{"self":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts\/4550","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4550"}],"version-history":[{"count":1,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts\/4550\/revisions"}],"predecessor-version":[{"id":4554,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts\/4550\/revisions\/4554"}],"wp:attachment":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4550"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4550"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4550"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}