Skip to content
Nerdy beta

DevEx: What Actually Drives Productivity

Noda, Storey, Forsgren, and Greiler argue that the productivity question has been asked backwards for twenty years. Instead of counting what developers produce, measure the conditions they work under, and the paper names three that account for most of the variance: feedback loops, cognitive load, and flow state. The contribution is the compression. Developer experience had been a grab bag of complaints about tooling and process; this paper turns it into three dimensions you can survey, track, and act on. Forsgren’s presence connects it directly to the DORA lineage, and Storey’s to SPACE — the same researchers narrowing their own earlier work into something a team can use on a Tuesday.

The paper also makes the business case that engineering leaders need when they ask for budget: friction compounds, and the cost shows up in delivery speed, defect rates, and who quits.

Resources