The "negative" you mentioned about using Teams Files is unstructured Sharepoint sites. However, their advantage is assist in solving a variety of issues that are common to virtual teams (shared channels). You don't experience new members to the channel not having access to some files because they aren't normally part of the organisational team that owns the Sharepoint structure. (Yes access can be managed, some don't do it well) Also getting access to a huge Sharepoint fileshare when you only need to collaborate on a half dozen files, each from somewhere deep in the path, which you can't remember. The above is a topic you may consider doing content for. If you want to retain your files in a formal SharePoint structure as you suggest, How do you pull the small number of resources into a shared channel so that a cross-discipline team can form, and collaborate for a month or two on a project. Then disband. Leaving behind some updated docs in Sharepoint where they should be. While at the same time, the team experienced the convenience of the streamlined Teams Files where they had handy access to only the resources they were frequently using.
Thanks very much for your detailed input David. The issue is more IT allowing 'end users' to create their own Teams and SharePoint sites, and not properly training them on how to use these tools, and when to save files in different places. I see it constantly, and people end up doing their own thing because of all the confusion and being overwhelmed by all the different Teams and sites that people have created. Using Teams for SharePoint files is only a negative when it has not been properly thought out. Sharing casual files over Teams in unstructured SharePoint sites is OK and by design. Sharing project files when the Team has been set up as a project Team is OK, if the company has decided that's how projects will be run. The key is the business deciding how these different tools will be used to meet their requirements, with the proper advice, being consistent, and then setting everything up with the correct permissions (as you point out, another area that people struggle with), and limiting who can create Teams and SharePoint sites so you don't end up with unorganised chaos. One of the most important and most overlooked issues is training end users on how to use these tools and where to save documents. If the leadership have not decided how to use the tools, the rest of the company has no hope. It's always helpful to establish SharePoint 'champions' in the leadership team to help ensure everything is filed properly. Great idea for another video. There is so much more to explore on this topic. Permissions and sharing across different business units and external users is another thing people find challenging. Thanks for watching!
![Are you STILL confused? Sharepoint vs. OneDrive vs. Teams - [2024]](http://i.ytimg.com/vi/sd5DKYZYtjY/mqdefault.jpg)
The "negative" you mentioned about using Teams Files is unstructured Sharepoint sites. However, their advantage is assist in solving a variety of issues that are common to virtual teams (shared channels).
You don't experience new members to the channel not having access to some files because they aren't normally part of the organisational team that owns the Sharepoint structure. (Yes access can be managed, some don't do it well)
Also getting access to a huge Sharepoint fileshare when you only need to collaborate on a half dozen files, each from somewhere deep in the path, which you can't remember.
The above is a topic you may consider doing content for. If you want to retain your files in a formal SharePoint structure as you suggest, How do you pull the small number of resources into a shared channel so that a cross-discipline team can form, and collaborate for a month or two on a project. Then disband. Leaving behind some updated docs in Sharepoint where they should be. While at the same time, the team experienced the convenience of the streamlined Teams Files where they had handy access to only the resources they were frequently using.
Thanks very much for your detailed input David. The issue is more IT allowing 'end users' to create their own Teams and SharePoint sites, and not properly training them on how to use these tools, and when to save files in different places. I see it constantly, and people end up doing their own thing because of all the confusion and being overwhelmed by all the different Teams and sites that people have created.
Using Teams for SharePoint files is only a negative when it has not been properly thought out. Sharing casual files over Teams in unstructured SharePoint sites is OK and by design. Sharing project files when the Team has been set up as a project Team is OK, if the company has decided that's how projects will be run. The key is the business deciding how these different tools will be used to meet their requirements, with the proper advice, being consistent, and then setting everything up with the correct permissions (as you point out, another area that people struggle with), and limiting who can create Teams and SharePoint sites so you don't end up with unorganised chaos. One of the most important and most overlooked issues is training end users on how to use these tools and where to save documents. If the leadership have not decided how to use the tools, the rest of the company has no hope. It's always helpful to establish SharePoint 'champions' in the leadership team to help ensure everything is filed properly.
Great idea for another video. There is so much more to explore on this topic. Permissions and sharing across different business units and external users is another thing people find challenging.
Thanks for watching!