Team communication: messaging and async
The hidden cost of badly tuned communication
When every message demands an instant reply, no one does deep work. Conversely, when everything goes through email, the team answers in hours instead of minutes for what truly matters. The right setting fits in one sentence: the right channel for the right level of urgency. This chapter covers the tools to talk to your team without interrupting it constantly.
Team messaging: Slack and its alternatives
Team messaging replaces internal email: threads by topic, search, integrations. The options by budget:
- Slack is the reference: channels per project, countless integrations, powerful search. Free plan limited to 90 days of history, then ≈ $7-8/user/month.
- Discord is free, solid for a community or a small team comfortable with its interface; less "corporate" but unbeatable on cost.
- Google Chat or Microsoft Teams make sense if the team already lives in Google Workspace or Microsoft 365 (included in the subscription).
Which tool for which context
| Context | Recommended tool | Indicative cost |
|---|---|---|
| Product/tech team, many integrations | Slack | free → $8/u/mo |
| Zero budget, team or community | Discord | free |
| Already on Google Workspace | Google Chat | included |
| Already on Microsoft 365 | Teams | included |
Structuring channels so you don't drown
A messy Slack is as painful as a flooded inbox. A few rules that hold over time:
- One channel per project or function, not one channel per mood.
- Clear prefixes:
proj-,team-,random-to find your way at a glance. - Important decisions don't stay in the thread: copy them into the knowledge base (see chapter 3).
- Use threads to reply, so you don't flood the main channel.
:::tip[Tip: pinning isn't enough] A pinned message gets lost as soon as there are ten. For a decision to survive, it must move from chat to a durable document. Chat is a river, not an archive. :::
Async video: Loom and the recorded demo
Explaining a bug, showing a mockup or giving detailed feedback takes five minutes on a narrated video versus twenty in text — and without scheduling a meeting. Loom (generous free plan, then ≈ $12.50/month) records screen + voice and generates a shareable link. Alternatives: Vidyard, or simply the native macOS/Windows screen recorder dropped into a Drive.
A three-minute Loom often replaces a thirty-message thread and a sync-up meeting.
Setting the culture, not just the tool
The tool fixes nothing without a few shared conventions. The most useful:
- Expected response time: chat isn't texting. You reply within the half-day, not the minute.
- Presence status: signal when you're in deep focus ("focus", notifications off).
- Write to be read without you: context + clear request + deadline, so people can answer without a follow-up.
The psychology here is attentional load: every notification fragments concentration. Reducing interruptions isn't comfort, it's recovered work time.
The "everything on chat" trap
Chat creates the illusion of organization because it's alive. But a task announced in a message isn't a tracked task, and a decision drowned in a thread is a lost decision. Chat is for talking, not for remembering or tracking work — those roles belong to the knowledge base and the project management tool.
Key takeaways
Set up team messaging (Slack if many integrations, Discord if zero budget, Teams/Google Chat if already in the suite), structure it into clear channels, and switch to async video (Loom) whenever an explanation deserves better than a wall of text. Tune the culture — response time, focus status, self-sufficient messages — to protect concentration. And remember chat talks but doesn't remember: the team's memory is the topic of the next chapter.