The systems thinking view on developer productivity and experience
summary
Historical frameworks (DORA, SPACE, Lean, Deming) get mapped to an agent-based model that simulates a 10-developer team and shows concrete effects: baseline delivery at ~150 days with ~308 man-days lost to unknowns (~20% of time in unknowns), introducing pairing cuts unknown-work to ~222 man-days and shortens delivery by about 10–15 days. Management actions that prioritize individual velocity suppress help-seeking, measurable psychological safety drops information flow, and PDCA-style experiments are required to find safe, system-level levers.
AI-written summary · about
chapters (10)
- 0:00Developer productivity challenges
- 2:11Productivity frameworks history
- 6:02Systems thinking feedback loops
- 11:23Team productivity demo
- 19:21Defining systems interactions
- 23:17Psychological safety impact
- 26:07System performance variation
- 32:23PDSA cycles for improvement
- 37:37Deming's key takeaways
- 38:42Q&A
related talks
37mA systems view of developer productivity
33mMeasuring Developer Productivity: the good, the bad and the data
43mMeasuring Developer Productivity: The Good, the Bad and the Data
31mDeveloper productivity is waste
43mThe Past, Present and Future of Developer Productivity Theories and Metrics
49mProductivity Panel
44mSPACE: Measuring Developer Productivity
31mHow Do You Measure Devel...