Crafting effective 1:1s for distributed teams
summary
Team size is 15 and meetings hit a 10 hour gap so one-on-ones run weekly and serve as the primary health check for people projects and teams. Concrete rules: use a shared document agenda for async notes, keep exactly two windows open (video and notes), meet with camera on, and start with a traffic light check-in. A concrete outcome: an engineer moved off a vague telemetry project onto infrastructure and is now thriving, showing follow-ups and ownership actually change outcomes.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:27The 10 hour gap
- 0:58Mias story
- 2:05Importance of oneonone
- 3:09Communication challenges
- 4:23My goal
- 4:36Guidelines
- 6:44Checkin
- 7:37Discussion
- 9:16Sharing excitement
- 9:54Follow up
related talks
46mCracking the cadence of your software engineering 1:1s
19mOops I'm a Manager - On More Effective 1-on-1 Meetings
44mHow To Lead a Remote Team
23mManaging diverse engineers for high-impact deliveries
27mLost on an Island: Building Remote Collaboration in Cross-Continent Distributed Teams
31mHarmonizing Across Product & Engineering (Cross Team Collab)
26mRemote-first teams work better
31mManaging Meetings Without Succumbing to Zoom Fatigue