← Back to blog

Our Collaboration Tools Are Stuck in 2015

collaborationslackproductivityaitools

Fivetran's CEO went on record asking Anthropic to build a Slack replacement. That's a sitting CEO of a billion-dollar company publicly begging for someone to fix team communication. Let that sink in.

He's not wrong. Slack launched in 2013. It's 2026 and the core experience is fundamentally the same: channels, threads, DMs, emoji reactions. The world has changed completely. Our communication tools haven't.

What's actually broken

I run a distributed team. Here's what my typical Slack day looks like:

I wake up to 247 unread messages across 23 channels. Maybe 12 of those messages actually need my attention. Finding those 12 takes 35 minutes of scrolling, reading context, and figuring out what happened while I slept.

Someone asked me a question in a thread at 2am. The thread is buried under 8 hours of other conversations. I find it at 11am. The decision already got made without my input.

A critical decision happened in a DM between two engineers. Nobody else knows about it until something breaks in production three days later.

This is not a Slack problem specifically. Teams, Discord, every synchronous messaging tool has the same fundamental issue: they optimize for sending messages, not for receiving information.

Why AI should fix this but hasn't

We have AI that can summarize entire books. We have AI that can write code, analyze data, and generate images. But my team chat still shows me messages in reverse chronological order and calls it a day.

Where's the AI layer that reads all my channels and gives me a prioritized briefing every morning? Where's the tool that detects when a decision is being made without the right stakeholders? Where's the system that takes a rambling 47-message thread and extracts the three action items?

Some startups are trying. None have nailed it. The incumbents are bolting AI features onto decade-old architectures and hoping that counts as innovation. Slack's AI summary feature is better than nothing. It's also not good enough to change how anyone works.

What I actually want

Here's my wishlist, and I don't think any of it is unreasonable given current technology:

Morning briefing. When I open my communication tool, show me the 5 things I need to know. Decisions made, questions waiting for me, blockers on my team, deadlines approaching. Don't make me scroll.

Smart routing. If someone asks a question I can answer, surface it to me immediately. If a conversation is happening that affects my project, pull me in. If it's noise, filter it out.

Decision logging. When a decision gets made in chat, capture it automatically. Link it to the relevant project. Make it searchable. Stop losing institutional knowledge in message threads.

Async-first design. Stop designing for real-time and bolting on async. Design for async and make real-time the option. Most work doesn't need instant responses. Our tools shouldn't pretend it does.

Why this matters more than you think

Bad communication tools don't just waste time. They create organizational dysfunction. Information silos form because finding information is hard. Decisions get made by whoever's online, not whoever's most informed. People burn out because they feel obligated to monitor channels all day.

I've estimated that my team loses roughly 90 minutes per person per day to communication overhead. That's 7.5 hours a week. Per person. At a 15-person team, that's 112 hours a week. Burned on scrolling.

Someone will solve this. My money's on a startup that builds communication AI-native from day zero, not a legacy tool that's trying to retrofit intelligence into a chat app. Whoever gets there first is going to eat Slack's lunch.

Fivetran's CEO is right to be frustrated. We all should be.