| > What specifically are teh workflow issues people have with teams? 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. |
Many companies auto-lock desktops after a few minutes of inactivity. If I go to chat to someone away from my desk, I definitely want Teams to make noises if somebody is phoning me - especially since I no longer have a desk phone.