Estimate project
← All posts

Discover What Sets the Best-Performing Tech Teams Apart

What really matters when building outstanding software? Read on to find out.

8 min read
DevelopmentSoftware DevelopmentSoftware delivery performanceInfrastructureDeveloper Productivity

The DORA research initiative has spent nearly ten years studying how effective the best technology-driven organizations are and how that effectiveness can be measured. In that time, it has collected input from more than 36,000 professionals working in organizations of all sizes across many different industries.

DORA’s goal is to untangle the relationship between operational practices (capabilities) and the results they produce, with a focus on meaningful achievements for the organization as a whole and for the people in it.

Everything in this article comes from the State of DevOps 2023 report. To get a fuller, more detailed picture, I suggest reading the report in its entirety. A free copy is available here.

Software delivery performance

Four key metrics are typically used to measure performance in software development and operations:

  • Change lead time is how long it takes for a requested change to be running successfully in production.
  • Deployment frequency tracks how often new code reaches production.
  • Change failure rate is the share of deployments that lead to a failure in production.
  • Failed deployment recovery time describes how fast a team can bounce back from a failed deployment.

A widely used way to improve all of these metrics is to shrink the batch size of changes to an application. Making smaller changes more often lets teams shorten the lead time for changes, deploy more frequently, reduce the risk of major failures, and recover from failures faster and more easily. This approach simplifies the development process and makes software delivery more efficient and reliable overall.

The teams that gain the most are frequently those that adopt a culture of continuous improvement. This mindset of ongoing development and refinement is about gradually evolving and improving their processes, practices and products. Earlier studies confirm this as well. There is no one-size-fits-all solution, so teams must be free to experiment and find out what suits them best.

To measure how effective these improvements are, the key is to compare the same application’s progress over time, not to look at other applications, organizations or industries. In this way, the team’s work is measured against its own earlier performance, which gives a clear and meaningful view of how it has grown and developed.

This strategy puts the emphasis on self-improvement and on learning from one’s own experience – essential for lasting success and innovation in a fast-changing technological landscape.

Concentrating only on performance metrics can occasionally backfire, as teams start to value the numbers more than real improvement. A more practical approach is to invest in building capabilities and nurturing a learning environment.

When skill development, knowledge acquisition and continuous learning take centre stage, teams are in a better position to adapt, innovate and improve their performance in meaningful ways.

The main takeaway is that teams that put learning and growth first usually improve the most. This fits the view that long-term success comes from evolving and reacting to new challenges and opportunities, not merely from hitting predefined metrics.

Organizational performance

In their quest to raise developer productivity and overall organizational efficiency, organizations frequently get fixated on the latest technologies and management trends. Research shows, however, that taking a user-focused approach to building applications and services is essential to an organization’s success.

To improve performance, you need a deep understanding of your users and must keep adjusting your approach based on what they tell you.

“Organizational performance is 40% higher in teams that focus on the user.”

User feedback plays a central role in pointing teams towards what matters most, so that they can build products and services that truly meet user needs. This focus improves the user experience and raises user satisfaction, which can then lead to higher revenue. By building capabilities that are better tuned to what users need, organizations put themselves on the road to success.

Putting the user’s perspective first makes sure that product development and delivery teams genuinely address their users’ needs and build the right solutions for the people they serve.

“A focus on the user results in 20% higher job satisfaction.”

Teams that revolve around user requirements are more likely to build products and services that closely match what is really needed. When teams are free to work on and maintain a system that helps their users, they are more satisfied with their jobs. This also raises their performance and the quality of the software they ship.

It’s worth stressing that a user-centered approach to software development substantially improves performance. Organizations that put their users first gain a wide range of benefits.

By incorporating user feedback, teams can bring their projects more in line with user needs, resulting in products and services with better user experiences. This alignment raises user satisfaction and may also increase revenue.

Technical capabilities

Putting effort into continuous integration, a loosely coupled architecture and quicker code reviews can lead to many improvements. It can boost the performance of the organization and its teams, as well as software delivery and operations.

On top of that, it supports the well-being of the people building the app or service. With a loosely coupled design, a team can also test, build and deploy its work without having to wait for other teams, which eliminates delays and makes the process faster.

“Software delivery performance is 50% higher in teams with faster code reviews.”

An efficient code review process has many advantages. It raises code quality, supports knowledge sharing and gives everyone a voice in the code. This results in stronger team ownership and shared responsibility.

A shorter gap between finishing the code and reviewing it can hurt both the developer’s effectiveness and the quality of the software. Smaller code reviews work better: they’re easier for the reviewer to grasp and help the team stay efficient and focused.

Within a company, it’s essential to build a culture that makes it possible to share risks, strengthens cooperation and creates psychological safety. This means shaping an environment where team members are comfortable taking calculated risks because they know their colleagues have their backs. Cooperation grows when everyone feels they belong to a team pursuing a shared goal.

Psychological safety is essential, as it lets people voice their ideas and concerns without worrying about negative consequences. A culture like this raises productivity and strengthens job satisfaction and team spirit.

Documentation

Good documentation is not only a guide – it serves as a store of the team’s knowledge. This matters all the more as people join and leave the team, since it keeps valuable information and insights preserved and accessible. Good documentation also has a positive effect on team performance, productivity and job satisfaction.

“With high-quality documentation in place, trunk-based development, for instance, is estimated to have 12.8x more impact on organizational performance than with low-quality documentation.”

Flexible infrastructure

Cloud computing is a key core enabler of flexible infrastructure. It isn’t simply a matter of using cloud services – the way a team uses them predicts its performance far better. Using cloud computing well can bring striking gains in job satisfaction and productivity, along with a marked drop in burnout.

Teams that make good use of the adaptability and scalability of cloud computing can work more efficiently and get better results, which adds to overall job satisfaction and productivity.

“Using a public cloud, for instance, increases infrastructure flexibility by 22% compared with not using the cloud. That flexibility then results in 30% higher organizational performance than with inflexible infrastructures.”

Simply shifting your workload from a data center into the cloud won’t guarantee success. To get the real benefits of cloud computing, you need to rethink from the ground up how you build, test, deploy and monitor your applications. That means adopting the five essential characteristics of cloud computing: on-demand self-service, broad network access, resource pooling, rapid elasticity and measured service.

The data shows that cloud computing has a mostly positive effect on people’s well-being. By simplifying processes and making resources easier to reach and manage, cloud computing can lower stress and raise job satisfaction, helping to create a healthier work environment. Relying on public cloud infrastructure considerably reduces the risk of burnout.

Culture

Culture plays a key role in both people’s well-being and the success of the organization. A healthy organizational culture greatly reduces burnout, raises productivity and improves job satisfaction. Such a positive environment is good for individuals and also substantially improves organizational performance, including software delivery, operational efficiency and team effectiveness.

Within a healthy organizational culture, teams are better at putting in place the technical capabilities that lead to better outcomes. This culture creates a supportive environment that encourages innovation, collaboration and continuous improvement. Consequently, teams are better prepared to face new challenges, adapt to change and make efficient use of technological progress.

A strong, positive culture is a cornerstone that lets teams flourish and excel in what they do.

“Organizational performance is 30% higher in teams with generative cultures.”

A healthy organizational culture strengthens technical capabilities. A positive, supportive culture helps put these capabilities into practice effectively, creating an environment in which innovation and efficiency flourish.

What’s more, a healthy culture not only supports technical improvements but is also central to improving people’s well-being. Where staff feel valued and supported, their overall job satisfaction and productivity often rise noticeably.

In the end, a healthy culture underpins an organization’s health and success. It is a key factor that shapes every part of an organization, from its technical capabilities and people’s well-being to its overall performance and growth.

Conclusion

It’s great that this research was carried out. We now have hard data on what works and why, which gives us insight into what really matters when building outstanding software.

Once more, I highly recommend reading the full report – the value of its findings is hard to overstate. It covers other fascinating topics I haven’t mentioned here, such as resilience and the role of AI in the industry. The report also explains the methodology, demographics, models and more.