Skip Navigation

Why do you hate Teams/Why is Teams despised?

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)

204 comments
  • Compared to skype, irc, slack, xmpp, and any other chat/phone software I've used its unreliable spyware.

    Spyware in that it's used to force idle status used by middle managers to make assumptions about when and how you work.

    Unreliable in that it stops showing system tray message status when it updates without alert, using vdi/Bluetooth headsets are a crap shoot if audio will work or not, and destroys history by allowing corpo policy to remove messages after X days.

  • Real talk? Because it's forced on people at work and it's made by Microsoft. It certainly has its flaws but it's not the worst software in the world.

  • Teams for chat and video is generally OK but when managers start trying to do scheduling, task lists, and kanbans in it it becomes annoying in my experience. A software should have a definitive scope and not try to be an everything tool. If you want that interconnectivity then it's better to implement a standard which works with another tool that is designed for that purpose instead of tacking on a bunch of shit.

  • Microsoft doesn't ACTUALLY care about teams so it's a nonstop bad UX, then they try to fix it, then they go a different direction, and so on. To Microsoft, its an add on that they mostly use to keep people away from Slack. When they spend time on it, all they are doing is enough to keep people away from Slack.

    Its been like, what, 2 years there they've shipped a "new" client seperate from the existing client (at least on macOS)? People are constantly using the wrong one or switching when one breaks, and Microsoft constantly breaks the new one.

    On windows the existence of the built-in "Teams" App is constantly confusing when people are trying to sign into a work account, which requires a different client. This is because the "Teams" App in Windows is just a rebadged Skype.

    Before 2022 when I used it for some meetings (we used slack in our unit since we had some of our own budget, but the wider corp was on teams) it was a daily toss up as to whether video calls would work on macos or linux.

    Most of my frustrations come from having to develop some integrations with teams:

    1. Right now there's a massive bug for the templating language to render cards in the UI and Microsoft's answer has largely been a big shoulder shrug.
    2. There are several really easy ways an admin can break a custom integration via azure. Obviously an app-based integration is better, but it's also really common in b2b to have more ad-hoc setups to send some data to teams. Even better, lots of small/medium companies have been convinced that they don't need IT people to help them with their Azure configuration, so no one ever knows how to solve any problems they create (this also applies to email fwiw... Unbelievable how many small/medium O365 customers have very broken email servers)
    3. Microsoft's implementation of federation between O365 users is a mess of tiered settings, and figuring our if rhe issue is on the business side or your side is a sysiphean task. If you are in an org which doesn't have a domain hooked up to your setup (as in you use username@company.onmicrosoft.com) there is a very specific sign in page you have to use or it'll blow up on you. And it's not the generic sign in page you get when going to teams or O364's web site.

    Tl:dr; Teams is a hacked together mess of bubble gum and toothpicks masquerading as a chat app. Its a miracle ir works as well as it does for "normal" usage, but it's a joke compared to Slack in every other way and quickly becomes a nightmare if you are working on integrations with it.

  • Today, this morning:

    It wouldn't let me into my morning meeting, it glitched out with jumping ellipses. I quit the program then when I tried to relaunch it went into a cycle of starting then immediately crash. This went on for two minutes before I restarted the computer. After restarting the computer then relaunched Teams it proceeded to crash/start four times before loading so I can attend my meeting.

    This kind of stuff is habitual. I now set alarms five minutes before meetings so I have enough time to press a button.

  • Every day it fucks my login token. Takes a while to load, then shows me my DMs but with a little "login problem sign in again" at the top (WHILE LOOKING AT MY DMS)

    So I click sign in in the toast. It takes forever. I'm now 1 minute late for standup.

    I do not have to log in. I do not have to reauthenticate or MFA. I just click the button and it logs me in again.

    WHICH IT COULD HAVE JUST DONE ON PAGE LOAD FOR FUCKS SAKE.

    The behind the scenes logic must be atrocious.

  • Because it's run by Microsoft, which is now a Big Data player. They use Teams to "monetize" your company's data and train their AI on it without your company's consent. They use Teams to collect data on employees who don't have a choice because they need a job to put food on the table, like real name, photo and phone number.

    If you don't want to give any data to Microsoft, too bad: your employer forces it on you. Don't like it? Your only option is to resign. That's the most egregious aspect of Teams - and Office 365, and all business-oriented Microsoft data honeypots: they use employers to collect data on employees who don't have any say about it.

  • I think it's because it's work. Its hard to have any positive feelings toward a tool used primarily to talk to annoying coworkers and bosses. It doesn't matter how good it bad it is.

  • I don't know if I hate it but it's annoying how opening links inside Teams tends to open in Teams instead of the real expected app.

    It's like they want a whole OS inside of Teams.

    Besides that: slack just feels better and less clunky for text chats.

  • So, I really don't like Teams. What follows is basically an unedited stream-of-consciousness that came out of me after reading the question. I've reread it and now realize that it comes across as extremely angry and dramatic. I would not put Teams in the top 50 difficulties of my life, but I do not have much patience for incompetent software. I'm also just in a bad mood and decided to swing at Teams.

    Fuck Teams' stupid fucking pseudo-markdown WYSIWYG editor. Either be markdown or don't, you fucking useless cretinous moron! If you're going to automatically insert an interactive code block when I enter a triple-backtick, then you should god damned well do the same fucking thing when I paste in a fully formed code block. (edit here) I do not want to see triple backticks, a new line, my code in a stupid non-monospace font, and then another triple backticks. I wanted a code block which is why I indicated my intention for it to be rendered as one by using the triple fucking backticks that you recognize(end edit). This is just one example, and I feel like I'm taking crazy pills every time I use that piece of shit chatbox.

    I use Linux, which means I use Teams exclusively through the browser (they used to have an electron app for Linux but they got tired of dealing with it and deprecated it). I'd be fine with the browser thing were it not for the fact that when I type in the Teams URI, there's a 50/50 chance that I'll be sent to Teams V1 versus Teams V2. Like, why the fuck are you like this, Teams? I have clicked the god damned "take me to V2" button so many times! I think there's like, an option or something for it that I've also clicked. (edit here) I have cleared my cookies and browser data for Teams, I have completely nuked ~/.{config,cache}/google-chrome for Teams, I have installed Chrome Beta for Teams, and still the issue persists (end edit). I do not want to wait 30 fucking seconds for the V2 version of the page to load when I already waited 10-15 seconds. Don't get me started on how broken the "install this as an app" bullshit is, ugh fuck I hate it.

    Finally, Teams has been really great at not fucking reading my auth cookie recently. My company uses Okta for SSO, and like, fuck man, most shitty web apps seem to get it. My browser stores a JWT, it sends that shit in a cookie, some magic crypto shit happens, and boom I'm authorized. Teams is just fucking deaf to this though, and it makes me click a "sign in again" button or some shit, which then has a chance to proc the V1 vs V2 UI issue. Like, come the fuck on bro I SEE the cookie when I look at my network requests, just put the fries in the bag and stop making my life that little bit more irritating.

204 comments