Just Makes Teams The Default for Groups
I may be misunderstanding Teams, but I am wondering why this just isn't the Groups platform? It's the perfect setup for what Groups seemed to be when they first came out. A quick, easy, convenient place for collaboration with files, events/meetings, planner, and conversation. Just seems to "choppy" as "another place". Sharepoint/Team sites can be left separate in the case there is a need for that type of functionality. But, again,
I may be misunderstanding. Really like the interface and definitely see this replacing internal email all together. With the potential for email to become external communications mainly.
Brad
shared this idea
2 comments
-
Adam
commented
We are moving to Office 365 and explaining to our users Teams vs Groups is very difficult. It appears they do the same, but with different terminology. If Teams to no more than Groups why have the confusion of the two?
-
Tim
commented
I totally agree that the way Groups creates conversations and Teams creates Chats is confusing to most people and this seems to be a time where too many choices is counter productive. I'm sure there are technical reasons why the 2 area's work separately but to general users the 2 ways of communicating is very confusing (and then you have Yammer as well). Would it not be better to have one interface that is used for communications and the user chooses the level of privacy etc they want. The user should also be able to choose between email or chat all from one screen other wise its just confusing having to decide should I uses Groups conversation or Teams chat. I'm sure this is in the pipeline but can we have it sooner rather than later