Empowerment in the Software Delivery Lifecycle
summary
Concrete practices decide whether to watch: a job family matrix that maps IC and leadership paths, explicit parallel IC and manager tracks, running hackathons that attract 50+ teams and produce reusable prototypes, carving slack time for innovation, making distributed teams feel ownership by routing customer feedback back to engineers, switching from meetings to book conversations not meetings, and using one‑on‑ones and mentorship to measure growth and whether built changes actually work.
AI-written summary · about
chapters (9)
- 0:00Panel introduction
- 4:57First leadership challenges
- 11:43Gender and age gaps
- 20:23Advice for aspiring leaders
- 26:42Qualities of technical leaders
- 31:18Innovation versus coordination
- 37:46Defining leadership success
- 45:05Confidence in leadership
- 51:00Closing remarks
related talks
26mScaling Better Software Delivery: A Framework for Dev Enablement Through DevRel and Outreach
34mBuilding a Culture For Developer Productivity
32mEmpowering Early-Career Developers
52mShifting into continuous delivery
44mEnhancing the Performance of Engineering Teams
36mNuances of Influencing Developer Experience and Productivity Through Tech Products
32mBuild Teams as an Engineer
46mImproving Software Flow