From Engineer to Engineering Manager
summary
Defines engineering management as four concrete pillars — people development, team health and culture, stakeholder management, technical strategy — and offers practical rituals and tools: run a career map and moving motivators in one-on-ones, run an anonymous health check every 3–6 months, use an influence–interest grid for stakeholders, adopt radical candor for feedback, delegate but retain accountability, and write a tech strategy (example: build a design system to unify inconsistent UI). Also notes trade-offs like lost coding time and slower feedback.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:30Engineering management meaning
- 4:35Building team trust
- 9:11Team motivation and values
- 11:56People development and reviews
- 13:47Team health and checks
- 15:12Stakeholder priorities
- 18:20Technical strategy and vision
- 20:47Team compositions
- 23:16Handling conflict and candor
- 25:45Delegation and accountability
- 27:30Tough decisions and trade-offs
- 28:56Signs not for management
- 30:19Final thoughts
related talks
42mHow engineering managers can lead with visibility
42mPanel: The Role of Engineering Manager
21mGrowing engineering managers: Breaking down the monolith
29mHow to Become a Great Engineering Manager
53mEngineering + Management != “Engineering Management”
31mThings I Wish I Knew When I Became a Manager
27mAn Engineering Leadership Roadmap
40mHot Take:Engineering Managers are actually useful!