Essay · 12 min read

On Productivity and Remote Work

Cal Newport · calnewport.com Free Intermediate

Newport diagnoses exactly why distributed teams end up always waiting on the founder: the hyperactive hive mind of ad hoc Slack pings has no structure, so every decision routes back through one busy person. He cites a University of Chicago study where remote workers added 30% more hours for flat output, and argues the fix is not more meetings but protocol-driven collaboration (shared task boards, defined workflows) that protects deep work. Read this to decide what genuinely deserves a live meeting versus a written thread, and why unstructured messaging quietly becomes the bottleneck.

  • Unstructured ad hoc messaging is the bottleneck: without a defined protocol, every question routes back to you and decisions drag.
  • Remote work does not lower productivity; keeping broken, meeting-and-ping-heavy collaboration habits does.
  • Replace the hive mind with structured workflows (task boards, Kanban, clear protocols) so work moves on rails instead of through your inbox.
Open on calnewport.com ↗

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. Doist runs a 100+ person team across every time zone with 80-90% of communication written, and this piece is their playbook... Doist / Twist Article · 18 min read Asynchronous Communication: The Real Reason Why Remote Workers Are More Productive Doist
eChai Partner Brands The partnership →