Engineering Culture
Making Developer Experience a Business Priority
Turned DevEx from an engineering-internal concern into a company-wide north star metric, moving a ~100-person org to the 75th percentile for developer experience in its cohort.
Key Metrics
- 50%+ on DXI — Developer Experience Index
- 75th percentile benchmark reached for similar-sized organizations
- Quarterly org-wide reporting — DevEx tracked alongside product and commercial metrics
The Challenge
In an engineering-powered B2B/B2C SaaS business, developer experience was considered "a nice-to-have." The negative impacts of poor DevEx—slower delivery, more incidents, higher attrition risk—were invisible to everyone outside engineering. A shift in the whole business's thinking about engineering productivity was required, beyond just tooling.
The Approach
We introduced the Developer Experience Index (DXI)—a compound metric combining qualitative survey data and quantitative signals—as a formal measure of engineering health. We established a baseline, benchmarked against comparable organizations, and made DXI a standing agenda item at the leadership level.
Investment went into underlying drivers: internal platforms, documentation, shared capabilities, and clear ownership models. Crucially, initiatives were framed in terms of business impact, not engineering comfort.
The Outcome
The organization moved from an untracked baseline to the 75th percentile for similar-sized companies, with a 5-point increase in DXI. DevEx evolved from an engineering conversation to a business conversation—now tracked quarterly alongside product and commercial metrics, signifying a lasting change in how the company values and invests in engineering capability.