Discover how companies measure and prioritize productivity and how developers feel about this process.
Most companies don’t have specialist roles dedicated to developer productivity. Instead, the responsibility falls on team leads and even developers themselves.
This is a problem because teams focused on delivery are also expected to master measurement methodology, often without resources or proper training.
Team leaders
Developers themselves
Dedicated specialists or dedicated teams
Developers want a balanced approach to productivity.
Devs want to be asked about their team processes and communication, satisfaction with tools, and overall well-being.
say non-technical factors, like job design, clear communication, peer and manager support, and actionable feedback, influence their productivity.
say technical factors, like performance and reliability of development tools, influence their productivity.
Many organizations combine operational metrics with human-centric dimensions to get a complete picture of developer productivity.
There is a shared interest in internal training, but a disconnect remains between the priorities of technical managers and what companies deliver.
Technical managers want 2× more focus on communication issues and nearly twice as much investment in reducing technical debt.
The State of Developer Experience and Developer Productivity
66% of developers don’t believe or aren’t sure that current metrics reflect their real contribution.
Instead, they consistently request greater transparency and clarity in measurement processes.
Get access to the full report