<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.


🙋🏼 Tips for effective communication

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

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


🕰️ 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.


📗 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.


Main Article - Working Async at Remote

🤝 Meetings at Remote

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

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.