What Technical Leads Can Learn from Great General Managers
summary
Argues that historical management fixes map to engineering leadership today and gives concrete tools and warnings: use the pyramid principle (state the point then supply SCQA details), run timebound OKRs with few targets and avoid linking them directly to comp, practice radical candor's feedback quadrants, and cultivate psychological safety from Amy Edmondson research. Calls out MIT Building 20 as a diversity + proximity case study, warns against 70% overreach, hero developers as single points of failure, and failing to delegate.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:50Courtneys background
- 15:16Michael Dearing
- 15:51The Pyramid Principle
- 17:49Radical Candor
- 19:08Business Results
- 22:31Diversity Matters
- 26:24Motivation
- 30:17Psychological Safety
- 32:01Initiative and Incentive
- 34:45Pitfalls
related talks
16mThe secret to technical leadership
58mMy Journey to Understanding Technical Leadership
29mHow to Become a Great Engineering Manager
21mGrowing engineering managers: Breaking down the monolith
01h 01mHabits of a Highly Effective Technical Manager
31mFrom Engineer to Engineering Manager
22mThe Role of being Technical in Technical Leadership
49mEngineering Leadership in Turbulent Times