4 ms·

We switched from Slack to Teams several years ago because we were all-in on Office 365 products. Everyone hated the change, but with stuck with it. It was slow,

We switched from Slack to Teams several years ago because we were all-in on Office 365 products. Everyone hated the change, but with stuck with it. It was slow, crashed a lot, search was abysmal and you'd have to be a masochist to use it willingly.... But they pushed out a new version recently. Now you've got Teams Classic and Teams NEW (work or school)... at least on the Mac. It's sooo much better. Way more stable. Search is a delight (relatively speaking). We get far fewer complaints now. Worth mentioning: We only use the "Chat" aspect, we don't use the "Teams" aspect. If we want to discuss a project, we just spin up a new chat with relevant parties and rename the channel to the project. Works great. We could never get "buy in" on the Teams aspect, nor threaded discussions. The main reasoning was having to monitor two tabs in the product. Everyone just wanted to stay on the Chat tab, so we made it work.

FireBeyond 3y ago
> If we want to discuss a project, we just spin up a new chat with relevant parties This part I struggle with, and maybe we're doing it wrong, but to me as a PM, this way is painful. Search helps. But then I have to remember, "Was discussion about X in the chat with people A + B + C, or was it in A + B + D's chat, or B + D's chat, or..." We also have significant challenges with knowledge silos (not intentional, and more about a cadre of new devs being brought on) that (not the only solution) I feel that pushing conversations to specific teams when appropriate might help, improving visibility.