Communication · less scatter, more signal
Choose the right channel for the moment
A message can be clear and still land in the wrong place. Make it easier for teammates to find updates, respond at a sensible pace, and know when something needs attention.
Agree what each channel is for
When every kind of conversation happens everywhere, people compensate by checking everything. Important decisions get buried in fast chat, task details are duplicated in email, and a request sent directly to one colleague becomes invisible to the people who need to act next. A small channel agreement can reduce that hidden work.
Describe the purpose of each place in ordinary terms. For example: a project space holds durable updates and decisions; a task tracker holds owners, status, and next actions; a team chat supports quick coordination that does not need to become permanent; direct messages are for sensitive or genuinely one-to-one matters. The right setup varies, but the distinction should be easy to explain to a new teammate.
For every channel, establish a lightweight expectation: who should read it, how often, what deserves a notification, and what response time is reasonable. Do not confuse a fast platform with a requirement to reply instantly. A message marked urgent should have a defined meaning and a known route; otherwise urgency becomes background noise.
Write messages that travel well
Async communication needs enough context to make a useful response possible. Put the ask or decision near the start, identify the deadline only when one exists, and include the relevant link or reference. If the topic is complex, state what has already been considered and what remains uncertain. A complete message saves a colleague from waking up to a chain of follow-up questions.
Be explicit about whether you need a reply, a review, or simply want to keep people informed. “For awareness” and “Please choose A or B by Thursday” ask for different kinds of attention. When a decision is made, record the conclusion and the reason in the agreed source of truth. A short summary is more findable than expecting future readers to infer a decision from a long conversation.
Coordinate handoffs with care
Different time zones can make a brief handoff feel like a full stop. Leave the next person a concise status: what has happened, what remains, what choice is needed, and who is responsible for the next move. Include a link to the current working document rather than several competing versions. If you are waiting on something, say so plainly and identify whether the other person needs to act.
Do not treat presence indicators as a reliable measure of commitment. People may be focused, caring for family, working a different schedule, or dealing with connectivity limits. Publish team overlap hours and use asynchronous updates for work that can wait. Make room for the occasional synchronous conversation, but avoid building a culture where a person must be online at all times to stay in the loop.
Good channel habits let people disconnect without losing the thread.
Build a compact channel agreement
- Give each platform one clear primary purpose.
- Separate urgency from ordinary response expectations.
- Record decisions in a durable, agreed location.
- Use direct messages thoughtfully; move shared work into a shared space.
- Revisit the agreement when new tools or recurring confusion appear.
A channel policy should help people, not police them. Ask teammates where important information is hard to find and where interruptions are most costly. Adjust the rules together, explain the reason for each change, and model the behavior in everyday work.