A Clear-Eyed Look at Distributed Teams
summary
Argues that success depends on concrete choices not slogans: commit to culture and buy good gear (Slack, Jira, ScreenHero, quality cameras), staff a critical mass — ~25–50% remote, and budget for travel (plan 4 trips/year per remote hire). Measure results by output not presence, prefer video, aim for 3–4 hours timezone overlap, and document decisions. Cites building a team from ~12 to 100+ engineers, round‑the‑clock ops coverage, higher retention and engagement, and practical tradeoffs that actually work.
AI-written summary · about
chapters (13)
- 0:00Start
- 4:05Make a Commitment
- 4:50But how do you build company culture when you are not working "shoulder to shoulder"?
- 6:12Use proper tools
- 7:18Critical mass
- 8:40Remote leadership
- 11:20Treat on-site and remote employees fairly
- 14:10Intentional vs accidental and implicit communication
- 20:03THE BEST! TOOL FOR THE JOB!
- 23:54Watch the work product, not the worker
- 25:21Know the law
- 26:09Understand and control your budget
- 29:11Start with the recruiting process
related talks
33mTips for Managing a Widely Distributed Team
32mHow to Be a High Performing Distributed Agile Team
27m"Thriving in a Connected World"
44mThe Keys to Working Remotely
34mBecoming a team, one pixel at a time
56mMental Health and Working Remote
09mBecoming a team, one pixel at a time (interview)
06mIgnite: Effective Remote Workers