Software engineering practices to improve management
summary
Sees a concrete claim: managers account for ~70% of team performance (Gallup), so reusable practices matter. Recommends decision logs and simple templates to record the why and reuse salary, promotion and hiring decisions; a lightweight run book or checklist makes delegation and onboarding work. Uses engineering rituals — sprint boards for prioritising management work, daily stand-ups, pairing sessions for feedback, and retros/journals for learning. Warns against over‑engineering processes: iterate a few cycles, then formalise. These practices reduce repeated toil and improve consistency.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:37Why is this important
- 1:52Salary review
- 2:47Dont repeat yourself
- 3:12Unit of reuse
- 4:12Write it down
- 4:51Process
- 6:32Application
- 7:25Pairing
- 8:16retrospectives
- 8:45conclusion
related talks
33mThe Care and Feeding of Software Engineers
46mCracking the cadence of your software engineering 1:1s
31mFrom Engineer to Engineering Manager
01h 01mThe Care and Feeding of Software Engineers
43mThe Joys of Managing Engineering Teams
09m"The Joys of Managing Engineering Teams"
44mBehavioral Software Engineering
32mDeveloper productivity 2.0