Study links psychological safety and clear requirements to major boosts in software project success

A large-scale study of 600 software engineers in the UK and USA reveals that many software projects collapse not because of technical flaws alone, but because teams conceal problems rather than tackling them head-on. The research, conducted by Junade Ali and documented on arXiv, identifies loss aversion—the psychological tendency to fear losses more than we value gains—as a key driver of this cover-up behavior.

Why problems spiral into disasters#

Engineers working under pressure often hide emerging issues to avoid blame or project cancellation. This avoidance behavior can transform manageable technical setbacks into catastrophic failures. The study builds on earlier empirical work showing that psychological safety—a culture where team members feel comfortable discussing and resolving problems openly—is foundational to project success.

Key findings on what works#

The research quantifies the impact of two critical interventions:

• Clear requirements upfront: Establishing well-defined project requirements before development begins, when loss aversion is lowest, correlated with 97% higher project success rates.
• Freedom to discuss problems: Creating an environment where engineers can openly raise and address issues without fear correlates with 87% higher success rates.

The human factor in software failure#

Rather than treating software disasters as purely technical matters, the findings argue for development methodologies that explicitly account for human psychology. By addressing loss aversion early—through transparent planning and psychological safety—teams can prevent the snowball effect that turns modest problems into full-scale collapses.