3 ms·

My company recently moved from Slack to Teams, for financial reasons. I'm sorry but Teams absolutely sucks compared to Slack. There are tens of thousands of p

My company recently moved from Slack to Teams, for financial reasons. I'm sorry but Teams absolutely sucks compared to Slack. There are tens of thousands of people voting for feature requests on the Teams community site, to bring Teams to parity with Slack. The killer one is that when you start a thread in Teams, it will be pushed to the most recent spot every time someone comments on the thread. In Slack, the original post that started the thread is stable, and threads are in a side panel, so the order of original posts is maintained chronologically. There are other examples as well, but just in general I find myself spending way more time just navigating around in Teams and losing productivity trying to work within it.

pinewurst 6y ago
Not sure why this is downvoted. I work for people who have both and while I'm definitely not a Slack fan, find Teams to be pretty much unusable outside of video chat. I have trouble even considering the two as covering the same space when I think about it...
- duderific 6y ago
  Maybe because I was a little hyperbolic with "absolutely sucks", but that represents how I feel pretty accurately.
- jcrawfordor 6y ago
  I think one reason is that some people, including me, find Slack's behavior of not moving threads with activity up extremely irritating. It means that thread replies are very easy to not notice and it makes it confusing to understand who knew what when. I realize this is a matter of opinion but I think that's kind of the problem, both platforms have chosen one way and forced it on users. I'm not sure that there's any same way to make this configurable either, but I don't think one option is clearly Superior to the other. There's also plenty of precedent either way, even just looking at old forum software which tended to sort topics by activity (the Teams approach). That seems to mean that neither way is going to be obvious to all users. I guess the conclusion is that I'm not sure there's an approach to this problem that won't piss someone off, but by that token it's not a clear win for Slack. Also for what it's worth I think Slack's behavior is the less common option across similar products, but I've not done any kind of exhaustive survey, I just use 4-5 of these things and Slack is the one that always throws me off by behaving that way.

pinewurst 6y ago

Not sure why this is downvoted. I work for people who have both and while I'm definitely not a Slack fan, find Teams to be pretty much unusable outside of video chat. I have trouble even considering the two as covering the same space when I think about it...

duderific 6y ago
Maybe because I was a little hyperbolic with "absolutely sucks", but that represents how I feel pretty accurately.
jcrawfordor 6y ago
I think one reason is that some people, including me, find Slack's behavior of not moving threads with activity up extremely irritating. It means that thread replies are very easy to not notice and it makes it confusing to understand who knew what when. I realize this is a matter of opinion but I think that's kind of the problem, both platforms have chosen one way and forced it on users. I'm not sure that there's any same way to make this configurable either, but I don't think one option is clearly Superior to the other. There's also plenty of precedent either way, even just looking at old forum software which tended to sort topics by activity (the Teams approach). That seems to mean that neither way is going to be obvious to all users. I guess the conclusion is that I'm not sure there's an approach to this problem that won't piss someone off, but by that token it's not a clear win for Slack. Also for what it's worth I think Slack's behavior is the less common option across similar products, but I've not done any kind of exhaustive survey, I just use 4-5 of these things and Slack is the one that always throws me off by behaving that way.