Explore / Build the product / Product management

Article · 25 min read · Starting Up

Asynchronous communication for remote work

This is the operating manual behind the answer's core rule: don't run a remote team on vibes. GitLab runs 1,600+ people across 60+ countries entirely on written, handbook-first, async-default communication, and this page hands you the exact norms to copy from your first hire: document the decision not just the outcome, put questions in a public channel instead of a DM, and treat working-hours overlap and response time as explicit agreements. It is the rare playbook written by a company that actually lives it at scale, so you can lift the practices wholesale into a three-person team.

GitLab · The GitLab Handbook · Article · 25 min read

The answers it serves4 answers

  1. How do product teams keep a consistent shipping rhythm as they grow? Starting Up
  2. How do I keep an offshore or remote dev team accountable across time zones? Starting Up
  3. How do I keep a distributed team genuinely async so people in different time zones and cities are not always waiting on me? Starting Up
  4. How do I hire remotely across Indian cities and manage a distributed first team well? Starting Up