Cracking the cadence of your software engineering 1:1s
summary
Claims concrete practices: run weekly 45-minute personal time per direct, keep a shared one-on-one doc with agenda and a follow-ups section, and use Tasks/Reminders on calendar. Measure with a five-question scorecard (did the report do most of the talking alignment on takeaways renewed motivation shared action items cross-checking claims). Managers report fewer bugs and faster shipping after adopting these rhythms, and backchanneling (verify with others) prevents acting on a single skewed perspective.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:00Meet Alexandra
- 1:30Meet Quesi
- 3:20Meet Zest
- 4:00Meet Adrienne
- 6:45Adriennes weekly meetings
- 8:35Alexanders 1s
- 13:45The Scorecard
- 19:15Bringing 1s
- 26:27Have a conversation that matters
- 27:48Establish psychological safety
- 31:36Establish traditions
- 32:40Recap
- 36:40Scheduling recurring meetings
- 38:00Being emotionally invested
- 39:55Scheduling
- 41:37The best version of yourself
- 43:14Trusting people
related talks
11mCrafting effective 1:1s for distributed teams
11mHow to talk to everyone
33mThe Care and Feeding of Software Engineers
27mDebugging the most critical relationship in your work life
41mDesigning your 1:1 - The most important meeting in your career
34mBuilding a Culture For Developer Productivity
23mManaging diverse engineers for high-impact deliveries
31mHarmonizing Across Product & Engineering (Cross Team Collab)