This is gonna sound like a troll post but i assure you it is not.

I don’t have a coding background but I’ve used Teams in a lot of workplaces and really only encountered like 2 issues entirely.

Either I got seriously lucky or it was before enshittification.

Why do you yourself dislike it? Is it UI? Performance?

I should also say I use Teams for basic purposes like messaging and uploading files, I literally don’t touch anything else and performance hadn’t been an issue. (Likely because I’ve been given thicc-ass workstations in the past)

  • @[email protected]
    link
    fedilink
    52 days ago

    Why would I need training for a chat app ?
    I have (as many many others) have used other apps before with no training at all without issues. Teams requires it because its UX is atrocious

    • @[email protected]
      link
      fedilink
      English
      02 days ago

      Because it’s not a chat app. It’s a communications and collaboration platform. It has chat in it, but it also contains a significant amount of other functionality that you clearly aren’t even aware of.

      People don’t even know what they don’t know about this app.

      It’s like consider a full RV as a “car”, sure it can get you from a to b, but that’s not really it’s intended use case and you’re going to have a bad time if you’re trying to use it to drop your kids off at school every day. If you know how to drive a car, you’re probably still going to need extra training to both drive and use the features of the RV properly too.

      • @[email protected]
        link
        fedilink
        1
        edit-2
        2 days ago

        Except the entire use case for teams in our organization (and I’m sure many others) is basically just to chat and make calls. None of the extra stuff is useful to us.
        Also you can look at slack which would also be a communications/collaboration platform, and weirdly enough the UX is fine and usable without training. Just admit MS shat the bed and made some Frankenstein abomination that no one knows how to use correctly. It’s pretty typical of Microsoft (and apple too) to just deflect that the user is doing it wrong instead of admitting they could improve the experience.
        To add to your RV analogy, Microsoft is selling an RV to moms and dads that just want to drop their kids to school. Sure sometimes they go on vacation and the RV is nice, but it’s not what the user needs. It’s also exactly why users hate it, they are given a monster truck just to go to the shop. (Plus in the case of software, they could have it transform as needed. The communication part could look like a regular sedan, but instead you are forced into the RV format at all times)

        • @[email protected]
          link
          fedilink
          English
          02 days ago

          Slack and Teams are not the same, Slack is a communications app, not a collaboration app.

          I know how to use Teams properly, and I have entire departments (government, universities, etc) that I have trained to use it and they get mad every time their IT departments try to introduce a new product that Teams (and M365) already handle just fine.

          Mom and Dad didn’t do their fucking research before buying it and didn’t bother to read the fucking manual after they did buy it.

          Don’t tell me the average user is correct when I get called into help offices multiple times a year that are still using Excel sheets to manage their vacation requests, manage their tasks on a blackboard on the wall of the office (even though they’re half remote), build their HR forms in Adobe, and have network drives with 90,000 files in 20,000 folders where nobody can find anything all while already owning M365 licenses.

          People aren’t using Teams’ integrated collaboration features properly, and it’s not because they’re worse than their existing processes and they have some sort of magic ultra-efficient system already, it’s because they simply do not know how to use them properly.