This happens because of how Microsoft approaches product development and design. On many product teams, PMs end up doing not only the product design decisions but even designs much of the products themselves. This works for them because it focuses product cycles on releasing what "matters" to the customer, but it ends up cutting craft and quality. This makes their products poor to use, but is also what drives revenue…
Ask HN: Why is Microsoft Teams still so bad?
41–50 of 814 posts
Re: Ask HN: Why is Microsoft Teams still so bad?
#42It isn't because Microsoft lacks good programmers. My guess would be that someone believes they need to have every feature from slack, zoom, WebEx, meet etc, and also integrate tightly with every Skype/SharePoint/OneNote feature, and also run on at least four platforms. But they aren't willing to give people time to do this.
Re: Ask HN: Why is Microsoft Teams still so bad?
#43Re: Ask HN: Why is Microsoft Teams still so bad?
#44We'd never see communications, even with notifications, in the "Teams" area of teams. When I did think to look at the conversations, all of the additional whitespace and padding the Mac client adds (not sure if it's all clients) on the messages in the "Teams" area just made it very difficult to consume context around a single discussion. There were another annoyances, but we didn't use it long enough for me to remember what they were.
We now just use the "Chat" portion of teams for all conversations and rename multi-person conversations with the project name. Starting a new chat with the same group of people for a different project is far more difficult than it needs to be, but I understand that's probably not the use case with how we're using it.
Search is abysmal. When clicking a result, you jump to the message but it is invariably devoid of any contextual information. It's just the message, by itself, in the chat window. It's only use is finding the date/time for the message you need, then scrolling back (for minutes sometimes) until you find the conversation from 3 weeks ago. And then, all the reverse infinite-scroll loading makes the client slow down to a crawl.
We routinely have issues with images not displaying. Sometimes loading the larger version works, many times it does not.
We routinely have issues with messages going completely missing in 1:1 chats. The sender can screenshot and show the message was sent, but the recipient never receives it, even after restarting the client.
I often get notifications of a new message in a 1:1 chat and when I goto the chat, I'm at the end of the channel and the message isn't there. I have to scroll up and then scroll back down so the infinite-scroll will load the missing message.
When in the new message box, I can CMD + UPARROW to edit my last message. This is useful because I make a lot of typos and fix them after sending/reading. A bad habit, perhaps, but it's how my process works. Anyway, this doesn't work if I someone has sent a message after mine. Teams is not smart enough to let me edit my last message with CMD + UP unless it was the last one sent. I have to switch to the mouse to make the edit. Also, if I CMD + UP in time to make an edit, submit it, then realized I missed another typo (it happens), CMD + UP no longer works. I have to manually focus the "Type a new message" box again and then it'll work. At that point I've touched my mouse, so I usually just opt to right click + edit the last message.
Sometimes after waking up my Mac, the teams window is missing. This happens to outlook too. CMD + TAB to focus the app doesn't retrieve it. I usually have to "launch" teams or outlook again (while it's still technically open) to get the window to reappear. No other App on my Mac does this, just Teams and Outlook.
Given how we use Teams, I like to "pin" chats for specific projects. I'm limited to how many I can pin. Why?
This one is minor: Gifs loaded with giphy can be paused. Copy/pasted gifs cannot. They auto play forever, which is annoying when it's the team chat I keep focused 90% of the day, but the conversation is slow that day.
I'm sure there are other things I'm missing.
Re: Ask HN: Why is Microsoft Teams still so bad?
#45No links
You can’t link to conversations. This means if you want to add context to a Jira ticket or in a code comment, you can’t easily do so.
Inconsistent UI
The UI between a Teams channel and a chat with multiple people is not consistent. Direct chats:
- do not have the ability to thread; so you end up with quotes all over the place and interleaved conversations.
- don’t support ``` for code blocks. Channel chats do. Why? I have no clue.
Notifications in channels are easy to miss
It’s really easy to miss notifications from channels unless you get messaged directly about it.
The emojis are bad
They aren’t customizable, but even the ones that are available are not great.
Compared to Slack
Teams lacks these features that I find useful in Slack:
- Don’t have time to address something immediately and don’t want to forget about it? Right click → Remind me later.
- Instead of struggling to communicate a screen location, draw on the screen when a co-worker is sharing their display. Ok, Teams introduced this recently. But the first time I tried it, I ended up stuck in annotation mode and had to quit Teams to be able to interact with my applications…
- Integration with Jira for automatic linking to mentioned issues by Jira Issue Key, e.g., PROJ-123. I think this one is just a limitation because my company hasn't added the integration.
- Notifications when when activity occurs in Bitbucket or Jira. Ditto.
The hold music sucks
The music played when alone on a call sucks. I suppose this is more subjective than the rest…
Re: Ask HN: Why is Microsoft Teams still so bad?
#46I wonder how many of these complaints are due to Teams itself or if it's due to the crappy "corporate" builds deployed to the PCs? My guess is that it's more due to the crappy corporate builds since I've seen so many of them that don't have up-to-date drivers (or have missing drivers), and many of them have multiple competing security scanning software, along with over-strict policies and restrictions that affect Tea…
It’s Teams. On a intel Mac with no management software, it is a shitty, buggy mess.
Re: Ask HN: Why is Microsoft Teams still so bad?
#47Teams is bundled with Office 365 to steal marketshare from other companies like Discord who charge a bit more and are a stand alone service. It’s why Salesforce bought Slack.
CFOs at Fortune 500 companies want to be efficient with their spending so they won’t buy an extra license if their existing bundle is “good enough”
Teams is “good enough” so Microsoft doesn’t invest in it as much as other more profitable areas
Re: Ask HN: Why is Microsoft Teams still so bad?
#48If it was just chat, it would probably by much less of a bloated mess of crap. The problem is that MS never makes just a simple tool anymore. They want it to hook into every other MS platform and product line and before you know it, the new product is slow and bloated again...
Re: Ask HN: Why is Microsoft Teams still so bad?
#49But it's normal for MS to rush with a product, only to get better after years. I remember that IE only gets good after IE 4, and SQLServer only after some versions too.
Re: Ask HN: Why is Microsoft Teams still so bad?
#50My company is transitioning to Teams and I find it frustrating. So much so that I collect my complaints in a confluence page. I could be wrong on some of these, so happy to be corrected! No links You can’t link to conversations. This means if you want to add context to a Jira ticket or in a code comment, you can’t easily do so. Inconsistent UI The UI between a Teams channel and a chat with multiple people is not cons…