Teams That Propel People Forward
summary
Argues teams can triple impact per engineer by changing coaching, handoffs and permission to experiment; gives concrete wins — one product org ships 3–4x faster after stopping handoff fights, juniors level up to mid in 6–8 months with focused mentoring, and small teams (dozens) built WhatsApp/Instagram-scale products. Recommends specific practices: mandate mentoring schedules, allocate slack for experiments (not just annual hackathons), measure qualitative milestones, and let engineers own features and mistakes.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:00What are we talking about
- 3:03Flashback
- 5:14Apollo 11 Control Room
- 7:21Whats stopping you
- 8:20Selffulfilling prophecy
- 9:22The daily battle
- 10:12Optimizing for growth
- 11:11Heroes
- 12:32Triple Impact
- 15:35Every Line of Code Matters
- 16:20Maximize Creativity
- 18:02The Most Important Thing
- 18:56Management is a Real Profession
- 20:37Management is not about reaching the deadline
- 22:19We need to become more relaxed about mistakes
- 23:47Hackathons are like a hack
- 26:50Create atmospheres that push people forward
- 29:02Direct connection to the product
- 32:24Speak up
- 34:43Persistence
- 37:17Experimentation
- 38:48Measuring Growth
- 39:46Team of Heroes
- 40:33Create a small atmosphere
- 42:57Gift
related talks
46mLeading with Radical Transparency: Empowering Product Teams
28mThe One Value That Matters: Trust
45m"Moving Fast at Scale"
38mHow a Culture of Mentorship and Collaboration Makes You Grow 10x Faster
32mDeveloper productivity 2.0
42mBuilding a Strong Engineering Culture – Stacy Devino
44mThe Way of the Mentor
46mTechnical Leadership and Empowered Teams