Article · 18 min read

Asynchronous Communication: The Real Reason Why Remote Workers Are More Productive

Doist · Doist / Twist Free Beginner

Doist runs a 100+ person team across every time zone with 80-90% of communication written, and this piece is their playbook stated plainly. It hands you the two norms your answer calls for: a concrete response-time rule (they expect replies within 24 hours, not 24 seconds) and a clear meeting-vs-thread decision (live only for sensitive feedback, brainstorming with real unknowns, and crises; everything else is written). It even scripts how to decline unnecessary meetings and how to judge people on output instead of how fast they answer Slack.

  • Set an explicit response window (Doist uses 24 hours) so nobody feels they must watch notifications, which is what lets a person in another city work without waiting on you.
  • Judge output, not responsiveness: measuring people by reply speed quietly rebuilds the always-on culture you are trying to kill.
  • Use the Direct Responsible Individual model so written decisions have one clear owner and threads resolve instead of drifting.

The question it answers

  1. How do I keep a distributed team genuinely async so people in different time zones and cities are not always waiting on me?

Read with it

  1. 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... The GitLab Handbook Article · 25 min read Asynchronous communication for remote work GitLab
  2. Newport diagnoses exactly why distributed teams end up always waiting on the founder: the hyperactive hive mind of ad hoc Slack... calnewport.com Essay · 12 min read On Productivity and Remote Work Cal Newport
eChai Partner Brands The partnership →