Wish to optimize the way your organization works remotely? Join our approaching web seminar “7 Ideas to Improve Remote Work and Ditch Content Sprawl with Microsoft Teams.” Register here!
Microsoft Teams is formally 3 years old this month. This chat-based application is responsible for a whirlwind of change since its release. Companies, including my very own, have accepted it as being a platform for internal and project-focused communication and document organization. There’s, however, some confusion regarding exactly how it ought to squeeze into our corporate intranets.
There’s two prominent misconceptions regarding Teams which i hear frequently on client calls and visits:
- It’s a secure-to the intranet where individuals chat and goof off a distraction and never an essential offering for that business.
- You just need Teams. Forget SharePoint. Just Teams. Only Teams.
Both views are extreme, and I’ve discovered that, out of the box so frequently the situation because of so many things, the reality lies somewhere in the centre. Microsoft Teams enhances our typically document- and news-centric intranet. It’s being positioned by Microsoft is the service application delivery platform for that organization. When leveraged correctly with thought and planning, it might be a centralized hub for working together.
Since it’s name suggests, Teams shines when positioned to boost working together! It isn’t designed or meant to replace SharePoint. Every item distributed to a group through the Files tab in Teams truly resides in a corresponding SharePoint document library (Shared Documents). Actually, the Files tab in Teams is simply an interface in to the connected SharePoint team site’s Documents library.
Instead of as being a substitute for SharePoint, Microsoft Teams is definitely an enhancement. When we disregard the document management functionality of SharePoint and try to change it with Files in Teams, we’ll soon find inside us a folder-filled, deeply nested structure which will soon represent the file share a lot of organizations moved from once they adopted SharePoint!
SharePoint document libraries. Build the SharePoint sites when needed for departments, functional areas, and project groups. Utilize additional libraries and lists for document management and organization. Create alerts, flows, custom metadata and views. Then tab to individuals lists and libraries within the appropriate Teams funnel.
The main objective of Team channels would be to provide some organization for conversations and content. By structuring our Teams based on the work patterns of those within the team, may well structure starts to unfold.
Within my example, I’ve built a group depending on how we at PAIT Group use Microsoft Teams for projects. Every client will get a group, and every project will get a funnel. It appears something similar to this:
Each funnel must have tabs that offer important sources for your internal audience. For instance, the dev team might mainly operate in the Onboarding Flow, Power Application Build, and Design Automation channels.
As you can tell below, tabs happen to be put into allow the dev team to get at the shape and client site in which the onboarding flow has been developed.
We typically suggest that the Documents library remain alone, around the SharePoint aspect. Let Teams purchased it and make other libraries when needed for document management. Otherwise, site people might start to upload content in to the library although not inside a Teams-connected folder, thus rendering that content inaccessible from Microsoft Teams.
By itself, Teams has great meeting and live event abilities, streamlines communication, and may provide us with quick access to Microsoft and third-party applications. But to really release the entire potential of collaboration, remember SharePoint. They really be more effective Together!