MS Teams: How we use it and what we think about it

Microsoft Teams is the most recent tool of Microsoft to support teams. If you haven’t heard of it yet, please visit SuccessWithTeams for a first impression and much more information or for an interactive demo. We are working with Teams since it was available in our tenant of the Office Cloud. I would like to share with you our first experiences.

Client tool and apps

In summary, MS Teams is a must-use tool for all cloud users and I don’t say that just because we are MS Partner. In the last months and years, Microsoft surprised us with a lot of new features and tools like Groups or Planner. But Teams is different: It is not just one more new tool. We see it as a central hub for communicating that brings together the different components of Office 365.

If you read my following comments to that new tool, you should know that we are using SharePoint for many many years now. Therefore our focus in evaluating Teams lays on how we can extend or improve the use of SharePoint or just use it as front end for SharePoint functions.

Teams and channels

One advantage is the client tool. Maybe I am too old, but sometimes I get lost in my browser -with all the open tabs. The tool is easy to understand and navigation is intuitive. It feels as if I work much faster than with SharePoint sites directly in the browser. And using the drag&drop function it is so easy to share my documents with the teams. The best is I can switch between different teams and channels very fast - much faster than using my favorites or open tabs in my browser.

Nevertheless you can use teams also directly in your browser, the desktop app or with the help of apps on your smartphone.

If you start using Teams you create a team (room) or join an existing one. For each team you can administrate the team members and their permissions (roles). For sub projects, topics or special task you can create channels. The channel concept is important because it gives you the ability to structure content. For example you create a team for your marketing department and a channel for each of your marketing campaigns. All these tasks are much simpler, faster and clearer to do than directly in SharePoint.

Also, the navigation between different teams and channels is really fast and better than SharePoint-only use. Here I give a clear plus for Teams. The content in each channel is accessible in different tabs. Out of the box you get “Conversation” and “Files”, but you can add more tabs, e.g. for a Planner site.

Conversations (Chats)

Due to Slack and other chat tools of competitors I guess the chat function is the most important feature of Teams in the eyes of Microsoft at the moment. In comparison to a SharePoint only site this is a clear enrichment for project work. I really like this chat. Our project specific Yammer groups can be replaced by this conversation. You can start a conversation with a subject title, which you cannot do in Yammer. I cannot say why, but for me it is also easier to recognize new messages. As in all chat tools the challenge is to give them a structure. Therefore we have some simple rules. In a project with concurring meetings for example we start a new conversation for each meeting with a small protocol. All messages concerning to topics of this meeting must be sent as replies and not as new conversation. This is why the subject title is so important for us. Chat function is a clear plus for teams. You can also add bots, but we haven’t tested it yet. But we will.


In the Files tab you can store documents and create folders. Using drag&drop, this is very simple. You can also send emails to a channel and these emails will be stored in a special folder. In the background, all these documents are stored in a SharePoint site, which you can access directly, if you want. However, I didn’t detect a way to add meta data to the documents yet.

Therefore, I a give a plus for easy handling but a minus for missing meta data. Even the most users will not miss the meta data, in some cases there are very helpful and more powerful than folders.

SharePoint integration

In the same way we really miss a better integration of SharePoint lists, such as links, contacts or tasks. Of course you can create such a list directly in SharePoint and then add a website tab in Teams showing that list, but this is not really a good integration in a tool. I am hopeful this feature will be improved in one of the upcoming releases. This is a first version and it would be sad, if it doesn’t leave wishes for the future.

Much harder to understand is why Microsoft doesn’t use subsites. It would be so easy to create a subsite for each channel. As long as you only use conversations and files it is not a problem. However as soon as you start using a lot of SharePoint list you can see the problem. For example: You have ten channels and each has 3 list, then you already have 30 lists in your SharePoint root (or top level site). I am afraid this could become an architectural problem for the future.

One big challenge

As I already wrote, Teams really convinced me and I also think more cool features will come up with it. Nevertheless one big question is not yet answered. How can a big company manage all these teams. Imagine a company with 50,000 employees. All of them join teams then you get thousands and thousands of teams. The projects will end or the organizational team will be reorganized and will no longer exist, then you will get “team rooms” without active members and no one will know what to do with the content or find it again. Of course a good search engine can help here, but we learned that a search engine cannot replace a good structure and a future-proof process.

We had and still have the same problem in pure SharePoint. For that reason we worked out different solution for this problem together with our customers, starting with a global site directory up to individual project cockpits using subsites. At the moment it is the biggest challenge for our customers to identify rules, e.g. who can create teams and how to manage existing and “finished” teams.

What we use it for

We started our evaluation with typical projects for managing software development projects. Usually we were using a SharePoint site or a subsite and a Yammer group. The task management is in TFS (Team Foundation Server), so we don’t need a lot of additional list for bug tracking or feature description and so on. For these kinds of projects our test was really very successful and the Yammer groups are no longer needed for these projects. But we still use Yammer for companywide messages.

We also have a kind of resources sites in SharePoint. For example, for Microsoft technologies, where we collect interesting links or documents to a Microsoft product. We made first successful tests here with Teams. In these cases we use the conversation as a team blog. If someone finds interesting information or a document, he will upload the document and send a message in chat like a comment to the information. This is what you may know as a “What’s new” in SharePoint.

We have some projects with several subsites because of permissions or because of several lists for each subsite. Before we test these kinds of projects we still wait for next versions of Teams hoping the list integration will be improved.

The future viability

If you “roll out” a new tool in your organization, you have to ask if this software will be up to date in the next years. We think this tool is important for Microsoft. Following the news stream I got the impression Microsoft is still working hard on this software. I am convinced MS Teams will still be important in a few years.

Some say MS Teams was born as competitor to Slack, but we think it is much more. Of course it looks similar at first glance and you can chat and work with channels. The big advantage of Teams is that it is empowered by the Office 365 Cloud and all available tools there in one portal.

As next steps, we’ll find out more about the bots, apps and connectors, you can add to your team or channel. I’ll keep you in the loop.