Habits of a Highly Effective Technical Manager
summary
Lists 12 concrete manager practices and gives real examples: bring a coach to teach TDD (borrow Raju), reassign people to fit strengths (developer moved and thrives 10 years later), enforce leaving at 5pm (turns off monitor, team ships more), question rewrites that cost $1M/year, and warn a greenfield can become a “3‑year‑old legacy.” Emphasizes adaptive planning, prefer alignment over agreement, use carrot not stick to raise quality and sustain productive pace.
AI-written summary · about
chapters (33)
- 0:00Introduction to management
- 2:05Being adaptive over reactive
- 4:23The reality of agile planning
- 8:14Adaptive planning practices
- 10:55Motivation through support
- 13:38Team motivation strategies
- 16:18Strength-based placement
- 18:23Results over presence
- 21:46Managing remote teams
- 22:01Effective communication
- 27:18Working smart
- 29:57Culture of focus
- 34:08Addressing problems
- 36:26The team-first mentality
- 38:41Facilitating change
- 39:15Sustainable pacing
- 39:30Alignment over agreement
- 40:10Avoiding politics
- 43:04The importance of quality
- 43:36Staying technical
- 45:01Understanding the 'why'
- 47:00Balancing trust and inquiry
- 47:30Summary of management habits
- 47:41Core leadership recap
- 48:09Final leadership lessons
- 50:18Practical management tips
- 51:36Building high-trust teams
- 52:05Defining success metrics
- 55:08The long-term developer view
- 55:31Technical leadership skills
- 57:16Critical thinking in teams
- 57:37Final reflections
- 57:53Conclusion
related talks
01h 01mQualities of a Highly Effective Manager
31mThings I Wish I Knew When I Became a Manager
58m10 tips to become an awesome Technical Lead
29mThe Constant Life of a Tech Lead
19mWhy It’s Good to Be A Software Manager
33mThe Care and Feeding of Software Engineers
48m10 tips to become an awesome Technical Lead
58mMy Journey to Understanding Technical Leadership