“We need better communication” is the least actionable sentence in any team retrospective. It describes a symptom — confusion, rework, missed context — without saying what to change. The fixes that actually work are smaller and more mechanical than they sound: they’re about defaults, expectations, and habits, not about people being nicer in chat.
This guide collects the changes that consistently improve day-to-day communication on teams using chat platforms, email, and documents together.
Diagnose before you change anything
Spend one week noticing where communication actually breaks. The recurring patterns are usually one of four:
- Wrong place: decisions made in direct messages that others needed, or threads continuing long after the topic moved.
- Wrong time: people expecting instant replies to non-urgent messages, then burning attention watching for them.
- Wrong shape: walls of text nobody reads, or five-word fragments that require three follow-ups to decode.
- No record: the decision happened, but nobody can find where it was written down.
Pick the pattern that costs your team the most, and fix that one first. Communication habits change one at a time or not at all.
Agree on where each conversation happens
Most confusion starts with routing: the same conversation could plausibly live in chat, email, a document comment, or a meeting. Agree on a simple map and publish it where new hires will see it:
- Public channels — anything a teammate might benefit from seeing. Default to channels, not DMs, unless the content is genuinely personal.
- Direct messages — one-to-one logistics, sensitive or personal topics, quick “are you around?” pings.
- Email — external communication and formal internal announcements that must reach everyone, including people outside the chat platform.
- Document comments — feedback tied to specific sentences and versions, not general discussion.
- Meetings — anything needing real-time back-and-forth, decisions with trade-offs, or emotionally loaded topics.
Write for skimmers
People don’t read chat; they scan it. Fighting that is pointless — writing for it is easy:
- Lead with the ask. First line states what you need and by when. Context follows.
- One message, one topic. Separate threads beat one message with four unrelated questions — each can be answered and searched independently.
- Use bold sparingly for the deadline or the decision, not for emphasis everywhere.
- Link, don’t paste. Point to the document or channel instead of quoting three paragraphs of it.
For longer proposals, write the document first, then share a link with a two-sentence summary. The chat stays navigable; the thinking stays versioned.
Set response expectations
Unstated expectations are where communication friction hides. Agree on rough service levels and make them visible:
- Mentions in a channel during working hours: reply within a few hours.
- Unmentioned messages: read within a day, no reply required.
- Email: within one or two business days.
- Anything marked urgent: use the escalation path — a direct mention, a call — not just the word “urgent” in a message.
The point isn’t policing response times; it’s removing the ambiguity about what silence means. “No reply yet” should mean “probably not seen,” not “possibly ignored.”
Close the loop on decisions
Teams lose hours re-litigating decisions nobody recorded. Make the decision message a small ritual:
- When a conversation reaches a decision, post it in one line: “Decision: we’re shipping the beta on the 14th. Owner: Dana. Reason: dependency on the API release.”
- Post it in the channel where the topic lives, not the one where the discussion drifted.
- Link the decision from the related document or task.
A month later, nobody has to reconstruct the why from forty messages of scrollback. If your team runs recurring meetings, the same ritual closes each one — see Building Repeatable Meeting Workflows for the meeting version.
Make feedback normal
Communication improves when people can say “that channel is too noisy” without it being a complaint about a person. Two habits help:
- Retros include communication. One question every few weeks: “What information did you have to hunt for?” The answers reveal routing problems, not personal failings.
- Correct in private, clarify in public. When something was miscommunicated, clarify in the channel so everyone benefits; save the coaching for one-on-one.
For the written-down version of these agreements, see Creating Clear Internal Communication Guidelines — a one-page charter beats a culture deck nobody opens.
Putting it into practice
Don’t launch five changes at once. Pick the routing map first — it’s the highest-leverage single fix — then add response expectations a week later. Close-the-loop comes third, once the first two habits are boring.
The related guides go deeper on each surface: meeting preparation is covered in Preparing for More Productive Online Meetings, and notification tuning — the receiving side of all this — in Managing Notifications Without Losing Important Updates.