My Journey to Understanding Technical Leadership
summary
Argues that technical leadership is serviceable work with concrete practices: run blameless retrospectives, enforce a 30-minute rule so blocked engineers ask for help, and use agile ceremonies and weekly check‑ins to spread knowledge. Prioritize trust, presence, and empathy—delegate tasks, coach rather than fix commits, and reassign people into growth roles (an engineer moved onto React). Balance innovation with pragmatism: prefer tested automation, limit risky tech bets, measure progress, and allow safe failure so teams learn and scale.
AI-written summary · about
chapters (20)
- 0:00ADAM BERGSTEIN UNDERSTANDING TECHNICAL LEADERSHIP
- 3:26WHAT IS A TECHNICAL LEADER?
- 5:33The task of leadership is not to put greatness into humanity, but to elicit it, for the greatness is already there.
- 10:56CHARACTERISTICS
- 11:32SERVANT LEADERSHIP
- 14:05Senior developers: unblocking and being a force multiplier to the junior developers on your team is literally the most important thing you can and should be doing with your time.
- 15:36EMPATHY
- 19:56CONTINUOUS LEARNING
- 23:48Only those who dare to fail greatly can ever achieve greatly
- 28:17To be trusted is a greater compliment than being loved.
- 31:15LESSONS LEARNED
- 31:28PRESENCE
- 38:05BE INFORMED
- 40:54BE FLEXIBLE
- 43:30No job is ever beneath you.
- 45:16EVOLVE
- 46:11Change is the end result of true learning.
- 48:34AWARENESS OF BUSINESS FACTORS
- 52:01TECHNICAL SEXINESS VS PRAGMATISM
- 56:54Small acts, when multiplied by millions of people, can transform the world.
related talks
24mTechnical Excellence in Technical Leadership
16mThe secret to technical leadership
22mThe Role of being Technical in Technical Leadership
06mThe role of being technical in technical leadership
41mLevel Up: Choosing The Technical Leadership Path
30mWhat I wish I knew as a first time Tech Lead
29mThe Constant Life of a Tech Lead
48m10 tips to become an awesome Technical Lead