Building a High-Performance Team is Everyone's Job
summary
A startup migrates an old Drupal/PHP site into Java microservices, cuts deploy time from weekly multihour releases to daily deploys, and measures immediate gains in autonomy and fewer release bottlenecks. Engineering career ladders are created and open sourced to fix pay and role ambiguity. Cultural work—introducing blameless postmortems, practicing apology, and building psychological safety per Google's findings—shifts a team from fear to trust and raises overall delivery speed and willingness to take measured risks.
AI-written summary · about
chapters (35)
- 0:00Intro
- 0:45Scaling
- 5:29What is Rent the Runway
- 7:00What Im like as a handson manager
- 7:32A cultural segfault
- 9:07Creating a culture of fear
- 9:41A wakeup call
- 10:04A culture of trust
- 11:03The elements of scaling
- 12:42Speed
- 15:21Engineers like to ship
- 16:02Frequent easy releases
- 17:17Be impatient
- 17:46Structure
- 18:22Learning Transparency
- 19:05Learning from Failure
- 19:38Tacoma Narrows Bridge
- 20:28Engineering Career Ladders
- 21:48First Engineering Ladder
- 23:44Learning Review
- 25:34Relatedness
- 26:57Vulnerability
- 28:41Apology
- 31:48Conflict
- 32:46Fitness Hammer
- 33:55Conflict vs Curiosity
- 34:40Boring Meetings
- 36:11Summary
- 37:19Never Give Up
- 37:55Empathy
- 38:28Resources
- 38:48Technical Debt Loan Sharks
- 42:53When to Apologize
- 44:15Where to Start to Change
- 46:18Engineering Career Ladder
related talks
51mBuilding a High-Performance Team is Everyone's Job
15mBuilding high performing teams
30mThe Elements of Scaling
28mBuilding happier engineering teams
44mFundamentals & Practices for getting a High-Performance Team
42mBuilding a Strong Engineering Culture – Stacy Devino
28mBuilding High Performance Engineering Teams
44mEnhancing the Performance of Engineering Teams