The goal isn't for individuals to code faster alone. It's to remove human and technical bottlenecks that slow down great teamwork. Developer productivity and happiness are tightly intertwined.
More on developer productivity, this time LinkedIn’s Developer Productivity & Happiness Framework 😊
Similar to Atlassian, LinkedIn looks to remove things that make the job suck, add human context to system output, and focus on developer happiness. TLDR:
To reduce incentives to game the system and performance theater, LinkedIn uses GSM to choose metrics:
🥅 Goals - Decide what are the goals that you want to achieve for your product or system
📶 Signals - Decide on the signals that tell you if you’re achieving your goal
📈 Metrics - Choose metrics that act as a proxy of that signal, since few signals can be measured perfectly
The most effective productivity metrics are tailored to each team's context and goals. Generic, company-wide metrics often miss the mark. To find the right metrics you need to:
💬 Ask developers what problems they face daily. Don't assume you know
🆗 Get input on whether a metric reflects an issue they care about fixing
📊 Involve developers in defining metrics for their team's workflow and objectives
We'd love to connect with teams that have successfully combined developer feedback and systems data to drive DevEx. Please DM us!
Excellent article!