As a distributed company we should be mindful of how we communicate.

Meetings

General guidance

Each meeting should have an agenda. This allows potential participants to prepare and decide whether attendance is required. Any participant can add items to the agenda, please prefix your item with your name or initials to communicate who's going to talk and lead the discussion. Adding new items to the agenda while the meeting is started is good practice and can be leveraged to keep the currently discussed item focussed and on-rails.

During the meeting

Meetings start on time by the person with the first item on the agenda, verbalize and discuss the item. Once done, hand over to the owner of the next agenda item.

During the meeting notes should be taken in an inline fashion. Non-participants can then read the agenda after the meeting and are up-to-date without having to scroll to a notes section.

Coffee calls

Coffee calls are social of nature and thus are the exception to the rule that each meeting should have an agenda. If you want to be matched to a random team member every two weeks for a coffee call, join the #virtual-coffee channel on Slack to be matched automatically.

Asynchronous communication

Communication through different timezones or due to differences in availability requires knowledge to be persistent in sources that are approachable to others and non-ephemeral.

Information should thus be stored in:

  1. Handbook
  2. GitHub issues
  3. Git Repositories pushed to GitHub
  4. Google Drive (Docs / Sheets / etc.)

Don't store information in:

  1. Slack
  2. Figma