Remote team communication: ground rules that work

Remote team communication works best when everyone knows which tool to use, how fast to reply, and where decisions are written down. Teams that skip these rules end up with long chat threads, missed messages and meetings nobody needed. A few plain agreements fix most of it.

This guide gives six ground rules you can adopt this week. They suit a team of five or a team of fifty, in one city or spread across Asia-Pacific.

Why the rules matter

In an office, people pick up context by sitting near each other. A remote team loses that. Nobody sees who is busy, who is stuck or what was decided in the hallway. Messages have to do all of that work.

Buffer's 2019 State of Remote Work survey asked 2,471 remote workers about their experience. Nearly all of them, 99 percent, said they would like to work remotely at least some of the time for the rest of their careers. The same report says many remote workers still struggle with unplugging, loneliness and communicating. Wanting remote work is not the same as having the habits to make it run well. Those habits are a leader's job to set.

Sources: Buffer, "State of Remote Work 2019" (buffer.com/state-of-remote-work-2019).

Rule 1: Write it down first

Make writing the default. A decision that lives only in a call is lost to anyone who missed it, and in a team spread across time zones, somebody always misses it.

GitLab, a company that has no offices, publishes its own handbook on the open web. Its approach is simple. Write the process or decision in one shared place, then point people to it. When someone asks a question that is already answered, you send the link. That saves the answer for the next person too.

You can copy this on a small scale. Keep one shared page for team rules, one for how projects run, and one log of decisions. Each entry needs a date, an owner and a short reason.

Sources: GitLab, "All-Remote" culture pages in the public GitLab handbook (about.gitlab.com/company/culture/all-remote/).

Rule 2: Give each channel one job

Most communication problems come from using one channel for everything. Agree on a short list and post it where all can see it.

Chat: quick questions and light updates. Not for decisions that matter next month.
Email: messages to people outside the team, and longer notes that need a clear subject line.
Shared documents or a project tool: tasks, plans and decisions. This is the record.
Video: hard topics, sensitive feedback and anything that has gone back and forth more than a few times.
Phone: true emergencies only, with a listed number.

When a chat thread turns into a debate, stop and move it to a call. When the call ends, write the result in the shared record. That last step is the one teams forget.

Rule 3: Set reply times, and say them out loud

Silence is the most stressful thing in a remote team. Is the other person busy, off or ignoring you? Remove the guessing with a simple promise.

A common pattern is to reply to chat within a few hours in working time, and to email within one working day. Urgent items get a clear tag such as "needs answer today". Everything else can wait. Write the promise in your team page and follow it yourself first, because people copy what the leader does.

Time zones need their own note. If your team covers Singapore, Jakarta and Sydney, pick a few shared hours for live talks. Keep the rest of the day free of meetings. Rotate the awkward early or late slots so the same people do not always pay for them.

Rule 4: Make messages easy to act on

A good remote message can be read once and acted on without a follow-up. Before you send, check four things.

What do you want from the reader: a decision, an answer or just awareness?
By when?
What background do they need? Add the link, not just a mention.
Who else must see it?

Put the request in the first line. Use short sentences. Use a clear subject or first line, so a busy person can sort it in two seconds. Do not assume tone will come across in text. A joke that works at a desk can read as sharp on a screen, so be a little warmer than you think you need to be.

Rule 5: Run video calls with a purpose

Video is for things that need voices and faces. Keep it short and send an agenda ahead of time. Ask each person to read the notes before the call, so the time is for talking and deciding.

Ask people to turn cameras on when they can, since faces help a distributed team feel like a team. Do not make it a test of loyalty, though. Bandwidth varies across the region, and some homes are not quiet.

Name one person to take notes and one to keep time. End every call by reading out the actions: who does what, by when. Post those in the shared record within the hour.

Also leave room for non-work talk. Five minutes at the start of a weekly call, or a chat channel for casual topics, does the job the coffee machine used to do. It also helps with the loneliness that Buffer's survey flagged.

Rule 6: Protect time off

Remote work blurs the line between work and home. Buffer's survey lists unplugging among the top struggles, so leaders need to model good limits.

Agree on working hours and show them in each person's chat status or calendar. Avoid sending non-urgent messages late at night. If you must write at that hour, schedule the message to go out in the morning. Tell the team clearly that nobody has to answer outside their stated hours unless it is a real emergency.

The book Remote, by Jason Fried and David Heinemeier Hansson of Basecamp, published in 2013, makes a related point. Work can happen anywhere, but people still need clear expectations and room to switch off.

Sources: Buffer, "State of Remote Work 2019"; Basecamp, "REMOTE: Office Not Required" by Jason Fried and David Heinemeier Hansson, 2013 (basecamp.com/books/remote).

A one-page starter agreement

Put these lines at the top of your team page and ask everyone to agree:

We write decisions down in one shared place.
Each channel has one job, and we follow the list.
We reply to chat within a few working hours and to email within one working day.
Every message states what is needed and by when.
Calls have an agenda, a note taker and a list of actions at the end.
We respect each other's working hours and time zones.

Review the page after one month. Ask the team what is working and what is not, then change a rule or two. Good remote team communication is not a fixed system. It is a short set of habits that the team keeps tuning together.

Sources

Buffer, State of Remote Work 2019: buffer.com/state-of-remote-work-2019
GitLab, All-Remote culture pages: about.gitlab.com/company/culture/all-remote/
Basecamp, REMOTE book page: basecamp.com/books/remote