Distributed Leadership
summary
Experience at GitHub (employee #50, 2011–2018) yields concrete tactics: use write the plan as a PR in a git repo so decisions are diffable, insist everything should have a URL, and run follow-the-sun on-call rotations to avoid waking people. Ship chatops (deploy from chat 30×/day), build low-noise channels for key updates, favor async docs over meetings, use RACI for decisions, automate linters and reviews, and accept that a teletype/live‑share style tool helps but productizing culture often fails.
AI-written summary · about
chapters (11)
- 0:00Distributed leadership intro
- 2:59Why distributed teams matter
- 6:11Challenges of distributed leadership
- 14:13Communication tactics
- 23:59Building social cohesion remotely
- 30:46Reducing sync meetings
- 37:29Unblocking across time zones
- 41:02Work-life balance
- 45:37Decision-making in distributed teams
- 47:03Cultural factors for success
- 47:25Q&A
related talks
59mTech leadership, one year after
01h 06mLeading successful remote teams
32mCode First, Ask Questions Later
42mHow Github (No Longer) Works
47mDistributed - of Systems & Teams
08mHow to run distributed teams
34mKEYNOTE: Software Development in Distributed Teams 🧭
46mLeadership for Engineering Teams in Remote Work Era | Panel Discussion