Beyond developer productivity: what's next?
summary
Claim: KPIs alone mischaracterize engineering success and developer productivity is an incomplete proxy. Presents a practical framework of alignment, delivery performance, health backed by experience running a platform and as VP engineering. Uses DORA metrics at team level, effort-allocation tracking (vs. timesheets), Jira ticket discipline, churn/satisfaction surveys and shared incentives for PMs and engineers. Describes applying the framework to map engineering work to business goals, expose metrics to teams, and measure platform shifts where DORA improvements indicate success.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 1:10Developer productivity hot topic
- 4:46Why productivity isn't the bottleneck
- 6:32Engineering success analogy
- 9:00Why engineering success is complex
- 11:50Success is relative to context
- 13:15Three components of success
- 15:20Measuring alignment
- 21:01Delivery performance metrics
- 25:33Health as sustainable context
- 27:18Key takeaways and Q&A
related talks
18mFrom developer productivity to engineering impact
47mCan We Measure Developer Productivity?
43mMeasuring Developer Productivity: The Good, the Bad and the Data
33mMeasuring Developer Productivity: the good, the bad and the data
31mHow Do You Measure Devel...
31mDeveloper productivity is waste
42mHelp! My Manager Wants KPIs!
44mEnhancing the Performance of Engineering Teams