this post was submitted on 27 Jul 2023
266 points (98.2% liked)
Technology
59419 readers
4559 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I absolutely agree : our company used slack, Google docs, and self-hosted exchange.
Eventually, MS forced us to replace our self-hosted exchange for MS' cloud solution. This was basically a ramrod for shoveling O365 and having it replace Slack with Teams and Google Docs with O365.
The migration was painful... going from "I have the exact tools I need for the job" to "jebus, this is the best MS has? On Teams I can only see 4 people at the same time? What was MS thinking".
My company only uses Teams and it works fine from what I can tell, what's so bad about it?
Lots of weird polish issues in my opinion... One that really peeved me was (for a while at least) you could search for a message, but there was no way to jump to that message from the search results. So you couldn't read the context unless you scroll all the way back up.
But primarily it's that the mechanics are different from things like Slack and Discord in ways that are just less intuitive.
Channels function more like announcements + comments rather than a chat—you are really shoehorned into posting a "Topic" and discussing it in the replies. There's no way to carry a linear conversation in a channel otherwise. And to load replies you have to keep clicking "see more" as if this is a social media site, so it's very annoying when your 800+ comment critical discussion happens there. Not to mention notification settings aren't granular enough, so you either get hammered by all activity, or remain oblivious to discussions which may have popped up in an older Post.
What tends to happen in my experience is small working groups spawn off a group chats because the flow is better for daily conversation there than in Channels. Which, of course hides this activity from anyone not in the chat. And group chat's are entirely linear in Teams—you don't have threads the way you do in Slack, so chat history tends to get messy quick.
The channel-then-thread organization Slack uses is much more natural for the teams I tend to work on, because you just have the one main discussion which can be segmented into threads as needed.
Hmm ok I guess those are valid points. My company doesn't use Teams for anything else besides meetings or as s chat app. There's no actual work being done through it