We ran an audit of our own Slack workspace this week, mostly out of morbid curiosity, and found 1,200 channels for a company with considerably fewer than 1,200 things that have ever happened to it. Here's what we found, and what it says about how decisions actually get made here.

#proj-synergy-v2-final

Nobody currently employed here was present for the creation of this channel. It has 47 members, three messages in the last calendar year, and a pinned message reading "moving decisions to the thread below," a thread that does not exist, was never created, or was deleted at some point by someone acting on information the rest of us don't have. The channel will never be archived, because archiving it requires someone to assert, in writing, that Synergy V2 is dead, and no one currently on staff has the standing to make that call about a project they've never heard of.

#random

Four years old. The last fifty messages are, in order: a birthday gif, a Wordle screenshot, someone asking if anyone's seen the stapler, a meme about Mondays, and a single message reading "wrong channel, sorry" posted by someone who then never corrected it. This channel has more sustained daily engagement than three of our active product initiatives combined, which should probably tell leadership something about where morale, attention, and unstructured bonding time actually live, and does not.

#leadership-sync (you are not in this channel)

This is the real one. Eleven people. Everything that actually gets decided gets decided here, then gets re-announced in a bigger channel in a tone implying it was always inevitable, arrived at collaboratively, informed by the very feedback that was never solicited from anyone outside these eleven people. The existence of this channel isn't a secret, exactly. It's just never mentioned, the way a load-bearing wall is never mentioned until someone tries to knock it down.

#q3-initiative-realignment-v3

The existence of a "v3" confirms there was a v1 and a v2, neither of which anyone can locate, both of which presumably contained a plan that got realigned into oblivion before this channel was created to realign it again. Searching the workspace for "v1" returns 4,000 results, because apparently everything here gets a v1, and nothing here gets a v4, which is either a statement about ambition or a statement about follow-through, and we're not sure we want to know which.

#general

Technically mandatory. Functionally abandoned, except for two use cases: company-wide announcements posted by someone in People Ops, and the occasional reply-all disaster where someone means to DM a coworker a complaint about a meeting and instead posts it to four hundred people, generating more genuine, candid engagement in eleven minutes than the channel sees in a normal month, before being deleted, unconvincingly, nine minutes too late.

#alerts-prod-urgent-do-not-mute

Muted by everyone. The channel name is a direct, written instruction, and its violation rate among the engineering team is effectively 100%, which either means the alerts in this channel are not actually urgent, or means they are urgent and everyone has made a collective, unspoken decision that urgency fatigue is worse than the thing the alerts are warning about. Nobody has investigated which.

Why nobody ever archives anything

Archiving a channel is an admission that something is over, and admitting something is over requires someone with the authority to say so, and the person with that authority is busy, and the channel costs nothing to leave open, so it doesn't get closed — it just gets quieter, year over year, until it's a tiny tombstone for an initiative nobody will eulogize because nobody can remember exactly when it died.

What this actually reveals about how the company runs

Not that we're disorganized, necessarily — that the real information architecture of the company isn't the channel list at all. It's a smaller, denser, mostly invisible graph of who actually DMs whom, which eleven people are in the room where it happens, and which 1,150 channels exist mainly to make everyone else feel like the room is bigger than it is.

Our recommendation

Archive aggressively, on a calendar, without waiting for permission that will never arrive. And if there's a channel you're not in where the real decisions happen, that's not a Slack problem. That's an org chart problem wearing a Slack costume.

If your workspace currently has a channel called #rebrand-2024-DO-NOT-DELETE that's still open in 2026, email us at contact@b2bsaas.guru. We'll help you audit it. We will not promise to tell you what's in #leadership-sync.