Same in a 7 person company. Got voted down in favor of Teams because the "learning curve" of anything else wasn't worth their time. This despite the confusing and ridiculous UX of Teams.
> because the "learning curve" of anything else wasn't worth their time
As someone on the other side of the divide who hates these products, this is accurate. A non-standard product is a non-starter in most fields unless it has a killer advantage.
Teams is a non-standard product to me who has used various chat programs over the years. It does some things okay, but I still want to go back to lync (skype for business). The features I use are worse than competition, and there are features I don't use that are annoying.
> features I use are worse than competition, and there are features I don't use that are annoying
I hate Teams. I hate Meet. But they work with basically zero training. You have to pick your battles, and successful businesses choose theirs in core competencies.
I must be a fucking idiot then, because no amount of engaging with it ever got me past "what the fuck, where did everything go, why is that there, how do I do X, why did it do Y when I did Z?" One of the most confusing programs I've ever used. Up there with some very-painful-learning-curve video games (think: Paradox games)
You lost me at 'they work'. They don't. To the point that I'm boycotting Teams, any customers that force us to use Team can take a hike, I'm not going to spend the first half hour (or more) of every meeting with a new set of people to get them all organized and solve a myriad of audio/video/networking issues. Teams is the biggest pile of junk MS ever released. And don't get me started on the linux client.
Possible, but none that I have been repeatedly exposed to. I axed Microsoft out of my life when they started their anti linux crusade and I haven't looked back but people keep pushing Teams on others.
The whole interop situation around video conferencing is ridiculous, there ought to be a common protocol and a variety of clients around this protocol, instead we have this utterly dysfunctional situation where there are five different walled gardens, each of which has their own set of problems and compatibility issues.
There are lots of other chat programs that work with zero training as well. All that is really needed is auto-start and auto-login when the user logs into the OS. If your chat program has those two: someone will figure out how to use it and everyone else will see the pop-up when a message is sent and start using it. Slowly everyone will learn features as they need them.
