Updated June 2023
Microsoft Teams has a relatively flat structure that provides little opportunity for the organization beyond the naming of the team. However, one of the ways you can help your workplace structure Teams is through the organization of channels.
Within Teams, channels are a way to separate and organize conversation and content into logical areas. We frequently put a lot of emphasis on information architecture in Office 365 using taxonomy, site structure and metadata but we should also be doing this for how we organize our channels within MS Teams. In this article, we are going to talk through MS Teams best practices for organizing channels, why it’s important and how you can organize tabs within Microsoft Teams channels to provide a consistent experience for users.
Download Now: Microsoft Teams Governance Planning
Channels are important for structuring content in MS Teams. Since Teams themselves are flat in structure with no ability to add additional metadata or nest teams, channels can provide structure in three main ways:
MS Teams Channels allow you to separate conversations around topic, process, or any way that you like. Since MS Teams doesn’t have the concept of hashtags yet, splitting conversations via channels provides a much-needed structure to the various conversations that you have within a Team.
Different types of teams will naturally have different ways of structuring channels as well. If you have a Team created around a well-defined process you might have your channels split up based on pre-defined stage gates or project process areas:
If you have a Team that discusses different topic areas, then it might make sense to have your channels based on different topic areas such as:
If you have a collaboration area within a department, you might split up your channels based on various works streams as seen below:
When creating a new channel, a new folder is created in the Shared Document library of the SharePoint site for that Team. This means that you have the ability to organize your content via channels if you want to. It also means that having a channel called Documents or Document Conversations is a bad idea. The launch of Private Channels will further impact this structure as it is likely that permissions will be applied to the folder that is part of that private channel.
With MS Teams, you can also show other content using Tabs. This content isn’t limited to Office 365 and can show external applications. Since this is available on a per-channel basis, you can customize the experience across your channels.
The naming of your channels is extremely important because at a glance this is what your users will see when they join a Team. To follow MS Teams best practices for naming channels, the first thing to do is to establish a naming convention. It can be frustrating for users if they are swapping between Teams and channels that are conceptually the same but are all named differently.
For example, having a channel that refers to Quality Assurance discussions can be represented as ‘Quality Assurance’, ‘QA’, ‘Testing’, ‘QA – Discussions’, and other ways. Having a convention reduces the cognitive load when users switch between Teams and it allows them to find the correct channel quickly and easily.
In MS Teams, you can configure tabs for each channel. Just like with your channels, you should think about how you name and position your tabs within each channel and across channels.
Most organizations are not using Microsoft 365 to its full potential.
Orchestry makes Microsoft 365 simple for all users.
Orchestry is an adoption and governance platform that allows End Users, Workspace Owners, IT admins and organizations to take full advantage of Microsoft 365.
To see Orchestry in action, request a demo and download our features sheet!