Short answer

When proposing design or process improvements that impact developers, proactively gather data that links these changes to business objectives like efficiency, cost reduction, or revenue generation.

Field: Innovation & Design
Source: Queue (2023)
Method: Mixed-methods research, combining quantitative data analysis with qualitative insights.
Evidence: Strong effect

Demonstrating a clear link between improved developer experience and tangible business outcomes, such as increased software delivery speed and reduced costs, is crucial for gaining stakeholder investment. This innovation & design research insight is drawn from a 2023 study published in Queue. Using Mixed-methods research, combining quantitative data analysis with qualitative insights., researchers explored how this design variable affects real-world outcomes. The key design takeaway: When proposing design or process improvements that impact developers, proactively gather data that links these changes to business objectives like efficiency, cost reduction, or revenue generation.

Study

Innovation & DesignRecentStrong effect

Quantifying Developer Experience to Secure Stakeholder Buy-in

Queue · 2023

Key Findings

01There is a strong correlation between positive developer experience and improved software delivery performance.
02Investments in developer experience can lead to significant cost savings and increased revenue through faster time-to-market.
03Business stakeholders often require clear, quantifiable evidence of ROI to approve initiatives aimed at improving developer experience.

Application

Design takeaway

When proposing design or process improvements that impact developers, proactively gather data that links these changes to business objectives like efficiency, cost reduction, or revenue generation.

How to apply

Before launching a new tool or process change for developers, identify key business metrics it could influence and establish a baseline for measurement.

Project actions

01When researching a problem, consider how your proposed solution will benefit the 'business' or 'organization' beyond just the end-user.
02Think about what data you could collect to prove your design's value.

Method & Evidence

AimHow can the impact of developer experience on software delivery performance and business value be effectively measured and communicated to non-technical stakeholders?

MethodMixed-methods research, combining quantitative data analysis with qualitative insights.

ProcedureThe research involved analyzing data from software development teams, correlating metrics related to developer experience (e.g., toolchain efficiency, documentation quality, collaboration ease) with business-oriented outcomes (e.g., deployment frequency, lead time, defect rates, operational costs). Case studies and interviews were used to gather qualitative context and understand stakeholder perspectives.

ContextSoftware development organizations, particularly those facing pressures for efficiency and adopting new technologies.

Variables

IVDeveloper Experience (e.g., toolchain efficiency, collaboration tools, documentation quality)

DVSoftware Delivery Performance (e.g., deployment frequency, lead time, change failure rate), Business Value (e.g., cost savings, revenue growth)

CVOrganizational size, industry, specific technology stack, team structure

Strengths & Limitations

Strengths

+Connects technical improvements directly to business objectives.
+Provides a framework for advocating for design and engineering investments.

Limitations

It can be difficult to isolate the exact impact of one specific design change on complex business metrics, as many factors are usually at play.

Reliability & validity

The study's reliability would be enhanced by replicating the analysis across a diverse range of companies and development methodologies. Validity is strengthened by using a combination of quantitative data and qualitative insights to triangulate findings.

Think critically

If improving developer experience leads to better business outcomes, why do so many organizations still struggle to invest in it?

Design Principles

"Quantify the business impact of user experience improvements to secure organizational support."

In today's competitive landscape, optimizing software development processes is paramount. Understanding how to articulate the value of developer experience in business terms allows design and engineering leaders to advocate for necessary resources and drive impactful improvements.

What This Means for Your Design

Making developers happier and their tools better makes the company more money and saves it money, but you have to show the numbers to prove it to the bosses.

How to use in your project

1.Use this research to justify the importance of your design project's goals, especially if they involve improving a process or tool for a specific group of users.
2.Refer to this when discussing the need for user research or testing that can provide data to support your design choices.

Add to My Project

Quick Cite

Paragraph starter

This research highlights the critical need to demonstrate the business value of design improvements. By quantifying the impact of enhanced developer experience on software delivery and operational efficiency, organizations can secure the necessary buy-in for impactful initiatives. This principle is directly applicable to my design project, where I aim to [briefly state project goal] by [briefly state design approach], and will therefore focus on measuring [specific metrics] to illustrate its positive contribution to [specific business outcome].

Source

Queue

DevEx in Action

journal · 2023

View source

Questions About This Research

What does the research say about quantifying developer experience to secure stakeholder buy-in?: When proposing design or process improvements that impact developers, proactively gather data that links these changes to business objectives like efficiency, cost reduction, or revenue generation. Evidence: Queue (2023).
Why does "Quantifying Developer Experience to Secure Stakeholder Buy-in" matter for design?: In today's competitive landscape, optimizing software development processes is paramount. Understanding how to articulate the value of developer experience in business terms allows design and engineering leaders to advocate for necessary resources and drive impactful improvements.
How can designers apply this research?: When proposing design or process improvements that impact developers, proactively gather data that links these changes to business objectives like efficiency, cost reduction, or revenue generation.
What were the main findings?: There is a strong correlation between positive developer experience and improved software delivery performance.. Investments in developer experience can lead to significant cost savings and increased revenue through faster time-to-market.. Business stakeholders often require clear, quantifiable evidence of ROI to approve initiatives aimed at improving developer experience.
What research method was used?: Mixed-methods research, combining quantitative data analysis with qualitative insights..
How strong is the evidence?: Evidence strength is rated Strong effect, based on a 2023 journal from Queue.
What should I do differently in my next project?: Before launching a new tool or process change for developers, identify key business metrics it could influence and establish a baseline for measurement.
What are the limitations?: The specific metrics and their correlations may vary significantly between different organizational contexts and software development methodologies.