Mike Knoop on Product and Design Processes for Remote Teams with Kevin Hale

TL;DR

Zapier grew from a startup weekend project to a 200‑person fully remote company by making remote work’s necessary cultural and process changes — explicit communication bandwidth rules, default to action, written async updates, and internal tools — which ultimately make the company stronger overall.

Key insights

• Remote companies must be explicit about when to “raise the bandwidth” from text (Slack) to video calls; a key signal is the “many people are typing” message in Slack — at that point jump on a Zoom cal
• Setting a 15‑minute limit on text discussions and deferring unresolved topics to a weekly Friday meeting killed 90% of unnecessary debates because people resolved them after sleeping on it.
• Default to action is the #1 value at Zapier because in a remote company you cannot tap someone on the shoulder; an employee who waits to be unblocked will fail.