Developer experience
Three dimensions that drive productivity as engineers experience it (feedback loops, cognitive load and flow state), all measurable and improvable. The framework distils its authors' earlier research; one of them, Nicole Forsgren, had led the DORA programme.
Evidence grade: practice A widely adopted practitioner model with clear provenance.
Use it when
Prioritising and reporting investment in the developer platform by the friction it removes rather than the tooling it installs.
Where it stops working
The framework paper reports no new study, and its dimensions are measured by survey. It measures experience, which is not the same thing as delivered outcomes.
Where the standard uses it
- DE-5Designing how work flowsProcess selection, developer experience, and AI-assisted workflows.
Sources
- Abi Noda, Margaret-Anne Storey, Nicole Forsgren and Michaela Greiler. DevEx: What Actually Drives Productivity. ACM Queue, 21(2), 2023. In the bibliography
Used alongside it
- AI-assisted developer productivity contested
- Aligned autonomy practice
- Goodhart's law practice
- Team topologies and cognitive load practice
- The operating cadence practice
Cite this model
Chicago, BibTeX and licence →Engineering Management Academy. (2026). Developer experience. In Engineering Management Academy Body of Knowledge (Version 3.1, TEC.developer-experience). https://www.engineeringmanagement.academy/body-of-knowledge/techniques/developer-experience