Beyond green squares: Effectively driving productivity

Before we can determine the impact of tools on productivity, we need to ensure we're asking the right questions.

The traditional approach to measuring productivity, and in turn velocity, is the number of lines of code. It's the most straightforward way to both understand and collect from a data perspective. Unfortunately, having this as our primary focus is a flawed approach. It both incentivizes the wrong behavior and doesn't provide a full picture of what a developer does in a day.

In this episode of Beyond the Commit, Eirini Nathan, staff researcher at GitHub, sat down with host Christopher Harrison to help us better understand developer productivity. She explains that no developer sits down for a day's work with a goal of writing a certain amount of code. Instead they work to implement features, fix bugs, and design architectures — activities that aren't reflected in the green squares that appear on a developer's profile.

There are established frameworks, such as DORA and SPACE, which are designed to provide a holistic overview of productivity. However, if you're new on this journey, these might not be the best approach. A better place to start is figuring out what goals you’re trying to meet by measuring, then have conversations with developers to determine any barriers they may be facing.

During the episode, Staff Product Manager Bronte Van der Hoorn calls in to add her perspective on the importance of goals. After all, it's impossible to determine success if there isn't a clear definition of what success looks like. Once you establish goals, you both have a direction and a topic of conversation for your developers.

Talking to your developers should take many forms, including surveys, focus groups, and one-on-one conversations. Eirini recommends taking a three-step approach: listen, act, and learn. As you talk to your developers, listen to their experience and the blockers they face. Act on that feedback, working to make changes to improve both the developer experience and their productivity. Finally learn from that journey, see what worked and didn't, then make the appropriate adjustments.

To learn more and continue your journey, explore the resources below:

Insights

Want to learn more about the strategic role of AI and other innovations at GitHub? Explore Executive Insights for more thought leadership on the future of technology and business.