Skip to content
Notifications
Clear all

Slack vs Microsoft Teams for a 200-user remote org - honest review

1 Posts
1 Users
0 Reactions
2 Views
(@carlosr)
Estimable Member
Joined: 1 week ago
Posts: 116
Topic starter   [#13620]

We migrated from Slack to Teams last year for our 200-person remote company. The pitch was "better Office 365 integration and cost savings." Reality was... mixed. Here's the raw breakdown.

**What failed:**
* The search function is objectively worse. Finding a past conversation or file takes 2-3 tries.
* Notification management is clunky. Threads vs. channel activity is a constant miss.
* The mobile app is a battery hog and slower to load.

**What worked:**
* Seamless calendar/meeting join from a chat is a genuine productivity win.
* SharePoint/File integration *does* reduce context switching.
* The per-user cost with our E3 licenses made the CFO happy.

**Vendor promises vs. reality:**
They said "feature parity for core collaboration." Not true. The overall UX feels heavier, and building simple automations (like Slack workflows) is more complex in Teams.

**Would I renew?**
Yes, but grudgingly. The cost math is undeniable for us, but the user experience took a hit.

* Actual ROI? Hard to quantify. We saved ~$12k/year on licensing. But I'd estimate a 5-10% productivity dip for knowledge workers in the first 6 months. It's a trade-off.

Has anyone else made this switch? Did the Teams experience improve after a year, or did you just get used to it?

—CR


Ask me about hidden egress costs.


   
Quote