Microsoft Teams is a digital workspace. It tries to provide the functionality to replace what goes on in physical offices; people talking to each other, having meetings, working and sharing documents. It is useful for the shift towards remote working and matrix teams, but also important for enabling organisations to reconsider how they management knowledge as a competitive advantage.
Apart from the difficulty of the product being called ‘Teams’, and the headings that channels are grouped under are called ‘Teams’, and groups of people who work together are called teams, Microsoft Teams is actually a good product for moving an organisation towards using a digital workspace.
How teams use it depends very much on how IT configures the settings, but here are a few thoughts on using the usual functionality in Teams.
Channels consist of a stream of chronological posts, a file repository, and the ability to add other tabs for things like Planner.
The dominant thinking is that it’s better to set up fewer Teams with more Channels than having more Teams with fewer Channels. I think this should be considered in light of how an organisation structures itself as this advice includes the implicit understanding about how actual teams of people work together.
If established teams always work together on the same things, then fewer Teams (actually one Team per team) with more members and more channels, each about a particular project or work stream, makes sense as all members of the team have visibility of everything even if it isn’t directly related to them.
However, if lots of different people are involved in lots of different things, then more Teams (with however many channels is appropriate) seems to make sense as only those members involved in the work will be on that Team and so see what goes on in that Team.
Private channels are a way to achieve having fewer Teams with lots of Channels as the Team can include lots of members but those members will only see the Channels they are members of. However, as yet Private Channels don’t have the full functionality of open Channels.
Teams can be set to only allow logins from within the organisation’s domain (via Active Directory) or set to allow guest access. Clearly, allowing people who aren’t under contract or NDA access to potentially sensitive information is an organisational decision that requires careful consideration, but if well managed can provide teams with a single platform to work with internal colleagues and external partners, rather than using Teams internally and something else for external communication.
Posts in Channels are a key functionality in Teams (that’s why the Posts tab is first). But Posts are also the most confusing thing. It isn’t clear how they should be used, whether they should be used instead of Chat, etc. A couple of things to consider is that Posts have replies, Chats don’t, which helps to focus a Post on a topic and provides a suggestion of how to use Posts. Posts have persistence as they hold the contents over time, can be saved to person’s Saved list, have images and files attached, and mention people to trigger a notification, all of which makes them useful for holding discussions on particular topics.
Immersive reader and voice
Posts can be read in the immersive reader and the voice functionality speaks the text in a post out loud. Unfortunately, single posts have to be read separately rather than as a stream, which seems like it might be more useful, but its still good to see Microsoft thinking about accessibility and how to include voice in Teams in the future.
Chat offers persistent web messaging, which means that the history of your chats with someone is not lost as it is with Skype. As anyone in the organisation can chat with anyone else, Chat isn’t limited in the same way Teams and Channels are.
Chats have the same file repository capabilities as channels, so files that are added to the chat and so hosted in Teams are available to both (or all) participants.
Group chats are a quick and easy way to get people from different teams together to either discuss an immediate issue or to have ongoing contact with each other. It doesn’t rely on everyone being in the same Team, and is easier than creating a new Team for what is often
Group chat or posting in channels? This is an immediacy vs. persistence question. If being able to get people’s attention quickly is important then a Group Chat is probably the better solution. If making the information available over a longer period of time is more important then posting in the channel (and @-ing someone to get their attention) offers greater persistence.
If Group Chats could be added to a tab in a channel this either/or choice could be avoided, but this isn’t possible at the moment.
Meetings can be created in Teams, assigned to a channel, and added to your Outlook calendar. The meeting is available to join by anyone in the organisation, they don’t have to be invited. Notes can be taken during the meeting which become a tab in the channel, and can be used to record decisions from the meeting. The video and audio from a meeting can recorded.
Teams has VOIP calls to individuals and groups within the organisation (which replaces Skype). I expect Microsoft to add AI to calls in the future to transcribe the contents of the calls to add to the organisational knowledge that Microsoft will be able to surface.
Files added to Teams are stored on SharePoint and surfaced on the Teams interface. Similarly, if you also use OneDrive, but files added to OneDrive are usually in personal storage. Adding files into the Teams file repository removes any issues of availability if the owner leaves the organisation.
Other Microsoft Apps can be added to tabs in channels
Planner is one of the Microsoft apps that works well as a Tab in a Channel. If the team does work that changes status, has assignees, has deadlines, etc., then Planner is good tool that can include the information held in the Planner board within Teams rather than a separate external tool. Planner has lots of advantages over Trello for enterprise organisations, including licensing and security considerations, but more importantly for holding all of the organisations information within a single platform,
Organisations providing Teams as a product to use is one thing, people across the organisation adopting Teams and getting the best use out of it is something else. The difficulty around adoption will have multiple causes for any organisation but I think an important one is the education around the benefits, both in the short term for users and longer term for the organisation. The short term benefits for users are in the efficiencies that come from working in more collaborative ways, such as on single a document rather than multiple versions, and reliability of files stored in the cloud rather than on a device. The longer term benefits for the organisation are around making knowledge and information available to the whole organisation rather than being trapped in people’s laptops.
It’s not difficult to see the direction Microsoft is heading with their suite of products. They seem to be betting on the future of knowledge-organisations realising that how they manage information, knowledge and intellectual assets is an essential part of the organisation’s competitive advantage, and needing a platform that can enable and empower that. Having all of an organisations information and knowledge on a single platform, that can be surfaced in multiple ways, shared and worked on collaboratively, and analysed by the artificial intelligence of the future, will be vital for large enterprise organisations