| I'v read this thread and there are soo many rants on teams. What specifically are teh workflow issues people have with teams? My experience is that someone books an online meeting, i get a teams link. When the meeting comes I click the link, everyeone's face shows up, we have the meeting and then close teams. I've never had any issue with teams, not even once. What are the issues people have with teams because there are a lot of rants about teams but no specific issues are mentioned. As a meeting tool its perfect, its there, just works and then goes away. Are the rants directed to it as a chat app? or a company wide messaging app? Because I use teams4-5 times a week and cant' think of a single time its failed me or crashed or slowed down during a meeting. its the definition of a tool that just works and then goes away until I need it again. What is making everyone so angry at the tool? |
The "channels" and accompanying wiki/file store is simply sharepoint with a different web-ui -- and it inherits all the problems of original sharepoint, i.e., it is where documents go to die.
It fails miserably to recognize when the system is "locked" and to "STFU" with its bleeps/blurbs/rings for new IM's/phone calls/whatever else it decides to be noisy about. Locked system means "not at work" which should mean "no noises from you, ever".
If you first initiate a screen share with someone, you can not add in a voice call (thereby making the screen share rather less than useful in most instances). Yet, if you begin a voice call first, you can then add in a screen share and keep the voice call going.
It is an "electron" app, so it is the single biggest resource hog (second only to Win11 itself) on the system. It even manages to out-hog Google Chrome by about 50% or better, which given Chrome's legendary hogginess is a testament to MS's ability to produce bloated software.
Just about the only thing it does get right is holding meetings. Click the link, meeting widow opens, hold meeting, click "leave" when done.