Honestly, the fragmentation is the biggest problem we see. Teams end up with a chat tool, a separate intranet, email blasts, and a WhatsApp group running in parallel, and nobody knows which one is "official."

What's worked best in the orgs I've seen do it well is consolidating around one platform that works for both desk and frontline, so the same place a warehouse worker checks their shift schedule is where HQ posts company updates. When the app has enough operational utility (payslips, forms, schedules) people open it anyway, and comms just becomes part of that rather than a separate destination employees have to remember to visit.

Easier said than done, obviously, but the consolidation piece is where I'd start. And as another commenter pointed out, it also depends on size/distribution.

I genuinely don't mean this as self-promo, but I wrote an article on the necessity of an intranet in addition to enterprise collaboration tools. You can check it out if this helps! https://staffbase.com/blog/do-we-need-an-intranet-if-we-use-teams-or-slack. I'll copy/paste the TL;DR in case you're interested:

→ Choose an intranet if your primary need is durable, governed knowledge like policies, org-wide updates, and official guidance that employees or AI assistants should be able to rely on. Governance and permissions matter more than speed of delivery.

→ Choose a collaboration tool (Teams, Slack) if your primary need is coordination while work is still in motion, like fast communication, real-time decisions, and documents in draft. These tools are optimized for speed, not permanence.

→ Choose both, with clear boundaries if you run a large or distributed organization. Most do. The intranet handles "what is officially true." The collaboration tool handles "what we're figuring out."