So, you’d like to stack rank your developers?

In an era where engineering leaders face pressure to maximize efficiency amid economic challenges, the temptation to use stack ranking to assess developer productivity is strong, though fundamentally flawed. The text highlights that relying on simplistic metrics to rank developers, such as the number of commits or pull requests, fails to account for the nuanced nature of software development work, leading to adverse outcomes like gaming the system, knowledge hoarding, and the departure of top talent. Instead, the piece advocates for a more holistic approach to performance management, emphasizing growth frameworks over competition, which involves understanding team dynamics, fostering collaboration, and focusing on competencies such as technical skills, business impact, and leadership. Such an approach not only aligns with the interests of boards seeking to understand engineering productivity but also supports a more sustainable and effective engineering organization.