SPACE: Measuring Developer Productivity
summary
The SPACE framework measures five dimensions — satisfaction, performance, activity, communication and flow — using telemetry and surveys to avoid single‑metric traps. Results include a 5,000-developer survey, code review and pull request telemetry, and interventions like org-wide health days that cut PRs to a third but recover in two weeks. New hires show a 23% drop in first-90-day PRs during remote onboarding; targeted changes yield 33% faster time-to-first-PR and 68% more one-on-ones.
AI-written summary · about
chapters (18)
- 0:00Start
- 1:47Why developer matters
- 2:33Myths and misconceptions about developer productivity
- 3:36Productivity is all about
- 6:31One productivity metric can tell you everything
- 9:37comes down to engineering systems and developer tools
- 10:53SPACE: A framework for understanding developer productivity
- 11:40Satisfaction and well-being
- 12:29Performance
- 14:43Communication and collaboration
- 15:43Efficiency and flow
- 16:43SPACE framework example 02
- 18:16How to use the framework
- 19:08What to watch out for when using the framework
- 24:38Investing in emotional wellbeing supports productivity
- 27:31SPACE Those new hires were struggling to connect
- 28:41Key tips heard from successful onboarding experiences
- 31:20SPACE Using SPACE to measure the impact of improved onboarding
related talks
33mMeasuring Developer Productivity: the good, the bad and the data
43mThe Past, Present and Future of Developer Productivity Theories and Metrics
43mMeasuring Developer Productivity: The Good, the Bad and the Data
11mWhat does 'productivity' actually mean for developers?
25mRethinking measurement for high-performing teams
47mCan We Measure Developer Productivity?
27mDevelopers Expose What's Breaking Productivity in Their Companies
37mA systems view of developer productivity