The Case for Principle-Based Engineering Management
summary
Engineering managers juggle four concrete responsibilities—people manager, technical leader, project owner and business owner—and the claim is that a short set of guiding principles reduces constant context switching and bad decisions. Examples: positive bias, insist-on-learning, emphasize strengths, and be data-driven. Tools used are explicit written principles, printed reminders, mentoring and metrics; a shared principle helped defuse a recurring tech‑lead conflict. Practical outcome: clearer hiring/roadmap tradeoffs and steadier decisions after five years of applying these methods in a ten‑year software career.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:45Who am I?
- 3:34Session Objectives
- 5:334 Major Functions
- 8:38People Management
- 10:56Tech Leadership
- 12:17Project Management
- 13:47Business Owner
- 15:30Why manage?
- 21:43Why principles?
- 31:01Summarizing
related talks
31mFrom Engineer to Engineering Manager
30mManaging at the threshold: Examining our principles in a moment of change
29mHow to Become a Great Engineering Manager
42mPanel: The Role of Engineering Manager
53mEngineering + Management != “Engineering Management”
22mWhat the Best Engineering Leaders Do Differently
38mEngineering Engineering: More than the sum of our parts
08m3 Principles That Create Modern Management