Where we’re going wrong with developer productivity
summary
Presents a clear claim: a science-backed metric called developer thriving (four factors: agency, learning culture, self-efficacy, belonging) predicts productivity across 1282 developers and explains a significant share of variance using serial mediation analysis. Introduces the software work visibility and value scale, a measurable lever, plus white papers, QR-linked resources and a research lab; shows resilient productivity beats brittle metrics like commits and hours and the interventions tested produce lasting benefits.
AI-written summary · about
chapters (6)
- 0:00Defining the problem
- 2:44Identifying brittle metrics
- 4:55Three myths of productivity
- 10:34The framework of thriving
- 13:47Evidence for resilience
- 24:42Leading the conversation
related talks
43mThe Past, Present and Future of Developer Productivity Theories and Metrics
33mMeasuring Developer Productivity: the good, the bad and the data
43mMeasuring Developer Productivity: The Good, the Bad and the Data
47mCan We Measure Developer Productivity?
34mBuilding a Culture For Developer Productivity
11mWhat does 'productivity' actually mean for developers?
51mDeveloper productivity is waste
31mHow Do You Measure Devel...
