Engineering Enablement by Abi Noda
Setting targets for developer productivity metrics
May 9, 2025
In this discussion, Laura Tacho, CTO at DX and creator of the Core 4 framework, dives into the world of developer productivity metrics. She emphasizes the importance of controllable input metrics over misleading output metrics, highlighting pitfalls like Goodhart's Law. Laura shares practical tips for fostering a culture of continuous improvement and why too much focus on outputs can distort data. Expect insights on engaging developers, setting effective goals, and measuring the real impact of productivity in engineering teams.
43:26
Episode guests
AI Summary
AI Chapters
Episode notes
Podcast summary created with Snipd AI
Quick takeaways
- Engaging teams in a collaborative process for setting productivity metrics encourages ownership and genuine improvement rather than mere compliance.
- Focusing on controllable input metrics allows organizations to drive meaningful enhancements while reducing the risk of data distortion and gaming the system.
Deep dives
The Importance of Collaborative Goal Setting
Setting targets for developer productivity requires careful consideration to avoid distorting data or system performance. Simply imposing metrics, such as increasing innovation rates by 5%, may lead to teams ignoring critical tasks, like bug fixes, just to meet targets. Instead, it's essential to engage teams in a collaborative process that invites them to participate in organizational improvements. Giving teams time and permission to enhance their systems fosters a sense of ownership and motivation to genuinely improve productivity.
