I'm stuck using Teams right now and it is an abysmal experience. There are definitely complaints to have about Slack, but it can be miles worse.
Just today I was looking for a prior conversation to document it for the future. I selected a portion of the conversation so that I could paste it into another tool I use for documenting. I selected the text once and it deselected a good chunk of it. Repeat. Okay, clearly not working well. I had to copy and paste 5 times to get ~15 lines of text because if you scrolled at all it somehow deselected some portion of the text.
I mean, honestly, what tool doesn't even let you easily copy the conversation? Teams is that tool. That's just one of the many issues I have run into today.
But did you ever try to search for a message in a conversation, and have it give you just the message you wanted, without any surrounding context? Or have you ever tried to scroll through chat history, only for it to lazy-load 10 messages at a time, making you spend 5 minutes scrolling constantly to find a conversation from a few months ago?
Teams would even lose my messages completely from time to time. It was honestly hard to believe how janky it was.
Yes; they seem to have fixed that now, I don’t know when but I was surprised when it took me to the conversation with context suddenly.
Did you know Teams had apps? Inside of it?!
90% of the problems I encounter with Teams (bad UX, crashing, freezing, corrupted sessions) would be removed if they deleted every feature outside of chat/video and more loosely coupled themselves to Office365/Exchange.
Do I stop my presentation so that I update my driver, or do I wait until next time I want to share my screen and interrupt then?
- Slack is so easy and fun to use that we use it for things we shouldn't be (fun channels, fun integrations). It creates too much noise and hard to extract signal. It ends up being distracting past 100+ people company.
- Teams is so bad that people try not to use it. It forces you to use it minimally because everything is terrible. It actually ends up being more productive than Slack.
That was part of the pitch at work - "oh, over 3 years our total savings is $200k" or something. Great, but if each dev loses 10 minutes a month, or is frustrated and less efficient for an hour, that costs us 5x that.
And now they have just flipped the interface so you scroll up for new and not down. With no warning and no notification so for the first day no one could find any current conversations.
And the terrible "Teams documents" so we can lock away documents behind a specific chat. If anyone should be having layoffs, it is their UX folks.
Yes, MS Teams might actually suck worse, but don't try to diminish valid complaints about something else that also sucks
Neither are good tools.
Adobe has already started to feed its customers' data to its AI. Who says, other providers won't take advantage of broad contracts and terms in order to avoid informing their clients.
If it weren't for the security and reliance implications, I'd run a company chat over Facebook Messenger. Simple as.
- HipChat, Campfire (Basecamp) clone
- FlowDock, which was superior to Basecamp and Slack
- Textual
- IRC
And now there's Discord, albeit for different purposes.
Workplace is an everything platform.
The problem with each tends to be distractions, discoverability, bookmarking, an app/browser performance. You really have to have a strong culture of netiquette to use any of them AND access to video conferencing to have quick meetings, because trying to do everything over chat doesn't work.
Let me introduce you to Teams.
Try writing code in Microsoft Teams. Slack is very decent.
And the "markdown" text input oh my. Rarely have I seen a worse markdown input than in Slack. Maybe on Bitbucket or Confluence it is worse. It is as if they have decided to not use any existing and perfectly well working markdown parsers, but instead get an incapable team of engineers to reimplement a bug-ridden one with missing features. One cannot even insert an image at any place in the message, but only at the bottom. That means one needs to refer to the image in the message, when otherwise one could have simply had the picture in that place where it is relevant. It is such a headache for anyone more familiar with markdown. At this point just give me a plain text input, that has any normal off the mill markdown parser to properly translate my text into a message.
Oh and they still have not managed to implement voice chat according to standards properly, so that it works in all modern browsers. While other more feature full chat programs like Discord had this solved for years ago, Slack is still the same old shit. Now I have to start ungoogled-chromium every time I want to enter a "Huddle" and navigate to their website, where they will bug me with their incessant popup asking me to use their desktop app, which I have to decline every. single. time. because chromium does not remember to block such popups from websites.
So basically Slack is quite crap.
[1]: https://github.com/zulip/zulip