Hey guys, guess who’s back from maternity leave? Your favorite Teams PM, Suphatra! I’ve been back for a few weeks and catching up on where we’re at in Engineering.
Private channels is still actively in development, and I am hoping I’ll be given clearance to share with you some more details. What would be great is if you can post in this thread any specific questions you have about the feature, besides just an inquiry on the release date.
You can also email them to me at firstname.lastname@example.org, as well as any other concerns you might have.
It’s good to be back, and good to be posting on here again. I hope you are all doing well!
SuphatraRENÉ RODRIGUEZ supported this idea ·RENÉ RODRIGUEZ commented
The concept of O365 TEAMS is brilliant. However in practice, within a host of industry applications, it's not as user friendly as it simply should be. For example - the premise is collaboration. Great. However, within the manufacturing industries, interacting with customers is paramount to a successful relationship. It's awesome that you can invite external customers to a TEAM. However, it's not a good business practice to allow ALL communication to be shared with that customer. Hence, the ability to create a TEAM, then create private channels within that TEAM is absolutely critical - just because humans are humans. It's really quite simple. Do you even realize how enthusiasm wanes drastically when TEAMS is introduced and then that little caveat of "oh. so you know all members can see everything within a TEAM." This alone makes adoption of TEAMS extremely difficult for everyone.
Personally, I do not feel the breakdown of various TEAMS is necessary. But that's just my opinion within my experience in Financial, Manufacturing and Medical Industries I've helped migrate to O365. However, the ability to have private channels within a TEAM is paramount.
Just my thoughts.