Best practices & tips for working in a Teams Environment

Note: The term 'Teams' is used multiple times throughout this blog post, in multiple ways, so just to clarify:

• 'Teams' refers to the Teams app.
• 'team/teams' refer to a bunch of people working together.
• 'Teams Owner' refers to the owner of the Teams Environment, and is responsible for all the ins and outs of that Teams Environment.
• 'Teams Chat' refers to the one on one/few chat functionality in Teams.
• 'Teams Environment' refers to the Teams Environment you have for collaboration with your team members.

Channel structure

For most of the Teams related things we can create some sort of 'best practice', however, how you should structure your Teams Environment with channels is almost impossible to put in a best practice. Why? Well, because every Teams Environment is created for a specific purpose, with a specific set of people, all with different needs.

Should you put everything in the 'General' channel?, or should you create (lots) of different channels? In the end, there is no right or wrong here, it all depends..

If the tasks you are going to do within your environment can be easily split up in different topics, then the logical step would be to create separate channels for these topics, to keep discussions focused on a (channel) topic, and not having all kinds of different discussion topics being discussed in one channel.

The size of your team also plays a big part in how you should organize things. In the case of a small team, it might be easier to just start with the general channel and go (and grow) from there.

However, in larger teams, it might be better to 'design' a good channel structure first, either alone, or with the help of one or two team members. Preferably do this before the other team members are added to the Teams Environment. This way you can first work on creating channels, create a set of working rules on how you want everybody to work in this environment, make changes where needed, etc.

When everything is set up, have a meeting with everybody that will be involved in the Teams Environment, to make sure everybody knows how the work will be organized, what the 'rules' are, etc.

Just adding people to a Teams Environment without telling them anything beforehand is usually counter-productive!

As you can see in the screenshot below, I've created a channel structure for a Teams Environment of a big department that has multiple teams. Each of the teams within that department will have a separate channel within that Teams Environment. By using separate channels for those teams the information is separated between teams so a member can easily find the information he needs. But as all teams are working in one Teams Environment, all information within those teams is also available to the whole department, which improves the collaboration between those teams.

You'll notice that next to the Management channel a lock symbol is shown. This signifies that this channel is a 'private' channel, which means that unlike regular channels to which all team members have access, only a subset of users (in this case, only the managers) have access to this channel.

In the past, all channels were open to everybody, and if some discussions and documents would need to be 'shielded' from other members, then the only solutions were to do these talks and files sharing through a Teams Chat, or request yet another Teams Environment just for this purpose. With private channels, you can now easily create a channel that is only available to a few members within that team. Team members that are not a member of a private channel will not even see the private channel(s) in their overview.

Working rules

Every newly created Teams Environment should have a 'Working in Teams' tab in the 'General' channel, this tab should have some basic rules and information about working in Teams. Matt Wade has created an excellent 'Definitive Guide to Everyday Etiquette in Microsoft teams' document ( https://jum.to/TeamsEtiquette) which has a lot of information that you can use for creating your own working rules.

One of the responsibilities of a Teams Owner is to make sure everybody is on the same page in regards to the working rules within that Teams Environment, so at least make the rules you intend to set for your Teams Environment known to the others members, and also to 'uphold' those rules (like for example addressing people that are constantly posting replies as new topics instead of an actual reply).

For larger teams, I would advise creating a set of working rules specifically for that Team. As all teams are different, teams might decide on other rules than other teams, so having a document that states how everybody should be organized in this specific team can be very helpful.

These working rules can be created in multiple ways, you can just create a Word document or OneNote or even a SharePoint page, within the Teams environment with the information that you display in a tab in the General channel.

Let's create a Word document with our rules. It might be handy to include some (or all) of the basic rules so that your team members don't have to look in multiple pages or documents.

To create a new Word document go to the Files tab of the General channel, click on '+ New / Word document', and name your document (for example 'Working Rules'.

After putting all of the rules for your environment into the document save/close it. This document can then be added a tab in the general, this way the information is easily available to everybody.

In the General channel click on the '+' sign and click on 'Word', next enter a name for the tab (for example 'Working Rules', select the document and click on 'Save'.

Adding tabs to channels

Having multiple channels within a Teams Environment enables you to create a focused work environment. Instead of having to switch between different applications and documents all day to do your work, it might be more efficient to unlock these applications and/or document directly from within Teams.

For example:

The Operations team uses the following applications and documents:

• Monitoring website to monitor the infrastructure
• Excel document for keeping a changelog
• Planner application to create and monitor tasks

The Marketing team uses these applications and documents:

• Planner application to keep a team-wide 'to-do' list
• Web browser link to the company intranet for posting news items
• Power BI dashboard for reporting purposes

All of these applications and documents can be easily added as tabs in the Operations and Marketing channel, in the same way, we added the 'Working Rules' document to the General channel.

For example, to create the team-wide 'to-do' list in the Marketing channel, click on the '+' sign and click on 'Planner'. Next, enter a name for the new Planner plan, and click on save.

When tabs have been created for all of the applications mentioned above, a team member would only need to use the Teams application do work on all related tasks, without searching for information, starting other applications, etc.

Make use of OneNote in Teams

OneNote is one of those applications that can be used for just about any purpose. Do you want an easy way to centrally store meeting notes (instead of having meeting notes in a meeting appointment as discussed in the previous Teams meetings blog post), or do you need an application to transform handwritten notes you wrote using your tablet's screen and pen to 'digital' notes? Then OneNote is the application to use.

OneNote can also be used by multiple persons at the same time. So for example, instead of having one person making notes during a meeting, all attendees could add their notes simultaneously during the meeting.

Let's say the Planning department has a weekly meeting, and they would like to have all their weekly meeting notes in a central location. For this, we click on the '+' symbol in the Planning channel and click on 'OneNote, then click on '+ Create New Notebook', give the notebook a name ('Planning Meeting Notes') and press save to create the notebook.

Make use of the SharePoint site of a Teams Environment (or don't!)

Every Teams Environment also has its own SharePoint site. Documents that are stored in Teams are actually stored in a document library of that SharePoint site.

To work in Teams, and to work with files there is no real need to make use of the SharePoint side of things, however, there are scenarios were using SharePoint can make your Teams Environment even better.

For example, the SharePoint site can be used for creating documentation in a modern style, using SharePoint you can create web pages with text, images, data from other sources (e.g. an excel view), which are easily editable. These pages can then be brought into Teams by adding them as tabs.

So, how do you create a SharePoint page in your Teams Environment?

Go to a channel within your Teams Environment (any will do), click on the '...' item in the top right corner and click on 'Open in SharePoint'. Next, click on 'Home' in the left menu.

When you click on 'Home' you will be redirected to the homepage of the SharePoint site of your Teams Environment. This homepage looks a lot look an intranet site, it has a new item block, quick links, and it displays the document library where all the Teams files are stored. Every channel you create in your Teams Environment will get a separate folder within that document library.

You can now add information to the page, in this example I'm creating an introduction page for the team, where I use the 'People' web-part to show all the team members, with some additional information. I could add more information to this page, like the purpose of the environment, etc.

When the design of the page is finished, publish it.

Next, we want to add a tab to the General channel so that all members can easily find the information. So head back to the Teams Environment, select the General channel, click on the '+' button, and select 'SharePoint' as the tab type. A list of the available pages of the SharePoint site is displayed, and you can select the created 'Introduction' page. After clicking 'Save' the SharePoint page is then shown as a tab in your Teams Environment.

SharePoint pages like this can be used for just about any kind of information, can be easily created and edited, offer a lot of functionality, and look a lot better than a Word document.

So you can use the SharePoint portion of your Teams Environment to make better informative pages, or you can use it as a 'publishing' location for 'final' documents.

Keep in mind though that the SharePoint site of a Teams Environment is only accessible to the team members, if others need to access the published information, then that information should be placed on a 'regular' SharePoint site, and NOT on a Teams Environments SharePoint site.

Files, Files, Files

Currently, our files live just about anywhere, in your home directory, on (multiple) file shares, on your laptop (although I hope not!), on your OneDrive for business, on (multiple) SharePoint sites, and in (multiple) Teams Environments.

And these are just the 'business' file locations. Before we had OneDrive a lot of business data was also floating around in personal storage locations, like OneDrive (personal), Google Drive and Dropbox.

So how and where should we arrange our data?

As working in the cloud enables us to do our work from any place, at any time, and on any device, it is only logical that all of our data should also be stored in the cloud. Working on your Centric laptop works fine with data still stored on an on-premises file server, but how about when you are on the go and need to fix a document with only your smartphone? If the file is stored in a cloud location then that's no problem, but when the file is stored on an on-premises file server, you probably need to call a co-worker (with a Centric laptop) to fix that document as you can't access the file from your phone.

Okay, so everything should be stored in the cloud... But where?

• Business documents should NEVER be stored on personal cloud storage like Google Drive, DropBox or OneDrive (Personal).
• Personal business documents (previously stored on your on-premises home directory) should be moved to your OneDrive for Business.
• Files from your department on-premises file share should be moved to your department Teams Environment.
• Files stored on a department on-premises SharePoint site should be moved to your department Teams Environment.

This sounds easy enough, right? Unfortunately, there are a bunch of exceptions that is making things a lot more complex.

For example, if a team is creating documents for publication to a broader public (other departments, or the whole of Centric), then these documents can't/shouldn't really live in a Teams Environment, as there aren't Teams Environments that are that broad.

In these situations, these (final version) documents should either be posted on the department's intranet site or on a separate SharePoint Online site if the information is meant for a specific target audience.

The document lifecycle

Not only the previous location of a file dictate where the file should be stored, but the status of a document is also relevant here.

• When working on a draft version of a document on your own, you can store the file on your OneDrive for Business (although you can of course also just start with the draft version in your Teams Environment).
• If you want to collaborate with another person on that document, you can share it with that person from your OneDrive for Business.
• If you want to share the document with your team, move the file to the Teams Environment of that team.
• If the document has reached a final status and needs to be shared with people outside of your team, then move the file to either your Intranet site or to a separate SharePoint Online site to which these people have access.

So in short, your Teams Environment is your 'work environment' where you work on documents, Intranet and SharePoint Online sites are 'publication platforms'.

Version history

Another aspect of working with files is versioning. A lot of people are still used to making copies of files and adding a 'V1', 'V2' or 'DRAFT' to the name, and in the end, numerous versions of the same document are floating around.

Every file that is stored in a Teams Environment (and on SharePoint and OneDrive) has automatic versioning. That means that all changes to a document are logged (including the user that made the changes), and you can easily look back into a previous version, or even revert to an older version (thus making an older version the current version).

To see previous versions of the document open that document in Teams, next, click on 'Files / Info / Version History'. On the right-hand side all the previous versions are shown, and clicking on one of them will open that particular version of the document.

Connecting other applications to Teams

Even though all of your applications and documents can now be easily accessed directly from within Teams, you still need to go to a specific tab to see if something has changed. Wouldn't it be easier if you were to receive a notification when something happens?

As Teams is meant to function as a 'hub' for your daily work as much as possible, you can also easily 'connect' with other apps. This enables you and your team to receive notifications if anything is updated in that other application.

For example, you can connect to an (online or on-premises) Azure DevOps environment and have notifications sent about activities in your projects to your Teams Environment.

Or you can connect to Yammer to receive a notification in your Teams Environment when a new post has been created in a selected public Yammer group.

You can also connect to 3rd party apps, but keep in mind that Teams only makes the connection possible, it does not mean you are automatically licensed for these applications.

To add a connector to a channel, click on the '...' next to the channel name and click on 'Connectors. Next, select the application you want to connect, in this example, we will be connecting 'Azure DevOps'. Click on 'Add' to add the connector to the channel.

Next, you need to configure the connection, like choosing the project you want to receive notifications for, the team and the event type. After saving the settings the connection is made, and whenever something is updated within the Azure DevOps environment, a notification is sent to the channel.

You can also add your Azure DevOps Kanban board or dashboard to Teams by adding this as a tab to the channel.

Certain connectors also have additional functionalities, for example, the Azure DevOps connector enables you to search for work items and use them in discussion topics.

Use Emoji in your Teams Environment

By pressing the Windows key + '.' (the punctuation mark) in any text field, a window that enables you to select an Emoji is opened. These emoji can also be used in Teams channel names for different purposes:

• Adding an emoji to a channel name makes it more distinctive
• Adding an emoji to channel names makes it look more 'fun' 😁
• Emoji in channel names can 'group' channels together (because they can influence the sorting)

After adding an emoji to the Teams channels, you end up with something like the following. As you can see the emoji for the 'Planning' and 'Marketing' channel has altered the sorting of the channels. This can be useful in larger Teams Environment where you can use that sorting to group certain channels together.