Measuring Specific Initiatives in Projects

2min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

Measuring specific initiatives in projects can be challenging due to the complexity of various changing factors. To address this, it is essential to use leading indicators such as metrics on flakiness, build times, and code review wait times that teams can directly influence. Lagging indicators like survey data and dorm metrics should not be used for key results (KRs) as they are less concrete and take longer to show results. These leading indicators are crucial as they provide measurable insights that can potentially influence outcomes over time. They serve as valuable complements, offering a high-level overview of the project's direction, identifying bottlenecks, and areas for prioritization. It's important to understand that survey metrics and quant metrics are influenced by numerous factors, and improvements may have a delayed impact on internal customers' perceptions and experiences.

Christopher Sanson is a product manager at Airbnb who is dedicated to enhancing developer productivity and tooling. Today, we learn more about Airbnb's developer productivity team and how various teams use metrics, both within and outside the organization. From there, we dive even deeper into their measurement journey, highlighting their implementation of DORA metrics and the challenges they overcame throughout the process.

Discussion points: