A systems view of developer productivity
summary
Argues that dashboards counting commits and PRs mislead because individual metrics drive people to hoard work and slow the whole system; using SPACE and DORA alongside measures of psychological safety produces balanced signals. Shows a simulation where encouraging ask for help/pairing cuts project time from 150 to 135 days and reduces ~300 to ~250 man‑days of unplanned work. Cites 94% system variation (not individuals) and recommends iterative experiments via PDSA instead of surveillance or one‑off interventions.
AI-written summary · about
chapters (13)
- 0:00Developer productivity focus
- 2:35Industry tools and measurement
- 5:45Historical software performance
- 11:53Systems thinking evolution
- 13:18Deming’s profound knowledge
- 14:05Team productivity model demo
- 20:48Optimizing whole system
- 23:18Psychology in productivity
- 26:12Fear and performance impact
- 27:57Management’s role in motivation
- 30:04Variation in system performance
- 33:54Theory of knowledge approach
- 36:43Conclusion and key takeaways
related talks
39mThe systems thinking view on developer productivity and experience
33mMeasuring Developer Productivity: the good, the bad and the data
43mThe Past, Present and Future of Developer Productivity Theories and Metrics
25mRethinking measurement for high-performing teams
43mMeasuring Developer Productivity: The Good, the Bad and the Data
31mDeveloper productivity is waste
14mWhat dashboards don't tell you
44mSPACE: Measuring Developer Productivity