New research offers guidelines to reduce developer burnout through belonging
Study links lack of belonging to higher burnout risk; here's how to fix it
Deep Dive
A study published in IEEE Software (2025) offers evidence-based guidelines for cultivating belongingness and reducing developer burnout. Based on prior research in proprietary software organizations and open-source software communities, the authors identify key characteristics like trust, acceptance, and mutual support. Practical recommendations include blameless postmortems, transparent promotion rules, and newcomer gatherings to foster healthier, more inclusive environments.
Key Points
- Lack of belonging is associated with higher burnout risk in both proprietary and open-source developer environments.
- Seven characteristics of belongingness identified: trust, acceptance, value recognition, friendship, membership, mutual support, and being known by others.
- Actionable guidelines include blameless postmortems, transparent promotion rules, newcomer gatherings, and continuous monitoring of belonging and burnout.
Why It Matters
Tackles the root cause of developer turnover with evidence-based, actionable strategies for tech leaders.