How To Lead a Remote Team
summary
Covers leading remote dev teams with concrete routines: daily short check‑ins, weekly one‑on‑ones, and 10-minute meetings to keep momentum; run 5-minute lightning talks to pull quiet members into demos; use Trello/Asana/Notion for weekly planning and avoid build‑week chaos. Suggests informal bonding (play Codenames), carries 10–15 notebooks to track strengths, and insists on early corrective conversations for underperformers so teams stay accountable rather than micromanaged.
AI-written summary · about
chapters (3)
related talks
30mBuilding and Leading Remote Teams
01h 06mLeading successful remote teams
46mLeadership for Engineering Teams in Remote Work Era | Panel Discussion
43mThe remote leader - distant but not removed
49mRemotely Operated - Managing Scattered Teams
36mHow YOUR scrum team can excel in a remote setting
37mBuilding and Maintaining a Remote Team Culture
17mFull Remote: How to Succeed Working as a Team?