How to measure AI developer productivity in 2025 | Nicole Forsgren
From Lenny's Podcast
Nicole Forsgren•Senior Director of Developer Intelligence, Google
Executive Summary
AI tools accelerate coding tasks but don't automatically increase overall developer productivity, as new bottlenecks and foundational issues like broken builds and flaky tests persist.
Traditional productivity metrics like 'lines of code' and even DORA metrics are becoming obsolete; the focus must shift to holistic frameworks (like SPACE) and measuring end-to-end velocity tied to business outcomes.
The developer's role is evolving from writing code to reviewing and verifying AI-generated output, placing a new premium on critical evaluation and learning how much to trust the machine.
Improving the core Developer Experience (DevEx)—defined by flow state, cognitive load, and feedback loops—is the most effective way to unlock sustainable performance gains in the AI era.
8 quotes
Concerns Raised
Traditional productivity metrics (lines of code, DORA) are no longer sufficient in the age of AI.
AI tools can create new bottlenecks and require a significant shift in developer work from writing to reviewing and trusting code.
Companies may invest in AI tools while ignoring more impactful, foundational DevEx issues like broken builds and flaky tests.
Simply shipping code faster is useless without a clear strategy on what to build and why.
Opportunities Identified
Leverage AI to accelerate prototyping and A/B testing, enabling faster learning cycles.
Use AI to help developers enter 'flow state' more quickly, making shorter work blocks more productive.
Implement a dedicated Developer Experience (DevEx) program to systematically remove friction and improve performance.
Shift developer focus from rote coding to higher-value activities like system design, code review, and strategic planning.