The Slack channel you didn't know you needed.

Process · 4 min read

A client once looked at me on the first call and said "What's Slack?" with complete sincerity. Another one told me he uses WhatsApp for everything, work included, and couldn't imagine needing another messaging app.

This is normal. Most people I work with haven't touched Slack before. They're not in tech. They're tradies, educators, health professionals, small business owners. They don't live in productivity tools.

But once we set up a shared channel, something shifts. And by the end of the project, most of them tell me it was one of the most useful things about the whole process.

One channel replaces a dozen meetings

The biggest change is what doesn't need to be a meeting anymore. A quick question about a button label? Drop it in the channel. A screenshot of a competitor's app you saw? Share it with a one line note. A decision about whether to include a feature? Talk it through in thread and move on.

Without Slack, every small question becomes either a meeting or a forgotten email. With it, the project keeps moving between meetings. Decisions happen faster. Context stays intact. And nobody has to schedule a 30 minute call to answer a yes or no question.

Research from a study of 61,000 Microsoft employees found that teams who shifted to async communication didn't lose productivity. They replaced synchronous meetings with messages and the work still got done. That's exactly what I see with clients.

The channel becomes the project's memory

Here's the part nobody expects. Three months into the project, when a question comes up about why a design decision was made, the answer is sitting in the Slack channel. Searchable. Timestamped. With the original context still attached.

Compare that to a verbal conversation in a meeting that nobody wrote down. Or a WhatsApp thread buried between grocery lists and group chat memes. The channel isn't just communication. It's documentation that writes itself.

I've had clients scroll back through their channel months later and say "oh, that's why we decided that." That kind of recall saves time and avoids revisiting decisions that were already made.

You don't need more meetings

Most clients think progress happens in meetings. And meetings are important for alignment, design reviews, and big decisions. But the real momentum happens between meetings. It happens in the quick exchanges, the shared links, the "just saw this and thought of the app" messages.

You don't need more meetings. You need one good channel. It takes about ten minutes to set up, and once you get the hang of it, you'll wonder how you ever managed a project without it.

Sources
The Effects of Remote Work on Collaboration (Yang et al., 2022, Nature Human Behaviour) - Study of 61,000 Microsoft employees found that async communication replaced many meetings without reducing productivity.

Related blog posts:

What happens on the first call →

Send the deck before the meeting →

Your timeline is wrong →