One position that will reliably get many people to enthusiastically agree is: “I absolutely hate Microsoft Teams, it is awful to use”. What is it about Microsoft Teams that prompts this reaction?

At several of my jobs over the years, the organisation mandated use of Microsoft Teams for status indicator, text chat, video+audio call, remote presentation; later, even polls and bots connected to other systems used.

From my experience, all of that worked fairly reliably, and still does today, even better than many other similar systems I’ve used over the years. Network outages or downtime of internal hosts of course disrupted this, but I can’t see people picking Microsoft Teams to rage at for this.

I have my own reasons to hate Microsoft as an organisation and to avoid its software and platform offerings. But my experience of this software in particular isn’t part of that, and it doesn’t spring to mind as software I dislike using.

And yes, when in an organisation that oppresses its workers with unreasonable expectations of presence, or response time to messages, or cameras-on for meeting participants, that can be terrible and needlessly oppressive. Again, though, that’s not something I’d blame on the communication platform.

So I’m left wondering whether people have wildly worse experience with specifically the Microsoft Teams communication platform, or user interface, or something like that, which doesn’t match mine?

What is it people experience that makes them so particularly hate Microsoft Teams?

  • owenfromcanada@lemmy.ca
    link
    fedilink
    English
    arrow-up
    22
    ·
    4 days ago

    The app itself feels bloated and slow. Feels a bit like an electron app. And overriding the system window decorations makes it more difficult to use. The core function of the app is sending and receiving text messages. Barring networking issues, this isn’t something that should ever feel slow.

    Despite how many times I tell Teams to open word/excel/powerpoint documents in their native apps by default, Teams ultimately decides after a few months to switch back to using the awful embedded webview garbage that MS has been trying to push for years.

    If I have a conversation open, and someone sends a message, it leaves the conversation as unread. I can click in that window all I want, but apparently Teams is dead set on keeping that conversation marked unread. After I’ve read it. I have to switch to another conversation and back again to clear it.

    The developers like to change things. Recently they decided to combine the conversation and group tabs (fortunately in this case, they gave an option to keep them separate). If an application is constantly changing things that don’t need to be changed, it means one of two things: either the UX is garbage and they can’t seem to fix it, or the devs are changing things for the sake of constantly “modernizing” for the sake of its appearance for the stock market. In either case, it’s a red flag. A good application UX doesn’t change constantly, because change throws off peoples’ workflows. If you’re going to introduce a change, it should be for a good reason, because every change introduces a challenge for your existing users.

    Overall, MS shows over and over again that they give zero shits about the users of their products.

    • QualifiedKitten@discuss.online
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 days ago

      If I have a conversation open, and someone sends a message, it leaves the conversation as unread. I can click in that window all I want, but apparently Teams is dead set on keeping that conversation marked unread. After I’ve read it. I have to switch to another conversation and back again to clear it.

      I was unemployed for quite a while, but I could swear it wasn’t always like that. Definitely been my experience currently though, and super annoying.