The Slack Channel Graveyard: Why Your “Async Culture” Is Just Loneliness at Scale

It was 2:14 PM on a Wednesday and Namfon’s green tea had gone cold. She could tell without touching it — the jasmine smell had faded twenty minutes ago, replaced by the stale hum of the air conditioning and the faint sweetness of someone’s mango sticky rice two desks over. She’d been walking seven people through a data migration tradeoff on the Teams call — three black rectangles, one person whose eyes hadn’t stopped scanning left to right for the last five minutes, and one who’d been on mute so long the icon had become a permanent fixture. She watched her own tiny thumbnail talking to a grid of initials and photos of people’s dogs, finished her thought, and asked, “Does anyone have concerns?” Three seconds of dead air. “Great, we’ll move forward then.” She ended the call and Spotify picked up where it left off — the opening bars of Hotel California drifting through her headphones, which felt about right for a meeting people had checked into but never really arrived at.

That wasn’t alignment. That was a group of people performing attendance while decisions happened to them. And it’s happening in your organisation right now — not because your people are lazy, but because you’ve built a communication culture optimised for the appearance of collaboration rather than the substance of it.

The Illusion That It Has Taken Place

George Bernard Shaw once said, “The single biggest problem in communication is the illusion that it has taken place.” He died in 1950, decades before Slack existed, but he might as well have been describing your company’s workspace.

Here’s the pattern I see repeated across teams here at Agoda and everywhere else I’ve worked: a problem emerges. Someone creates a Slack channel. #project-phoenix. #architecture-decisions. #incident-retrospectives. The channel is announced with optimism. People join. A few early messages set a hopeful tone. Then the conversations slow, thin out, and eventually the last message is a solitary “Thanks!” from seven months ago, sitting there like a headstone in a digital cemetery.

The channel still exists. It’s still in the sidebar. And when someone asks “where do we discuss architecture decisions?” the answer is still “there’s a channel for that.” The channel exists, therefore alignment must exist. It’s cargo cult collaboration — building the runway, lighting the signal fires, and wondering why no planes land.

We’ve confused the tool with the outcome. Slack channels don’t create communication any more than a gym membership creates fitness. But we’ve collectively decided to pretend otherwise because the alternative — acknowledging that real collaboration is expensive, synchronous, and uncomfortable — doesn’t fit the narrative we’ve been sold about modern work.

Where Async Shines (And Where It Quietly Dies)

Let me be clear: I’m not here to bury async communication. It’s brilliant for what it was designed for. Status updates? Perfect. Reference material and documentation? Ideal. Non-urgent questions where someone can respond when they have context? Absolutely. Async is a tool, and it’s a good one.

The problem is that organisations have stretched async to cover things it was never built to handle: architectural decisions, conflict resolution, nuanced tradeoffs, building shared understanding across teams. These require bandwidth that text in a channel simply cannot provide.

Think about what happens when a genuine technical debate kicks off in Slack. I’ve seen it dozens of times. Someone posts a proposal. Another person disagrees. A thread spawns. Within an hour, you’ve got a thread with 87 replies, each one a small essay. People are so busy composing their next thoughtful response that they skim — or outright miss — the three other thoughtful responses that landed while they were typing. The “discussion” becomes parallel monologues, not a conversation. Nuance gets lost. Tone gets misread. Someone gets frustrated and takes it to DMs, where the real decision happens with half the stakeholders.

And here’s the part nobody wants to say out loud: if you use a Slack channel as your decision record, your decisions now live in Slack history. Is that really where you want the reasoning behind your architecture to live? Buried in a thread, interleaved with emoji reactions and “can someone look at this?” messages from three other conversations? Decisions deserve a home. Slack is a hallway, not an archive.

The Agile Manifesto — remember that thing we all claim to follow? — has something to say here. Principle six, stated without caveat or qualification: “The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.” Not “a Slack thread with the right people tagged.” Not “a well-structured async RFC.” Face-to-face conversation. We’ve taken the manifesto’s clearest directive and built an entire communication culture around ignoring it.

The Bandwidth Problem Nobody Wants to Acknowledge

Now, someone reading this is already composing a rebuttal: “But we do synchronous communication — we have video calls!” And sure, you do. But let’s be honest about what most video calls actually look like.

You schedule a meeting. Eight people join a Teams call. Seven black rectangles and one Engineering Manager with their camera on, whose eyes are tracking left to right in that unmistakable pattern of someone reading something else entirely. The meeting window occupies maybe a quarter of everyone’s screen while email, Slack, and that PR review compete for the remaining real estate. Someone presents. Someone asks a clarifying question. Nobody challenges the approach — not because it feels confrontational, but because half the call has been skimming Slack in another window and missed the key detail that would have prompted the challenge. The one manager with their camera on scans the grid of black rectangles, asks “Any concerns?” and interprets silence as consensus. It’s not. It’s absence disguised as agreement.

Even with cameras on, I catch people doing this. Their eyes drift. Their attention fragments. With cameras off, it’s worse — you’re essentially broadcasting into a void, hoping the void is paying attention. Someone might have stepped away to settle their kid, or ducked to the bathroom and missed three minutes of context that changes the entire decision. You just don’t know. And because you don’t know, you can’t course-correct.

The physicist Albert Mehrabian’s research — often oversimplified but directionally useful — suggested that a significant portion of emotional communication is non-verbal. Body language, facial microexpressions, the energy in a room. When you’re debating whether to take on six months of migration work or accept a year of workarounds, those non-verbal signals matter enormously. The slight frown when someone hears a number they think is unrealistic. The posture shift when a senior engineer disagrees but hasn’t decided whether to say it yet. The temperature of an over-occupied meeting room that creates a shared sense of urgency.

You don’t get any of that through a grid of avatar photos and pet dog pictures. And you get absolutely none of it in a Slack thread.

As the coach Phil Jackson — who won eleven NBA championships by getting extraordinarily talented individuals to function as teams — observed, “The strength of the team is each individual member. The strength of each member is the team.” That strength is built through presence, through the friction of being in a room together, through the accidental conversations that happen when you’re not trying to have them. You cannot Slack your way to that kind of cohesion.

Hot Takes and Hot Seats

I recently had a conversation with someone from the business side who was pushing for hot-desking in our office. When I pushed back, he looked at me like I’d suggested we go back to punch cards. “Shouldn’t tech people be the ones pushing for these more modern practices?”

I’m not backwards. I work with engineers. It’s a highly collaborative profession. Ensuring a team is not only co-located but sitting together is important for accidental conversation — the kind that happens when you overhear someone wrestling with a problem you solved last month, or when a quick “hey, have you thought about…” turns into a whiteboard session that saves two weeks of async back-and-forth. Hot-desking turns this into a gamified booking system where coming to the office to collaborate becomes a logistical puzzle. That’s not modern. It’s friction dressed up as flexibility. And it’s a blocker to effective engineering.

But let me set aside my opinions about workspace ownership — that’s a topic for another blog. The deeper point is this: the current tech culture narrative has decided that async is enlightened and progressive (“we respect people’s focus time!”) while synchronous, co-located work is outdated, even oppressive. I’d like to offer some counter-evidence.

What Happens When You Actually Get People in a Room

We recently ran an Acceleration Week with a partner company — twenty-five engineers in a co-working space for four days. Minimal pre-planning. No elaborate scoping documents. Just the right people, in the same room, pointed at the same problems.

The results were striking, but the retro comments told the real story. One engineer said it plainly: “One thing I really like about this kind of approach — less context switching. Normally, day to day, I’m doing like ten things at a time and nothing gets done.” Another reflected on the discomfort that precedes the productivity: “You kind of have to be comfortable being uncomfortable. And then at the end of the week, I look back on it — holy shit, look at what all we did. For having very limited planning, we actually knocked so much stuff out.”

But the comment that should be tattooed on every engineering leader’s wall came from Somchai, an Engineering Manager, who put it bluntly: “If we didn’t do this, the migration probably would have lasted a year. All of those problems we solved right away. Otherwise that will be communication on Slack and then reply maybe next week, because we are busy, or you guys are busy.”

Read that again. A year of async communication compressed into a week of being in the same room. That’s not a marginal improvement. That’s an order-of-magnitude difference in velocity, achieved not through better tooling or smarter processes but through the oldest collaboration technology humans have: physical proximity and unstructured time together.

I wrote about the broader organisational dynamics behind this in The COVID Hangover Is Killing Your Engineering Velocity. The short version: the pandemic forced us into remote-first patterns, and we’ve kept many of them not because they’re optimal but because they’re comfortable. Comfort and effectiveness are not the same thing.

Fighting the Graveyard: What Actually Works

The solution isn’t “just have more meetings.” That’s the lazy take, and frankly, bad meetings are worse than no meetings. The answer is being intentional about which communication needs which medium, and having the discipline to enforce it.

Classify your communication by decision weight. Lightweight, reversible, low-context stuff belongs async. Status updates, FYI announcements, simple questions with clear answers — Slack is perfect for these. But anything involving tradeoffs, ambiguity, or cross-team coordination needs synchronous time, and ideally face time. Stop pretending a thread can substitute for a room.

If you’re unsure which category something falls into, default to in-person. You’ll rarely regret over-communicating synchronously; you’ll frequently regret under-communicating asynchronously.

Remote synchronous calls work well when people are already familiar with each other — teams that collaborate nearly every sprint, groups that report to the same manager, people who’ve built enough trust that cameras come on by default and the conversation flows naturally. You can usually tell: if everyone joins and most cameras are on without being asked, that’s a group comfortable enough for remote sync to work. If the meeting opens to a wall of black rectangles, you’ve got a bandwidth problem that video can’t solve.

Kill channels proactively. Archive anything that hasn’t had meaningful activity — not “thanks!”, not emoji reactions, but actual substantive conversation — in thirty days. The graveyard metaphor works because nobody ever cleans up. They just keep creating new channels hoping this one will be different. It won’t. Dead channels don’t just take up sidebar space; they actively dilute the signal. When everything has a channel, nothing has attention.

There are probably rare exceptions to the thirty-day rule. But they’re rarer than you think.

Timebox synchronous interaction, don’t eliminate it. The answer isn’t wall-to-wall meetings. It’s short, intense, high-bandwidth sessions with the right people. Thirty minutes of focused real-time discussion with three people who own the problem beats a week of async threads copied to twelve people who don’t.

A couple of tactical tips that sound small but compound: if you have several recurring meetings with the same audience, put them back-to-back. If one finishes early, start the next one early. You’ll be amazed how much dead time this eliminates. And default your meeting slots to thirty minutes, not an hour. Schedule a one-hour meeting and it finishes in forty-five minutes? People fill the remaining time with filler. Restrict the time and people optimise naturally through the pressure of the constraint.

Measure communication outcomes, not activity. Stop counting messages sent or channels created. Those are vanity metrics for collaboration theatre. Start measuring time-to-decision — how long does it take from “we need to decide X” to “X is decided and everyone understands why”? Track how often decisions get revisited because alignment wasn’t real. Count how many DM side-channels exist for topics that supposedly have a “proper” channel — that gap between the official channel and the shadow channel is a direct measure of your communication culture’s dysfunction.

And for the love of shipping software, document outcomes outside of Slack. Create a bot that summarises decisions and pushes them to your documentation platform. AI is genuinely excellent at this — extracting signal from noise, summarising thread conclusions, creating durable records from ephemeral conversations. Use it.

The Anxiety Management System

Here’s the provocation I’ll leave you with: your Slack workspace isn’t a communication platform. It’s an anxiety management system.

People post to feel like they’ve communicated. People read to feel like they’re informed. Neither is actually true, and the quiet loneliness of async-first work is the emotional tax of maintaining that fiction. We’ve built organisations where hundreds of people can be “connected” all day and still feel profoundly isolated — where the busiest channels have the least alignment, and the most important decisions happen in DMs that half the team never sees.

The Agile Manifesto told us to value individuals and interactions. Somewhere along the way, we decided that “interactions” could be replaced with message timestamps and read receipts. They can’t. The most productive engineering work I’ve ever seen — and I’ve been doing this across continents for a long time — happens when smart people are in the same room, uncomfortable, arguing productively, and building the shared understanding that no amount of threaded messages can replicate.

Your Slack channels are dying. Most of them were never really alive. The question isn’t how to resurrect them — it’s whether you have the courage to acknowledge what they can’t do and invest in what actually works.

Now, if you’ll excuse me, I need to go archive about forty channels. The last message in #cross-team-alignment is a thumbs-up emoji from October. I think it’s time.