MicrosoftNogaRonenRoshin Ramesanthis piece leads with "allowing you to organize information and communicate your way."
But in reality you're making everyone do it your way.
The use cases developed and on which this change are based - DO NOT suit the way many customers use TEAMS. As pointed out may users of TEAMS are several years behind the product development in terms of how they understand the elements of a TEAMS team.
Up until this change Chat and Channel posts were separate things, used in different ways, for different purposes with different names, but similar functionality. The new chat and channel experience blows up most user's mental model of the system. I'm sure you have many customers, probably high speed software development teams (like your selves) that will love this change because it is more like other products they are used to. The reality is that they are only SOME of your customers, and everyone is a truly poor representative of their customer's user cases.
I know you are great at your jobs and do care about what you're doing, but PLEASE please, EVERY change like this burns social capital for people who are seen as the Microsoft person in their organisation. THERE must be a better way to allow people to move at a pace that suits their own userbase .....
"The new chat and channel experience blows up most user's mental model of the system." I'm in total agreement with you on this Dorje-McKinnon ... I've spent the last few years training people on why using Channels is more effective for deep work rather than Group Chat... Interestingly, many people were not that familiar with Channels, but after they're shown, they agree it is more effective than a long continuous stream of Chat.
Having them separate helped make the transition easier in my opinion....combining them really doesn't seem like a good idea!
