Back to Blog Home

5 ways to improve communication for remote teams

communication for remote teams

We recommend four habits for remote-team communication: keep work in public channels, put anything people must see in the channel instead of a thread, move to a call after five minutes of typing on the same issue, and write the standup before the call so the meeting only has to cover roadblocks. Kipwise is a 100% remote team (we explained why we decided to work remotely as co-founders). The sections below cover chat, calls, meetings, project tools and knowledge.

1. Communication best practices for instant chat tools

Slack is the example here (we have plenty of Slack tips too), and the same rules apply in other chat tools. Instant chat seems easy, but using it badly causes its own communication problems.

Default to public channels instead of direct messages for transparency

Make public channels the default. Everyone can follow progress on different tasks, teammates can jump in and help, and interdependent tasks don’t end up with important background hidden in direct or private messages. Write down the few things that do belong in a DM, such as pay, performance feedback and personal matters, so the rule doesn’t push sensitive topics into a channel.

You might worry about too many messages to catch up with. That is where better organizing your Slack channels comes in: group conversations by function, project and topic so teammates can focus on the channels that matter to them.

Nest messages around threads to keep conversations easy to follow

Threads matter most for remote teams, because teammates in different time zones read the channel at different times. Without them, other topics jump in and it is hard to tell which reply belongs to which discussion. A thread is also quiet by design: @channel and @here do not notify anyone when they are used in a thread. So keep the discussion in the thread, and put anything people must see in the channel itself, either as a new message or by sending the reply back to the channel with the checkbox under the reply box.

Use @channel wisely to reduce noise for teammates

@channel notifies everyone in a channel, while @here notifies only the people who are active at that moment. Reserve both for an important announcement or an urgent matter that everyone needs to read. In channels with six or more members, Slack asks you to confirm before it sends either.

Use status and profile to communicate availability

Unlike onsite workers who share an office, remote teammates can’t easily tell who is on vacation or when others are working. Set your status when you are away, and use your profile to show your time zone and typical working hours.

Other than Slack, some other great team chat tools include Microsoft Teams and Troop Messenger.

2. Don’t be reluctant to jump on calls

Instant chat is good for quick updates, but a phone or video call is often still better for discussing complex issues. A tool such as Zoom adds screen sharing, which makes complex issues much more efficient to solve.

The 5-min rule

If you find yourself typing on Slack for more than 5 minutes on the same issue, jump on a call instead. Afterwards, type a quick summary of the outcome to keep everyone on the same page. It also makes the issue easier to trace back using search in the future.

3. Regular face-to-face meetings to check on progress and ask for feedback

Regular voice or video calls also help create connections in a remote team. Emotion and expression come through much better than in text, and email and instant messages can’t always compare.

Daily standup meeting to align goals and address roadblocks

Have teammates take turns answering 3 questions:

  • What have you done since the last meeting?
  • What will you do until the next meeting?
  • Is there any roadblock?

Phrase them as “since the last meeting” and “until the next meeting”. With teammates in different time zones, “yesterday” and “today” mean different things, especially when the daily meeting falls in the middle of someone’s work day.

Ask everyone to type their answers in a channel such as #daily-updates before the call (a Slack reminder in the channel helps people remember). Then the call only has to cover roadblocks, and on a day when nobody lists one you can skip it. If no time fits everyone’s working day, keep the standup written and drop the call.

Check out our daily standup meeting template with tips on how to keep the daily standup meeting focused and effective.

Biweekly all-team meeting for big picture updates

A longer biweekly meeting covers the big picture. The business team shares high-level metrics such as revenue, number of new signups, major conversion ratios and important leads in the pipeline, and the product team lead gives a brief overview of what has launched recently and what is coming. For a startup that moves fast, it is also the place for the CEO to share changes in short-term goals and direction.

Biweekly product team sprint retrospective

The product team, designers included, can hold a retrospective every two weeks: how the past two weeks went, what can be improved and the priorities for the coming two weeks. The engineers can then stay longer to discuss in-depth technical issues.

Monthly 1-on-1 with managers

Some things are hard to share in a team meeting where everyone is present, so meet one-on-one every month. The manager asks for the teammate’s feedback and gives feedback on how the teammate can improve.

4. Tips on using project management tools

Project management tools help remote teams communicate more effectively: you can group conversations around specific tasks and projects in an organized way and track progress more efficiently.

Trello + Slack power-ups

Trello integrates with Slack, so you can get notifications in Slack when there is activity on your Trello cards or boards (this needs the Slack Power-Up as well as the Trello app for Slack, and you can customize the type of activities you are notified about).

Planyway for Trello

The Planyway add-on turns a Trello board into calendar, timeline or Gantt-like views, and it can connect several boards for a view across teams and projects, which makes it easier to coordinate your team schedule and see who is doing what and when.

5. Neatly organize internal knowledge using knowledge management tools

In a remote setting, you can’t just tap someone on the shoulder to ask. With time zone differences, you might wait a long time for an answer if important knowledge is not organized in an easily accessible way.

Make a habit of documenting team knowledge in an organized fashion. We might be biased, but Kipwise fits because it’s integrated with the tools that remote teams love, easy to use, and has built-in workflows to keep your content accurate and fresh.

If you need more tips on building an internal knowledge hub, check out our blog post on how to create an effective internal knowledge base.

Related posts

Your team’s knowledge, answered in Slack

Add the Kipwise Agent. It answers from your pages with the source, and asks before it changes anything. 7-day trial, no card needed.