<aside> 👋 Communication at Remote At Remote we lean heavily into asynchronous communication. This page should help to provide context as to how we communicate at Remote. We should lean heavily into our values, as well as our DEI principles. We encourage everyone at Remote, regardless of who and how you are communicating to utilise these guidelines to create effective and inclusive daily communication.

</aside>

🙋🏼 Tips for effective communication

When in doubt, always refer back to Remote’s values when communicating with others.

• Aim to use inclusive language, review our examples of inclusive language or contribute to them.
• Always default to posting communications publicly so others can see, learn and contribute to the conversation.
• Create a safe space so other feels comfortable to say ‘I don’t understand, can you explain again?’ Everyone should feel like they belong.
• Be open to different styles of communication. We are a hugely diverse organisation and that is one of our strengths.
• Got questions or feedback? The people team want to hear it. Reach out to #people-help

<aside> 🚫 Remote has a zero-tolerance policy regarding our standards as described above.

</aside>

🕰️ Use UTC when Referencing Time

Use Coordinated Universal Timezones(UTC) as the format for scheduling events and estimated delivery dates. This makes sense for anyone at any time of the day regardless of the timezone.

Examples:

• 👎 Bad: “I will do it this afternoon.” Why: Your afternoon might not be the same as the others.
• ⏲️ Okay: “I will do it later, in 2-3 hours." Why: You are still relying on the other person to read the message at the same time you posted it.
• 💯 **Good: "**I will do it around 18-19 UTC" Why: A message that makes sense for anyone, anywhere.

📗 Preferred Language - English

At Remote we have standardised language to English. It's widely spoken and as close to an "international language" as it's possible to get, being the official language for both sea and air. External communications should be done in US English (en-us), but internally you can speak in which ever variant you're native in or most identify with.

Default to Asynchronous Communication

<aside> 🚆 Always favor asynchronous(async) communication over synchronous(sync) communication. Sync communication is costly, interrupts peoples’ thought processes, and hinders productive execution. When there is a need to use sync methods, ensure it is for the right reasons.

</aside>

Main Article - Working Async at Remote

🤝 Meetings at Remote

<aside> 🚅 Make it really easy for others to contribute.

• Enable others with a Notion doc, a Google form, or something similar to make sure you get what you need AND make it easy for others.

• Set clear expectations. If you need contributions, make that known who you need it from and by what date. E.G Please complete this by Monday 4th.

• Remind people. Don't be afraid to follow-up. Calendar events can also be useful. You could even have checkmarks for each individual person you'd like feedback from. </aside>

• Include Stakeholders, Stick to an Agenda, Take Useful Notes, End with Action Plan

  • Schedule using "speedy meetings" in GCalendar
  • Always have an agenda and adhere to the apportioned time.
  • Take Notes. Information communicated in meetings should not go undocumented. Good meeting notes will distill conversations to essential talking points and action items. Also be sure to include links to any materials or documentation shared.
  • End with an Action Plan. Everyone should know their duties/deliverables before adjourning.

  Main article - How to Run A Meeting

Be Transparent - Communicate in Public as Much as Possible

When using Slack or similar, try to communicate as much as possible in channels that everyone can access rather than private channels. We prime visibility and open dialog.