Building a Culture For Developer Productivity
summary
Argues that productivity means high-quality software at speed and that leaders should measure blockers not output, run small developer focus groups and short surveys, and track whether managers act on results; Atlassian reports a 25% improvement in developer satisfaction after this approach. Recommends milestone-based delivery and carving time for tech debt, uses feature-flagging and experimentation tooling (Split) and Harness engineering insights to surface bottlenecks, and says developer-facing SDK work and iterative releases measurably improve outcomes.
AI-written summary · about
chapters (12)
- 0:00Developer productivity culture
- 3:43Defining productivity
- 7:11Why output metrics fail
- 8:39Leadership role in productivity
- 11:25Managers undermining joy
- 16:24Actions for culture
- 18:29Developer feedback surveys
- 22:16Psychological safety in surveys
- 25:26Practical survey changes
- 27:31Measuring developer experience
- 29:37Impact on external customers
- 32:25One key step for leaders
related talks
33mMeasuring Developer Productivity: the good, the bad and the data
31mDeveloper productivity is waste
43mMeasuring Developer Productivity: The Good, the Bad and the Data
51mDeveloper productivity is waste
48mDeveloper Joy – How Great Teams Get s%*t Done
58mDeveloper Joy – How Great Teams Get S%*t Done
45mDeveloper Joy – How great teams get s%*t done
47mCan We Measure Developer Productivity?
