Goals Signals Metrics Framework Explained

3min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

The goals signals metrics framework involves setting goals as the reason for existence, identifying key indicators (signals) that indicate goal achievement, and defining first-order approximations (metrics) of those signals. When engaging with directors, it entails determining their goals, identifying signals of success, and figuring out how to measure them. On the other hand, a bottom-up approach involves consulting with developers who often prioritize service metrics like availability, which may not necessarily align with productivity. It's crucial to engage with people early on to build systems that can measure meaningful factors, rather than getting stuck with service metrics that may not provide relevant insights.

In this episode, Abi chats with Grant Jenks, Senior Staff SWE, Engineering Insights @ LinkedIn. They dive into LinkedIn's developer insights platform, iHub, and its backstory. The conversation covers qualitative versus quantitative metrics, sharing concerns about these terms and exploring their correlation. The episode wraps up with technical topics like winsorized means, thoughts on composite scores, and ways AI can benefit developer productivity teams.

(1:10) Insights in the productivity space
(7:13) LinkedIn's metrics platform, iHub
(12:52) Making metrics actionable
(15:35) Choosing the right and wrong metrics
(19:39) The difficulty of answering simple questions
(26:23) Top-down vs. bottom-up approach to metrics
(32:12) Winsorized mean and selecting measurements
(39:25) Using composite metrics
(46:57) Using AI in developer productivity