Perks and Pitfalls of Building a Remote First Team
summary
Company grows to ~60 people with about 60% remote, an 11‑person umbrella team spanning four time zones and five countries, and uses Donut plus Slack channels like celebrate and thanks to build ties. Practices that work: enforce company remote days (Tues/Thurs), give regional teams clear authority to act (zap a customer during incidents), hire contractors where local employment law is hard, and insist engineers document more: longer PRs, project docs and explicit urgency flags to avoid blockers and burnout.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:45Why build a remote first team
- 3:16Perks of being remote
- 4:37Pitfalls
- 5:55Regional Autonomy
- 7:31Cross Teamwork
- 9:11Ignore Things
- 11:23Document More
- 14:23Long Term Sustainability
- 16:19Unhealthy Remote Culture
- 18:15Trust People Not Characters
- 20:23Techniques
- 25:20Autonomy
- 31:42QA
