Leading successful remote teams
summary
Practical playbook for distributed engineering: clear policies (remote only, minimum enforced leave + 7 weeks recommended after unlimited leave backfired), lightweight ceremony (no daily standups, one 45‑minute Monday all‑hands), tooling and conventions (Google Workspace, Slack, GitHub, ClickUp replacing Trello), roles (tech leads + lead developers), code hygiene rules (three‑comment rule on code reviews), handling neurodiversity (one‑third self‑identify ADHD) and outcomes: 80% via reputation and average retention over four years.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 9:45Failed remote team lessons
- 18:31Building remote-first company
- 24:31Core principles for remote teams
- 35:46Team structure and tools
- 42:45Remote mentorship and onboarding
- 51:53Health, wellbeing, and neurodiversity
- 1:04:54Key takeaways and advice
related talks
57mLessons from {distributed,remote,virtual} communities and companies
01h 10mLeading successful remote teams
46mLeadership for Engineering Teams in Remote Work Era | Panel Discussion
44mHow To Lead a Remote Team
50mDistributed Leadership
55mWorking Distributed - How Does It Even Work?
39mPerks and Pitfalls of Building a Remote First Team
52mRemote Working Approaches That Worked (And Some That Didn’t)