Guidelines for Cultivating a Sense of Belonging to Reduce Developer Burnout

TL;DR

This paper reviews recent research on belongingness in software teams and offers evidence-based guidelines for fostering inclusion to reduce developer burnout and improve well-being.

Contribution

It provides a comprehensive synthesis of belongingness factors and practical, actionable guidelines for leaders and communities to enhance developer well-being.

Findings

Belongingness is linked to resilience, job satisfaction, and well-being.

Key characteristics include trust, acceptance, and mutual support.

Guidelines include recognition, inclusivity, and continuous monitoring.

Abstract

Burnout affects software developers' mental and physical well-being and contributes to turnover, generating strong concerns in the software industry. Prior research has shown that lack of belonging is associated with higher levels of burnout among software developers, while a sense of belonging is linked to resilience, job satisfaction, engagement, and well-being. In this paper, we revisit recent studies on belongingness in software development teams, including proprietary software organizations and open-source software communities, to offer evidence-based guidelines for cultivating belongingness and reducing developer burnout. We summarize characteristics of belongingness, such as trust, acceptance, value recognition, friendship, membership, mutual support, and being known by others, as well as factors associated with belongingness, including recognition, psychological safety, intrinsic motivation, English confidence, tenure, gender, and cultural power distance. Based on these findings, we propose practical guidelines for leaders and communities, including timely and consistent recognition, transparent promotion rules, inclusive benefits and initiatives, intentional connections through collaborative tools, blameless postmortems, optional in-person opportunities, informal newcomer gatherings, and continuous monitoring of belongingness and burnout. These guidelines can help software organizations and open-source communities foster healthier, more inclusive environments that support developer well-being.