There are two simple reasons why Slack has not become, and will not become, the company brain.
- Slack captures mostly coordination, not execution
- Slack is built for messaging, not prompting
Slack's purpose is primarily to route attention. It helps people ask questions, share updates, escalate issues, and coordinate meetings.
A company brain's primary purpose is to do work. Slack rarely captures the knowledge of how to work, and even in the rare cases it does, it does so by accident.
Problem 1: Work does not happen in Slack
Most work is coordinated in Slack and then performed somewhere else.A person asks a question in Slack, but then the actual work moves to a meeting, or a document, or a ticket or most often nowadays, a private AI chat.
We can see the handoff on slack, but not the actual work.Slack sees:
“Can someone look into this?”
It often misses:
What did they inspect? What hypotheses did they test? What evidence changed their mind? What tradeoff was made? What should the next person remember?
During an SRE incident: the valuable knowledge is not just that people discussed the incident and its status over time. The valuable knowledge is the operational reasoning and knowledge uncovered during the resolution of the incident.
Why was rollback rejected? Why did the team trust one graph and not another? Which dependency made the mitigation risky? What did the team learn about the system?
While some of that may appear in Slack, most of it happens while people are looking at logs, investigating code, joining calls, trying out fixes and so on.
A team working on an email nurture campaign may discuss ownership in Slack. But the valuable knowledge is created over time while people are building the campaign and while investigating the results of the campaign.
Why use activation rate instead of open rate? Why is MQL conversion misleading? Which segment matters most? What caveats exist in attribution?
Slack may get the update, but it does not get the work. And because it does not get the work, it can't extract the know-how into a "brain".
Problem 2: Slack is built for messaging, not collaborative execution
Slack’s core product goal is to increase human-to-human messaging. That shapes how people use it.
People do not go to Slack to perform complex work with AI. They go to Slack to talk to other people.
They ask questions, clarify ownership, and coordinate next steps. Then they leave and use AI and their tools privately. They reason through the actual problem somewhere else.
That means the company loses the most valuable context.The prompts are private. The analysis is private. The judgment calls are private. The reasoning that produced the final "accurate" answer is private.
This is why adding AI on top of Slack history is useful but limited.
It can help answer:
Who mentioned this? Where was this discussed? What was the rough outcome? Who owns the project? What did someone say last time?
But a company brain needs to answer a different question:
Given this problem / task at hand: what should we do and how do we make AI do it?
The difference is surprisingly subtle, but obvious in practice
An AI native alternative may look like Slack.
It may have channels, threads, mentions, notifications, reactions, and participants.But the big difference is the message.
In Slack, a message is usually communication. In an AI-native system, a message is an operational move. It's a prompt to a human or to an AI.
The conversation is not about the work, instead the conversation is the work (a part of the work to be precise).A Slack thread opens with:
“Can you look into why activation dropped?”
Instead of:
“Why did activation drop?"
Then AI & humans can pull the relevant data, compare cohorts, surface possible causes, ask for human judgment, record the caveat, and create the follow-up. The conversation thread now contains the discussion, the evidence, the actions, the artifacts, and the decision.
Conversation threads like that contain operational wisdom, because the work happened inside the conversation. Slack is usually outside that work loop.
It is the coordination theatre before the work, after the work and around the work. It is rarely the work itself.
That is why Slack will not become the company brain.Because even though Slack does have useful context, it just has the wrong kind of context.
