Tools do not create bad communication; they amplify whatever norms a team already has. A channel can be a calm, searchable record of work or a firehose of fragments, and the difference is almost entirely behavioural. These are the norms that separate the two, written down so they can be adopted deliberately instead of argued about later.
Thread Replies, Always
The single highest-impact norm: reply inside the post, not as a new post. Threads keep a topic and its discussion in one collapsible place; unthreaded replies scatter one conversation across the channel and bury unrelated topics between its fragments. Teams that enforce threading for one month never go back.
Write Messages People Can Answer
- Lead with the request or question; context after, not before.
- One message, complete — five consecutive single-line messages produce five notifications and zero clarity.
- Include the deadline and the decision needed: "by Thursday, approve option A or B" beats "thoughts?".
- Link, do not paste: a link to the document stays current; a pasted excerpt rots the moment the document changes.
Response-Time Expectations, Stated Out Loud
Much chat anxiety is unspoken assumption: one colleague expects minutes, another considers a day prompt. Publish the team's contract — for example, mentions answered within four working hours, channel posts within one working day, everything else asynchronous by design. Once written, urgency becomes a choice rather than a default, and do-not-disturb stops feeling like defiance.
Reactions are answers
Agree that an acknowledgement reaction means "seen, no objection" and silence means nothing at all. This tiny convention removes entire waves of "just checking you saw this" follow-ups. It only works if the meaning is shared, so write it into the channel description.
Meeting Culture Belongs Here Too
No agenda, no attendance — a norm that sounds harsh until you count the hours it returns. End every meeting with the five-minute written follow-up in the owning channel. Cancel meetings where the agenda resolved itself in chat; announcing the cancellation publicly rewards the chat habit that made it possible.
Onboarding Newcomers Kindly
- Post a pinned welcome message: purpose, norms, where decisions and files live.
- Assign a buddy for week-one questions so newcomers do not have to guess whom to interrupt.
- When a newcomer breaks a norm, correct in private, once, with the reason — public corrections teach everyone to write less, which is the opposite of the goal.
- Revisit norms quarterly; a team of six and the same team at sixty need different rules.
When Norms Collide With Reality
Incidents, launches and crises legitimately break every rule above: unthreaded urgency, rapid fragments, calls without agendas. That is fine — norms describe the weather, not the storm. What matters is that the team knows the difference, returns to the norms afterwards, and writes down anything the storm taught them.
Etiquette prevents most confusion; the final chapter handles the rest — the everyday failures and fixes, from sign-in loops to missing files, that support desks see every week.
