Slack and Async: Communication Norms in Remote Teams

In remote and hybrid tech teams, most communication is not in meetings. It is written, in Slack, Discord, Linear, Notion, or email. This is called async (asynchronous) communication: you write once, and people respond when they can, often across time zones. The norms of async are different from email and from live conversation. This lesson teaches the patterns that keep remote teams fast and sane.

Channels versus DMs

Slack and similar tools organize talk into channels (group spaces) and DMs (direct messages). The golden rule of remote teams is: default to public channels.

• Public channels keep knowledge visible. When you ask a question in #engineering, the answer helps everyone, not just you.
• DMs hide information. A question answered in a DM benefits only two people.

Use DMs for private or sensitive topics (performance, personal matters, confidential projects). For nearly everything work-related, post in the channel. The team's shared memory depends on it.

Threading

A thread is a reply chain attached to a specific message. Threading is the single most important habit in a busy channel.

• In-thread reply: the conversation stays attached to its topic. The main channel stays clean.
• Main-channel reply: the message appears for everyone. The channel fills with side conversations.

Rule of thumb: if your reply is about a specific message, reply in the thread. Post in the main channel only for things the whole channel needs to see.

Writing async updates

Async means your message must stand alone. The reader should be able to understand and act without a live conversation. A good async update has three parts:

1. The context : what this is about.
2. The result or question : what happened or what you need.
3. The next step : what should happen now, with a link.

Example:

I finished the payment webhook fix (context). The PR is here: [link] (result). Could someone review it by tomorrow morning your time? (next step)

Notice the time-zone awareness: your time instead of a fixed hour. This is a mark of experienced remote workers.

Channel etiquette

Each channel has a purpose. Respect it.

• #general : company-wide notices. Do not post a bug report here.
• #engineering, #design, #product : team and discipline channels.
• #random, #watercooler : social and off-topic.
• Project channels (#launch-mobile, #billing-fix) : focused on one effort.

Posting in the wrong channel is like shouting in the wrong room. Before you post, ask: is this where the people who care will see it?

Status and presence

Use your status and working hours to signal availability.

• Set a status (in a meeting, heads down, on vacation) so people know when to expect a reply.
• Respect others' working hours. If someone is off, schedule the message for their morning instead of pinging now.
• FYI and no rush tags tell the reader this is not urgent.

Common mistakes

1. Over-messaging. Ten short messages in a row (hi / you there? / quick thing) interrupt more than one clear message. Write one complete message.
2. Hiding decisions in DMs. If a decision affects the team, it belongs in the channel.
3. Treating Slack like email. Slack is for quick, current conversation. Important decisions and long documents belong in email, docs, or tickets, where they can be found later.

Practice

Rewrite this messy Slack burst as one clear async update:

hi you there? quick thing did you see my pr? lmk

A clean version:

Hi Jordan : I opened a PR for the webhook fix: [link]. No rush, but could you take a look by tomorrow afternoon your time? Happy to pair if anything is unclear.

You have now completed the Email Writing Essentials course. You can structure an email, match the register, avoid the top errors, write clear recaps, and communicate well async. In the next course, Conversation Basics, you will take these skills into spoken workplace conversation.