Use DORA metrics to support the next generation of remote-work models

The move to remote working is creating tensions between CEOs and CHROs that could culminate in decisions that are not always in the best interest of the business. For tech teams, that disconnect could lead to making quick fixes that ultimately cost the organization more money and individuals more time and stress.

The remote revolution is here to stay. More than three-quarters of engineers want the option to work from home, and some countries are considering introducing remote work into law. Before that happens, CEOs and CHROs need to get back on the same page to support their tech teams and business outcomes.

Start with DORA metrics

DORA metrics measure software delivery velocity and throughput by plugging into Git (commits and pull requests) and deployment data.

The metrics consist of deployment frequency, lead time for changes, mean time to recovery and change failure rate. This information can also flag if engineers are losing engagement, highlight high and low performers and help companies avoid resorting to quick fixes that aren’t sustainable for remote-work models.

Whether you’re ready to move past the hybrid midpoint or are taking the direct leap to remote, here’s why you need DORA metrics at your side.

Shine a light on areas for growth

When working from different locations, it’s easier for processes to slip, miscommunication to happen and opportunities for improvement to be overlooked. With DORA metrics, remote teams can more efficiently review their practices and track their success.

To effectively track DORA metrics, companies need a CI/CD platform (Jenkins, CircleCI or Github Actions) that connects to a development analytics platform to aggregate data on engineering teams’ output. Teams can then zoom in on metrics like lead time for changes to measure the quality of code, and ultimately, the product or service they maintain.

Similarly, DORA metrics can reinforce the need for remote teams to include testing in the development process to lower their lead time for changes. This can help eliminate bottlenecks, as testers can teach developers to write and automate tests.

Likewise, keeping tabs on deployment frequency will prompt tech teams to release more often and in smaller chunks, allowing them to spend less time and resources trying to detect issues retrospectively.

By looking at a combination of DORA metrics, teams can avoid making quick fixes that aggravate issues down the line. The more frequently teams release, the more often they can make fixes that address the root cause.

Provide remote engineers with development paths

More than 40% of executives say that remote employees are less likely to be promoted due to limited visibility and contact with management than in-person employees. But with fully remote teams becoming the norm, remote engineers can’t go unnoticed or be put at greater risk of disengaging.

DORA metrics are tied closely to value. A top-performing worker generally has low lead times for changes and high deployment frequency with a low mean time to recover and change failure rate. Managers can recognize individuals that may be falling behind on these metrics and set up meetings to learn how the remote shift has impacted them and their work.

At the same time, career-enhancing assignments can be identified using DORA metrics, ensuring that remote engineers are equally tasked with day-to-day duties and development opportunities. For example, DORA metrics can highlight if teams have more work around practical metrics like mean time to recover rather than innovation projects that would showcase their potential to move into more complex roles.

If a team is excelling in their DORA metrics, you may want to offer them a specialization track, where they own a particular area of the product that correlates with the metrics. If a team or individual is struggling, you could provide training courses, mentorship programs or other support. Together with other objective data around performance, DORA metrics can let you make informed decisions for bonuses and promotions.

Visually track the impact of being remote

Like most data, DORA metrics can be visualized to allow you to automate and centralize software-delivery measurement. Not only does this visualization let decision-makers draw clear and accurate conclusions, it also makes it easier to spot trends and patterns in how software is built and released.

Managers can compare their DORA dashboard takeaways with industry benchmarks to understand how their teams perform relative to others and pinpoint any bottlenecks. Any stark anomalies in DORA metrics could mean that your teams don’t have the tools or working conditions they need and that your business needs to change its remote strategy.

A general best practice for collecting and tracking DORA metrics involves identifying a baseline and setting up targets at the team, product and organization levels. Early and frequent commits alongside automated testing and validation should also be on engineering managers’ radar when reviewing DORA metrics.

Take for example Zoopla, which used DORA metrics like mean time to recover, change fail rate and production-deploy frequency to consolidate its remote engineering strategy. The data was discussed in the company’s fortnightly ops review and influenced it to automate the majority of its deployment pipelines, train teams in incident response, improve onboarding and review alerting. Zoopla also chose to display the metrics publicly so everyone could see the company’s progress and compare its position against competitors.

Companies that dive into being completely remote without DORA metrics could see their strategy sink. DORA metrics supply a reference point for future product development and unite remote team members under a common goal. Moreover, DORA can be a springboard for companies to keep engineers motivated and efficient and naturally slot into the modern ways of working.