Just like parent stating "usable? yes", I too find it usable at best. Coming from a history of using Discord and Slack, where Discord was mostly "less formal Slack without all the utilities, but with voice chat", I find Teams to fall into an uncanny valley.
The focus on video conferences might be the most annoying part. Most of the time, I just want to see the shared screen at best. There's an option to stop incoming video, though this one isn't on by default. There also flat-out isn't a way to stop looking at your own face when sharing video.
Meetings with Teams links tend to inflate the history, dozens of chats that could've been one thing now cause dumb questions like "should we stay here or go into the other call?". This was already solved by apps like Teamspeak more than a decade ago. It feels immensely clunky, but the culture also doesn't provide an intuitive way to avoid this problem.
The last bit highlights my biggest problem. It's mostly culture. It feels as restrictive as your average enterprise program, yet it also feels chaotic in all the wrong ways. Many problems have already been solved and plenty of cultures, like global social gaming, have already experienced ways to handle this. Had I not had any experience with other apps, I likely wouldn't feel this way.
I also realize part of the problem is how Teams is configured, which I have no experience with. But then it once again boils down to "here you have this tool that can do a lot, but it's not intuitive and we don't give you a lot of guidelines" despite the fact most companies have zero experience with remote.
The focus on video conferences might be the most annoying part. Most of the time, I just want to see the shared screen at best. There's an option to stop incoming video, though this one isn't on by default. There also flat-out isn't a way to stop looking at your own face when sharing video.
Meetings with Teams links tend to inflate the history, dozens of chats that could've been one thing now cause dumb questions like "should we stay here or go into the other call?". This was already solved by apps like Teamspeak more than a decade ago. It feels immensely clunky, but the culture also doesn't provide an intuitive way to avoid this problem.
The last bit highlights my biggest problem. It's mostly culture. It feels as restrictive as your average enterprise program, yet it also feels chaotic in all the wrong ways. Many problems have already been solved and plenty of cultures, like global social gaming, have already experienced ways to handle this. Had I not had any experience with other apps, I likely wouldn't feel this way.
I also realize part of the problem is how Teams is configured, which I have no experience with. But then it once again boils down to "here you have this tool that can do a lot, but it's not intuitive and we don't give you a lot of guidelines" despite the fact most companies have zero experience with remote.