Engineering Enablement by Abi Noda

Setting targets for developer productivity metrics

51 snips
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.
Ask episode
AI Snips
Chapters
Transcript
Episode notes
ANECDOTE

Gaming Metrics Destroys Value

  • Setting a target to increase innovation rate without context can lead teams to game metrics by ignoring bugs or incidents.
  • Distorted data harms the system rather than improving it, highlighting the risks of poorly set goals.
INSIGHT

Control Inputs Not Outputs

  • Input metrics are behaviors teams can control, while output metrics reflect results teams can’t directly influence.
  • Setting targets on controllable inputs improves system health and avoids distorted data from chasing output numbers.
INSIGHT

Break Down Metrics Like Health

  • Breaking large output metrics into smaller, actionable input metrics clarifies where teams can make improvements.
  • Analogous to health, daily habits (inputs) drive infrequent high-level measures (outputs).
Get the Snipd Podcast app to discover more snips from this episode
Get the app