From developer productivity to engineering impact
summary
Claims that engineering success requires three measurable components not a single KPI and that developer productivity alone is misleading. Argues industry metrics like DORA are useful at the team level but get misused as executive KPIs and lead to optimizing the wrong things. Gives a concrete lead time example (2.5 days) and calls delivery metrics a Fitbit for teams that only matter when paired with action. Describes building a product called echos to connect everyday work to purpose, says manual attribution was a nightmare, demo available at the booth to show it working.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:58Developer productivity hot topic
- 3:23Why developer productivity is not the full answer
- 4:25Engineering success beyond productivity
- 7:33Three pillars of success
- 9:40Alignment as first pillar
- 13:09Delivery metrics misuse
- 16:41Health as foundation
- 17:44Key takeaways and closing remarks
related talks
33mBeyond developer productivity: what's next?
43mMeasuring Developer Productivity: The Good, the Bad and the Data
47mCan We Measure Developer Productivity?
33mMeasuring Developer Productivity: the good, the bad and the data
31mHow Do You Measure Devel...
31mDeveloper productivity is waste
36mNuances of Influencing Developer Experience and Productivity Through Tech Products
06mDelivery Metrics: the good, the bad, and the totally ridiculous