Without getting too in the weeds. If you're a Microsoft 364 customer already, Teams is likely included at most subscription levels. Adding Slack on top of that seems like an unnecessary cost in that case. Transitioning a culture to use Teams is a bigger challenge. For meetings we've been found a good adoption rate, but for actually making Teams there's less motivation. I personally love the Chat capability, but getting people to respond to emails is hard enough nevermind thowing chat into the mix.
Microsoft 364 was a typo, but I stand by it, since it does go down more than I'd like.
3 years 1 month ago#52059by Elan Aleksandr Sablich
I agree. It depends on who is using it and for what, but Slack isn’t something I see on-site staff utilizing without headaches. I’d also stick with Teams.
Slack doesn't really do anything you can't do through Teams. But if you can't get your team to use email effectively, neither Slack nor Teams are going to be received well.
3 years 1 month ago#52061by Elan Aleksandr Sablich
I live and swear by Asana! It’s all about assigning yourself or others tasks and you can have an ongoing comment thread on each task with the ability to share files
We just went from slack to Microsoft Teams after 2 years. Each has its own advantages.
The main reason we changed is because slack just updated their os and now you have to have Android 9.0 to run it. And a lot of guys have 8.0 or older and can no longer use slack with out everyone going out and buying new phones.
I will add - I always start “Manager Chat” in Teams so Managers can chat with each other throughout the company. They answer so many of each other’s questions easily and quickly throughout the day.